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

lnwallet: reject a zero CSV delay

Public commit record

What the developer wrote

Authored by Olaoluwa Osuntokun

78/100 · Adequate
lnwallet: reject a zero CSV delay

In this commit, we reject a CSV delay of zero during constraint
verification.

The CSV delay is the time the owner of a commitment must wait before
sweeping their own output, and it is the window the other party has to
respond to a breach. A delay of zero removes that window entirely and
is never a sensible value, but VerifyConstraints only bounded the delay
from above.

VerifyConstraints is the one place every delay passes through:
CommitConstraints calls it for the delay the remote party requires of
us, in both the initiator and responder roles, and the funding manager
calls it for the delay we require of the remote party. Checking for zero
there covers every channel type and both directions.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This change tightens the rules for opening Lightning payment channels by refusing a setting called the CSV delay when it is set to zero. The CSV delay is the waiting period a user must endure before reclaiming their own funds from a channel commitment, and it is also the time the other party has to punish a cheating attempt. A zero delay would remove that safety window, so the patch makes it impossible to accept or propose such a channel. The fix is applied at the single central checkpoint that all channel types and both sides of a channel pass through.

Recommended action

No immediate action beyond applying the patch is required. Operators should ensure they are running a version that includes this constraint check before opening new channels. Existing channels with a non-zero CSV delay are unaffected.

Security signals we found

01

Rejects a zero CSV delay that would eliminate the breach-remedy window

02

Centralizes the check in VerifyConstraints so all channel types and directions are covered

03

Adds explicit error type and unit test for the new constraint

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.