-
Notifications
You must be signed in to change notification settings - Fork 901
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
Store the announcement_signature
in the database to work around some impls not sending it on reconnect
#2409
Comments
If you don't hurry, I want to have a try. |
Absolutely, go ahead. I can't add you as assignee until you accept my collaborator invitation, but consider yourself the owner of this issue 😉 |
thank u :) ! |
yikers, I haven't looked at my lightning node in awhile and saw this:
|
@jb55 i'm not sure what i'm looking at here. are these all in the same channel status, or did you edit it the output to condense it to just the statuses? |
yeah sorry that was just I noticed with lnvis that all my channels were closed, and all my peers have these statuses. thought that was strange and found this and related issues. |
Actually I'm not sure if they're "closed", but they're not in the listchannels? |
if they're waiting for announcement signatures they won't be 'announced' (no |
yeah none of my channels are getting announced because of this. will try #2619 |
Proposed by @SimonVrouwe here.
This should reduce the number of "Waiting for their announcement signature" channels dramatically.
The text was updated successfully, but these errors were encountered: