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

Update handling of `BumpTransactionEvent::ChannelClose` for 0FC channels

Public commit record

What the developer wrote

Authored by Leo Nash

85/100 · Strong
Update handling of `BumpTransactionEvent::ChannelClose` for 0FC channels

Set an empty witness to spend the P2A anchor, and set the version of the
anchor transaction to 3.

We still check whether the commitment transaction has enough fees to be
broadcast on its own, as these transactions may be non-zero fee due to
trimmed / rounded outputs.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This commit updates how Lightning Dev Kit handles fee-bumping anchor transactions for a newer type of channel (zero-fee commitment channels, or 0FC). It makes two key changes: it uses a much smaller empty witness for the new-style P2A anchor output, and it sets the anchor transaction version to 3 instead of 2. These are protocol-specific adjustments needed so the new channel type can close and fee-bump correctly. The commit does not describe itself as a security fix, and the changes appear to be compatibility/correctness updates rather than a patch for an active vulnerability.

Recommended action

Treat as a protocol-compatibility and correctness update rather than an urgent security patch. Reviewers should verify that the empty-witness P2A spend and version-3 transaction format align with the latest Lightning spec for zero-fee commitment channels, and that the conditional logic correctly distinguishes 0FC from legacy anchor channels to avoid invalid transactions or failed force-closes.

Security signals we found

01

Protocol-specific transaction version change (v2 -> v3) for 0FC channels

02

Witness weight reduction for P2A anchor inputs

03

Conditional skipping of holder-keyed anchor signature for 0FC channels

04

Fee-sufficiency check retained for commitment transactions

Risk score

Why this scored 42/100

Our methodology →
Potential impact 12/30
Exploitability 8/25
Stealth signal 6/15
Affected reach 7/15
Confidence 6/10
Evidence quality 3/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.