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

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 adds an upper bound: a ceiling of 10,000 satoshis per virtual byte and bounds on the API’s minimum-relay estimate. The ceiling acts as an extreme-value guardrail. Fee estimates are inputs to decisions, not instructions. Errors, format changes, or compromised dependencies can produce unusable values; bounding inputs reduces the blast radius from upstream failures. This aligns with the operational principle highlighted by Bitcoin Core’s revised disclosure process: money-handling software needs processes to find issues and deploy fixes.

A candidate build still needs evidence from its deployment setting

The GitHub release marks the build as a pre-release and provides signature and binary-verification steps. Verification checks the artifact; it does not prove behavior across node configurations. The notes also report a native SQL connection-pool deadlock fix, which addresses reliability risks where a process stays up while requests fail to complete. Testing should exercise real workloads: 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.

Operational duties for payment nodes differ from custody controls such as shared-key Bitcoin lending. Custody and recovery arrangements, including insured options noted here, do not replace software maintenance. This candidate offers specific changes to evaluate. Final release and operator deployment decisions remain separate steps.