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

Merge pull request #11380 from ziggie1984/fix-update-fee-floor

Public commit record

What the developer wrote

Authored by ziggieXXX

73/100 · Adequate
Merge pull request #11380 from ziggie1984/fix-update-fee-floor

lnwallet: reject fee updates below commit floor
✓ 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 to the Lightning Network Daemon (LND) fixes several related bugs around commitment transaction fee rates for anchor-style channels. It prevents LND from accepting or sending fee updates below the protocol minimum, clamps a configuration value that could overflow and silently turn into a much lower fee, and cleans up a wallet reservation leak when an incoming channel open is rejected. The practical effect is to stop channels from being created or updated with fees so low that they cannot carry payments, and to prevent a misconfiguration from accidentally disabling the intended fee cap.

Recommended action

Upgrade nodes running LND to a version containing this commit, especially if they use anchor or taproot channels with non-default max-commit-fee-rate-anchors settings. Review any channels opened with fee rates below 253 sat/kw, as they may now be unable to update fees and could require cooperative closure.

Security signals we found

01

Rejection of sub-floor commitment fee updates before they are logged or signed

02

Integer-overflow mitigation for max-commit-fee-rate-anchors via clamping

03

Resource-leak fix for declined incoming channel reservations

04

Defense-in-depth floor check retained inside validateCommitmentSanity

05

Release notes explicitly describe the security/robustness relevance

Risk score

Why this scored 59/100

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