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

Merge pull request #11480 from Roasbeef/pub/restored-force-close

Public commit record

What the developer wrote

Authored by Olaoluwa Osuntokun

73/100 · Adequate
Merge pull request #11480 from Roasbeef/pub/restored-force-close

lnwallet: reject force close for restored channels
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This change fixes a bug where LND could try to force-close a Lightning channel that had been restored from a Static Channel Backup (SCB) even though the local node does not actually have a current commitment transaction to broadcast. In Bitcoin Lightning, force-closing without the right transaction can lead to broadcasting an outdated state, which the remote party could punish as a protocol violation (a 'justice transaction'), potentially causing loss of funds. The patch now rejects force-close requests for restored channels and logs the situation clearly instead of pretending a close transaction was published.

Recommended action

Apply the patch. Operators using SCB/restored channels should ensure they are running a version containing this fix and should avoid manually triggering force-close on restored channels. Monitor logs for the new 'waiting for remote close' warning.

Security signals we found

01

Prevents broadcasting a force-close commitment for restored/SCB channels that lack a usable local commitment

02

Avoids potential outdated-state broadcast, which could be penalized by a counterparty via a justice transaction

03

Adds explicit error wrapping and logging for the restored-channel case

04

Adds unit tests for both the wallet-level rejection and the peer-level nil-transaction handling

Risk score

Why this scored 58/100

Our methodology →
Potential impact 18/30
Exploitability 10/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.