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

Set 0FC `HolderHTLCOutput`, `HolderFundingOutput` to require addl funds

Public commit record

What the developer wrote

Authored by Leo Nash

73/100 · Adequate
Set 0FC `HolderHTLCOutput`, `HolderFundingOutput` to require addl funds

Also set the malleability of 0FC `HolderHLTCOutput` to be the same as in
CSV anchor channels.

And add debug asserts from CSV anchor channels that also apply to P2A
anchor channels.

Co-authored-by: Matt Corallo <git@bluematt.me>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes how a Bitcoin Lightning node handles a newer channel type (zero-fee commitment transactions, or 0FC). Before the patch, the node did not recognize that 0FC channels need extra on-chain funds to broadcast certain rescue transactions, and it treated some 0FC outputs as easier to manipulate than they should be. The change makes 0FC channels behave more like the older CSV anchor channels for safety checks and fee requirements. This is a defensive correctness fix in fee-bumping logic; the commit message does not describe an active exploit.

Recommended action

Treat as a defensive fix and include in the next maintenance release. Review related 0FC paths for any other places where `supports_anchors_zero_fee_htlc_tx()` is checked without also considering `supports_anchor_zero_fee_commitments()`. No emergency response is indicated by the available materials.

Security signals we found

01

Fee-bumping requirement corrected for zero-fee commitment (0FC) channel outputs

02

Malleability classification of HolderHTLCOutput aligned with CSV anchor channels

03

Debug assertions extended to cover 0FC alongside existing zero-fee HTLC anchor checks

04

No explicit vulnerability, CVE, or exploit described in commit or supplied references

Risk score

Why this scored 57/100

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