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

Add 0-reserve to the internal API of V2 channels

Public commit record

What the developer wrote

Authored by Leo Nash

80/100 · Strong
Add 0-reserve to the internal API of V2 channels

Note that this currently does not match the spec as we use an odd TLV
for the `disable_channel_reserve` field in `open_channel2` and
`accept_channel2` msgs.

If the counterparty does not understand this field, that's ok as it just
means that the counterparty will not send some HTLCs we would have
accepted.

We make the assumption that the counterparty will not complain if we
send a HTLC that pushes their balance below our selected reserve; this
could happen if the counterparty is the funder of the channel. They
should not complain because if we push them below our selected reserve,
this is our problem.
✓ 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 adds an internal-only option for V2 Lightning channels to disable the usual channel reserve requirement. It is marked by the authors as not matching the official protocol specification, using a temporary experimental message field. Because it is internal and not exposed to end users, the immediate security risk is limited, but it introduces assumptions about how peers will behave when reserves are skipped.

Recommended action

Treat as a feature-in-progress rather than an active vulnerability. Reviewers should verify that the public API does not expose zero-reserve channels until the spec-compliant mechanism is finalized, and ensure HTLC acceptance logic enforces the correct reserve when the counterparty is the funder. Monitor for follow-up commits that remove the experimental odd-TLV or add spec-compliant negotiation.

Security signals we found

01

Non-spec-compliant protocol field (odd TLV 103) added to dual-funding channel messages

02

Channel reserve, a standard economic safety mechanism, can be set to zero internally

03

Authors assume counterparties will tolerate HTLCs that push balance below reserve

04

Change is internal-only; no public user-facing API appears in the diff

05

Extensive test coverage added for message encoding with the new flag

Risk score

Why this scored 31/100

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