LND release candidate caps external fee estimates at 10,000 sat/vB

External fee estimate bounds added

The release notes describe that external fee estimates previously had only a lower bound. The update adds an upper bound before estimates influence wallet operations. The change sets a ceiling of 10,000 satoshis per virtual byte and bounds the API’s minimum-relay estimate. The ceiling functions as a guardrail against unusable values caused by service errors, format changes, or compromised dependencies. A fee estimate is an input to a decision, not an instruction. Bounding the input reduces the impact of upstream problems on wallet behavior. The change aligns with the need for robust processes to find and deploy fixes in money-handling software, reflecting broader themes noted in Bitcoin Core’s revised disclosure process.

Pre-release status and operational considerations

The GitHub release page marks the build as a pre-release and states no database migration is required. It provides signatures and binary-verification steps that confirm download integrity but do not validate behavior across all node setups. The notes include a fix for a native SQL connection-pool deadlock. Reliability depends on storage behavior and network communication: a process can appear live while failing to complete requests.

Testing should focus on real workload: receiving requests, accessing storage, handling failures, and clean restarts. The absence of a migration removes one change category but does not guarantee unchanged interactions with existing data. This operational reliability is distinct from custody design: shared-key Bitcoin lending and insured custody solutions address signing authority and recovery, not node software maintenance. Operators must evaluate the candidate’s specific changes, and both the final release decision and deployment choices remain separate steps.

Written by the News Desk and edited by Samuel Rae.