gossmap_manage.c: update BOLT quote and logic to wait for 72 blocks instead of 12 blocks before forgetting a channel.
What the developer wrote
Authored by Níckolas Goline
gossmap_manage.c: update BOLT quote and logic to wait for 72 blocks instead of 12 blocks before forgetting a channel.
test_gossip.py: Update the tests to reflect the changes.
What changed, and why it matters
This commit only adjusts a test file to match an already-implemented change in how long Core Lightning waits before forgetting a closed channel (72 blocks instead of 12). The actual logic change happened elsewhere; this is a test-only fix so the test correctly verifies the new behavior. There is no security issue in this diff.
No action needed; this is a benign test-only alignment commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies tests/test_gossip.py in test_close_72_block_delay. It changes bitcoind.generate_block(70) to bitcoind.generate_block(71) so that after the prior setup, the channel is exactly 72 blocks deep and still visible, matching the updated gossip retention rule. No production code is changed.
Changed components
tests/test_gossip.pyInspect captured patch +1 / −1
diff --git a/tests/test_gossip.py b/tests/test_gossip.py
index 326a4391..13724b9f 100644
--- a/tests/test_gossip.py
+++ b/tests/test_gossip.py
@@ -2059,7 +2059,7 @@ def test_close_72_block_delay(node_factory, bitcoind):
# That implies 72 blocks *after* spending, i.e. 73 blocks deep!
# 72 blocks deep, l4 still sees it
- bitcoind.generate_block(70)
+ bitcoind.generate_block(71)
sync_blockheight(bitcoind, [l4])
assert len(l4.rpc.listchannels(source=l1.info['id'])['channels']) == 1
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.