Neutral

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

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

LND’s October 22 release candidate highlights a wallet risk from permissive handling of external fee estimates. Version v0.21.5-beta.rc1 introduces an upper bound on externally sourced fees and includes fixes affecting node reliability.

Scope and status

  • Build: v0.21.5-beta.rc1, marked pre-release.
  • No database migration required.
  • Signatures and binary verification provided on the release page to confirm download integrity. Verification does not replace behavior testing across node configurations.

Fee estimate bounding

  • External fee estimates previously had only a lower bound. The change adds an upper bound before values reach wallet operations.
  • New ceiling: 10,000 satoshis per vbyte on external estimates, plus bounds on the API’s minimum-relay estimate.
  • Purpose: limit the impact of erroneous, malformed, or compromised external fee data on wallet decisions. The ceiling is a guardrail, not guidance on typical fees.

Operational considerations

  • Release notes emphasize that fee estimates are inputs for decision-making, not directives.
  • The update aligns with the need for clear processes to detect issues and deploy fixes in money-handling software, similar in aim to Bitcoin Core’s revised disclosure process.

Node reliability changes

  • Fix: native SQL connection-pool deadlock. Relevance: a process can appear healthy while requests stall, affecting dependent applications.
  • Testing focus for operators: validate real workloads, storage access patterns, failure handling, and clean restarts. Absence of a migration removes one risk category but does not guarantee unchanged behavior with existing data.

Operational boundaries

  • Payment node maintenance and reliability are separate from custody arrangements and key management. Controls used for shared-key Bitcoin lending or insured custody do not substitute for software maintenance.
  • This candidate introduces specific changes to evaluate; final release and deployment decisions are separate steps for maintainers and operators.

Original publication

Authors credited by the source: NewsBTC Editorial Team

Published by Holder based on an external source.