LND sets 10,000 sat/vB ceiling on external fee estimates in pre-release
LND’s October 22 release candidate highlights a wallet risk from permissive external fee estimates and introduces guardrails and reliability fixes. The 0.21.5 notes outline a ceiling on external fee inputs and clarify that this pre-release needs deployment-specific testing despite no database migration.
Key points
- Version: v0.21.5-beta.rc1 is a pre-release.
- Fee input limits: External fee estimates now have an upper bound of 10,000 sat/vB and a bounded minimum-relay estimate. This prevents unusable values from propagating into wallet operations due to upstream errors or compromised dependencies.
- Operational scope: The ceiling is an extreme guardrail, not guidance on normal or economical fees.
- Security and process: The change aligns with the need for clear paths from problem discovery to repair deployment in money-handling software, reflecting priorities seen in Bitcoin Core’s revised disclosure process.
- Reliability fix: A native SQL connection-pool deadlock fix targets scenarios where a node appears alive but stops completing requests, emphasizing storage and concurrency stability alongside network behavior.
- Verification vs testing: Release signatures and binary checks confirm download integrity. They do not validate behavior across diverse node configurations. Absence of a database migration reduces one risk category but does not guarantee unchanged interactions with existing data.
- Operational responsibility: Payment node uptime and behavior remain separate from custody arrangements. Custody, recovery, and shared-key lending do not replace software maintenance and upgrade decisions.
Implications for operators
- Risk reduction: Bounding external fee inputs lowers exposure to fee API anomalies influencing wallet spend decisions.
- Testing focus: Evaluate request handling, storage access, failure handling, and clean restarts in the actual deployment environment before production rollout.
- Upgrade planning: Treat this candidate as an opportunity to validate fixes and identify configuration-specific issues ahead of final release.
Authors credited by the source: NewsBTC Editorial Team
Published by Holder based on an external source.
