LND pre-release limits external fee estimates to 10,000 sat/vB
LND published v0.21.5-beta.rc1 on October 22. The candidate adds guardrails for external fee estimates and fixes a native SQL connection-pool deadlock. It is a pre-release and requires no database migration.
TL;DR
- Version: v0.21.5-beta.rc1 pre-release.
- Change: caps external fee estimates to limit extreme inputs.
- Note: release verification confirms download integrity, not runtime behavior.
A remote estimate needs limits before it reaches the wallet
The release notes document that external fee estimates previously had only a lower bound. The change introduces an upper bound of 10,000 satoshis per virtual byte and bounds the API’s minimum-relay estimate. The ceiling acts as an extreme-value guardrail rather than guidance on normal fee levels.
Fee estimates are inputs to decisions. Services can return unusable values due to errors, data format changes, or compromised dependencies. Bounding inputs limits how upstream problems can influence wallet behavior. The broader operational point aligns with Bitcoin Core’s revised disclosure process: money-handling software needs both effective problem discovery and a path to deploy repairs.
A candidate build still needs evidence from its deployment setting
The GitHub release page marks the build as a pre-release and provides signature and binary-verification steps. These confirm what was downloaded but do not prove behavior across different node configurations. The notes describe a native SQL connection-pool deadlock fix that affects reliability because a process can remain running while requests stop completing.
Testing should reflect actual operations: receiving requests, accessing storage, handling failures, and restarting cleanly. The absence of a database migration removes one change category but does not guarantee unchanged interactions with existing data. For payment providers, custody controls such as shared-key Bitcoin lending differ from keeping a payment node operational. Custody and recovery arrangements do not replace software maintenance. The candidate introduces specific changes to evaluate, and both the final release decision and an operator’s deployment decision remain separate steps.
Authors credited by the source: NewsBTC Editorial Team
Published by Holder based on an external source.



