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

Create a single P2A anchor on commitment transactions in 0FC channels

Public commit record

What the developer wrote

Authored by Leo Nash

73/100 · Adequate
Create a single P2A anchor on commitment transactions in 0FC channels

Zero-fee commitment channels replace today's existing `to_local_anchor`
and `to_remote_anchor` outputs with a single `shared_anchor` output.

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 changes how Bitcoin transaction fees are handled for a new type of Lightning channel. Instead of each party having their own small 'anchor' output to bump the transaction fee later, the commit creates one shared anchor output. It also switches these zero-fee commitment transactions to use a non-standard version 3. This is part of an ongoing protocol update and does not by itself look like a security bug fix; it is more like feature construction.

Recommended action

Treat this as a protocol feature change rather than an urgent security patch. Reviewers should verify that the P2A output value calculation cannot underflow or exceed consensus limits, that version-3 transactions are accepted by relevant Bitcoin relay policy, and that the single shared anchor preserves fee-bumping rights for both channel parties. No immediate action is indicated by the commit alone.

Security signals we found

01

New P2A anchor output introduced for zero-fee commitment channels

02

Commitment transaction version changed to non-standard Version(3) for zero-fee anchor channels

03

Anchor value derived from channel value remainder and capped at 240 sat

04

Existing anchor logic retained for non-zero-fee channel types

05

No explicit bug fix, bounds check, or vulnerability disclosure language in commit message

Risk score

Why this scored 32/100

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