-
Notifications
You must be signed in to change notification settings - Fork 385
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
Send channel_resstablish that causes lnd to force-close if we don't have the channel #1565
Comments
I might pick this up at some point since I'm familiar with how |
Since we may send |
It depends on how lnd handles the reestablish message, I think ideally we'd just always follow an error with a |
Related to this, would be great if we had a way to give a set of |
As #2401, can you comment there a bit more why we should do that vs users using VSS? I kinda don't want to do it unless we have a very specific user in mind who can't do anything better. |
Done in #2658 |
lnd
is now the only major lightning implementation that deliberately ignoreserror
messages, causing it to not force-close channels even though we ask the peer to.lnd
themselves works around this when trying to restart with their "static channel backups" (which are not, in fact, channel backups...) by sending achannel_reestablish
message that is bogus (I don't recall exactly how, so would need to dig on that first). As much as I really hate to create yet another workaround in our code just because lnd continues to ignore the common spec that no one else has a problem with, it is kinda important we can make our peer broadcast the latest state if we ask, so we should probably send a similarchannel_reestablish
any time we receive achannel_reestablish
from a peer for a channel we dont (any longer) have.The text was updated successfully, but these errors were encountered: