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

Merge pull request #11212 from ziggie1984/disable-legacy-channels

Public commit record

What the developer wrote

Authored by ziggieXXX

58/100 · Thin
Merge pull request #11212 from ziggie1984/disable-legacy-channels

multi: stop opening legacy channels
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This change stops LND from opening new Lightning channels using the old 'legacy' commitment format. The legacy format makes it harder to recover funds if something goes wrong, because the money owed to you is tied to a secret key that changes with each channel state. From now on, LND will either use a safer default or refuse the channel open. Existing legacy channels keep working normally; only brand-new legacy channels are blocked.

Recommended action

Deploy this patch to prevent new legacy channels from being opened. No urgent incident response is required because existing legacy channels continue to operate, but operators should consider migrating liquidity to modern commitment types over time. Review any custom tooling that explicitly requests CommitmentType_LEGACY, as it will now fail.

Security signals we found

01

Prevents opening new channels with the legacy commitment type, whose tweaked to_remote output complicates data-loss recovery

02

Closes a negotiation path where an empty channel_type TLV bypassed feature checks and forced a legacy channel

03

Adds explicit RPC and wire rejection with a dedicated error code

04

Deprecates the dev-only protocol.legacy.committweak option that disabled static remote key signalling

Risk score

Why this scored 62/100

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