Neutral

LND pre-release caps external fee API estimates at 10,000 sat/vB

На русском
2 min
LND pre-release caps external fee API estimates at 10,000 sat/vB

LND’s October 22 release candidate focuses on guarding wallets from faulty external fee estimates and improving node reliability. The v0.21.5-beta.rc1 build caps remote fee inputs and fixes a SQL connection-pool deadlock. It is a pre-release that needs deployment-specific testing; binary verification does not replace operational validation.

TL;DR

  • Build: v0.21.5-beta.rc1 pre-release.
  • Fees: upper bound added to external estimates; minimum-relay estimate also bounded.
  • Ops: no DB migration; includes SQL connection-pool deadlock fix; verify downloads and test behavior separately.

External fee estimates now have upper limits before reaching the wallet

The release notes indicate external fee estimates previously had only a lower bound. The change adds a ceiling of 10,000 satoshis per virtual byte and bounds the API’s minimum-relay estimate. This creates an extreme-value guardrail so unusable values from errors, format changes, or compromised dependencies do not propagate into fee-sensitive wallet operations. The update aligns with the need, reflected in Bitcoin Core’s revised disclosure process, for both problem discovery and timely repair paths in money-handling software.

Pre-release status and operational reliability

The GitHub release page marks the build as a pre-release and states no database migration is required. It includes signatures and binary-verification steps that confirm download integrity, not behavior across node configurations. The notes also document a native SQL connection-pool deadlock fix, underscoring that node reliability depends on storage as well as network I/O. Testing should validate real workloads: request handling, storage access, failure handling, and clean restarts. Absence of a migration removes one change category but does not guarantee unchanged interactions with existing data. For payment providers, custody arrangements and key security are separate from keeping a payment node operational; maintenance and testing remain required.

Original publication

Authors credited by the source: NewsBTC Editorial Team

Published by Holder based on an external source.