-
Notifications
You must be signed in to change notification settings - Fork 912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Channel not auto closing (other node SCB'ed) #5818
Comments
Same issue here with v22.11. |
see here: #5876 |
This is the correct behavior. Your node should not force-close merely because of receiving an outdated |
Um, sure. Meanwhile, he should be able to force it! Try |
…ning. This gives the peer a chance to send an error, which will make us drop to chain. Signed-off-by: Rusty Russell <[email protected]> Fixes: ElementsProject#5818
…ning. This gives the peer a chance to send an error, which will make us drop to chain. Signed-off-by: Rusty Russell <[email protected]> Fixes: ElementsProject#5818
…ning. This gives the peer a chance to send an error, which will make us drop to chain. Signed-off-by: Rusty Russell <[email protected]> Fixes: ElementsProject#5818
…ning. This gives the peer a chance to send an error, which will make us drop to chain. Signed-off-by: Rusty Russell <[email protected]> Fixes: ElementsProject#5818
…ning. This gives the peer a chance to send an error, which will make us drop to chain. Signed-off-by: Rusty Russell <[email protected]> Fixes: ElementsProject#5818
…ning. This gives the peer a chance to send an error, which will make us drop to chain. Signed-off-by: Rusty Russell <[email protected]> Fixes: ElementsProject#5818
…ning. This gives the peer a chance to send an error, which will make us drop to chain. Signed-off-by: Rusty Russell <[email protected]> Fixes: ElementsProject#5818
running v22.11rc3, ~230 channels
So this other node broke, and the owner used the SCB to recover his funds. My node noticed this, but didn't close the channel. Closing it manually seems to have worked now.
Partial listnodes output:
The text was updated successfully, but these errors were encountered: