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

Broadcast holder commitment immediately on alternative funding reorg

Public commit record

What the developer wrote

Authored by Wilmer Paulino

73/100 · Adequate
Broadcast holder commitment immediately on alternative funding reorg

We can't rely waiting on another (or the same) renegotiated funding
transaction to confirm, since it may never happen. We also don't want to
rely on the counterparty to broadcast for us, or require manual
intervention from the user, so we choose to broadcast the new holder
commitment immediately. This ensures we're able to claim funds from an
already force closed channel after an alternative funding reorg.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This change fixes a situation in the Lightning Dev Kit where, after a blockchain reorganization that undoes an alternative funding transaction, the user's own commitment transaction could fail to be broadcast automatically. Previously the code would cancel stale claims but then wait for a new funding transaction to confirm before broadcasting the user's valid commitment. If that confirmation never happened, the user might not recover funds from a force-closed channel. The patch now broadcasts the user's latest commitment immediately after such a reorg, without relying on the counterparty or manual action.

Recommended action

Treat as a recommended reliability/security fix. Users running nodes with alternative funding flows should upgrade to ensure holder commitments are broadcast promptly after reorgs that undo alternative funding transactions. Review related reorg handling paths for similar deferred-broadcast patterns.

Security signals we found

01

Funds-recovery reliability fix after blockchain reorganization

02

Automatic broadcast of holder commitment instead of relying on counterparty or user

03

Change in control flow: broadcast now occurs immediately after stale claim cancellation

04

Broadening of trigger condition from holder_tx_signed to include funding_spend_seen

05

No explicit CVE, advisory, or researcher attribution in commit or supplied references

Risk score

Why this scored 50/100

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