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

Merge pull request #11334 from gijswijs/fee-ceiling-clamp

Public commit record

What the developer wrote

Authored by Yong

73/100 · Adequate
Merge pull request #11334 from gijswijs/fee-ceiling-clamp

lnwallet/chainfee: clamp web API fee estimates to a ceiling
✓ 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 commit adds an upper limit (ceiling) to fee estimates that LND pulls from an external web API. Previously, only a lower bound existed, so a malicious or malfunctioning fee API could return extremely high fee rates. Those inflated rates could then flow into wallet operations and cause users to overpay transaction fees. The patch clamps both per-block fee estimates and the minimum relay fee rate to a maximum of 10,000 sat/vbyte. It also ties the sweeper's maximum allowed fee rate to the same ceiling so the two limits stay consistent.

Recommended action

Treat this as a security hardening fix. Users relying on --fee.url should upgrade to a release containing this commit. Operators should verify their external fee API source is trustworthy and monitor logs for 'exceeds fee ceiling' warnings, which may indicate API misbehavior.

Security signals we found

01

Untrusted external input (fee API) was previously only lower-bounded, allowing unbounded high values

02

High fee estimates can propagate into wallet signing and fee-sensitive operations

03

New ceiling bounds both block-target estimates and min_relay_feerate

04

Sweeper max fee rate is now derived from the same ceiling to prevent limit divergence

05

Release notes explicitly describe security relevance: out-of-range API values could propagate into fee-sensitive wallet operations

Risk score

Why this scored 60/100

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