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

Merge pull request #11223 from gijswijs/legacy-dust-retribution-fix

Public commit record

What the developer wrote

Authored by ziggieXXX

73/100 · Adequate
Merge pull request #11223 from gijswijs/legacy-dust-retribution-fix

lnwallet+contractcourt: skip trimmed HTLCs in legacy breach retribution
✓ 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 update fixes a bug in how LND handles old-style punishment transactions when a channel partner tries to cheat. Previously, tiny (dust) HTLCs were left as blank placeholder entries in the punishment data, which could cause the node to crash or behave incorrectly when trying to claim funds back. The fix removes those blank entries and adds safety checks further down the line.

Recommended action

Apply the patch and ensure nodes are upgraded, especially watchtowers or nodes that rely on automatic justice transaction creation for old channels. Monitor logs for the new warning messages about skipped HTLCs.

Security signals we found

01

nil-pointer dereference risk in breach retribution path

02

legacy revocation log handling inconsistency with modern format

03

defensive hardening added for trimmed/dust HTLCs

04

release notes describe the change as a bug fix for breach retributions

Risk score

Why this scored 56/100

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