AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 60 Bitcoin

lightningd: don't forget a channel once we've sent tx_signatures

Public commit record

What the developer wrote

Authored by Sangbida Chaudhuri

81/100 · Strong
lightningd: don't forget a channel once we've sent tx_signatures

Once our sigs have gone out, BOLT #2 says to hold onto the channel
until an input of the funding tx has been spent. Guard the deletion
paths on the new i_sent_sigs flag so an abort or error after that
point keeps the channel around.

Changelog-Fixed: Protocol: dual-fund: we now remember the channel when the peer sends `tx_abort` after we have already sent our `tx_signatures`, as required by BOLT #2.
Co-authored-by: Cursor <cursoragent@cursor.com>
(cherry picked from commit 435fec73acbba17bf9d14bcc72ea088f2beaaf01)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This patch fixes a bug in Core Lightning's dual-funded channel opening. Previously, if the peer sent an 'abort' message or an error occurred after we had already sent our transaction signatures, the node might forget the channel. Because those signatures could let the peer broadcast the funding transaction on the Bitcoin network, forgetting the channel could leave the node unaware of funds it had committed to. The fix makes the node remember the channel until the funding transaction's inputs are spent, as required by the Lightning protocol specification.

Recommended action

Apply the patch. Nodes running dual-funded channel opens should upgrade, as the bug could cause them to lose track of a channel whose funding transaction they have already signed. Monitor for any channels that may have been prematurely forgotten and reconcile on-chain state if necessary.

Security signals we found

01

Protocol compliance fix for BOLT #2 tx_abort receiver rule

02

Prevents premature channel deletion after signature publication

03

Guards against loss of funds/tracking if peer broadcasts funding tx after abort

04

Adds defensive logging for unusual abort-after-signatures cases

05

Cherry-pick from upstream fix indicates backport of a recognized correction

Risk score

Why this scored 60/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 8/15
Affected reach 10/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.