Fix: Progress channel announcement state when remote_sigs already in DB#8808
Open
Andezion wants to merge 6 commits into
Open
Fix: Progress channel announcement state when remote_sigs already in DB#8808Andezion wants to merge 6 commits into
Andezion wants to merge 6 commits into
Conversation
cdecker
requested changes
Dec 26, 2025
cdecker
left a comment
Member
There was a problem hiding this comment.
A couple of minor comments, specifically the elements check for 300-546sat outputs is likely important.
6f069fd to
fd9d635
Compare
cdecker
approved these changes
Jan 8, 2026
63364f7 to
843377e
Compare
09b41a2 to
6e0d480
Compare
9dbf1f6 to
f99f74e
Compare
…th (Fixes ElementsProject#8493) Changelog-None
Fixes ElementsProject#8552 Changelog-Fixed: Channel announcements now work after restart even if peer doesn't resend announcement_signatures
Changelog-None
Remove unused pytest import, strip trailing whitespace from blank lines Changelog-None
Changelog-None
f99f74e to
7a34af4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(Fixes #8552)
Depends on #8493 (this PR is stacked on top of the P2TR dust limit fix)
Problem
When a node restarts after exchanging announcement_signatures with a peer - the remote_sigs are loaded from the database during channel_gossip_init(). But when the peer reconnects, it may not resend announcement_signatures if it already sent them before the disconnect!
This causes the channel to get stuck in CGOSSIP_WAITING_FOR_MATCHING_PEER_SIGS state forever, preventing the channel from being announced to the network.
Solution
Modified channel_gossip_channel_reestablished() in channel_gossip.c to check if we already have remote_sigs loaded from the database. If we do - we call update_gossip_state() to attempt to progress the channel gossip state machine instead of waiting forever for the peer to resend signatures
Added comprehensive tests in test_gossip_announcement.py:
test_channel_announcement_after_restart_with_saved_sigs: Reproduces the exact scenario from issue A specific channel is not announcing my side #8552 (channel announcement after node restart)
test_channel_announcement_reconnect_without_restart: Verifies channel announcement works after simple reconnect without restart
Important
26.04 FREEZE March 11th: Non-bugfix PRs not ready by this date will wait for 26.06.
RC1 is scheduled on March 23rd
The final release is scheduled for April 15th.
Checklist
Before submitting the PR, ensure the following tasks are completed. If an item is not applicable to your PR, please mark it as checked:
tools/lightning-downgrade