LND Tests A Guardrail Against Extreme External Bitcoin Fee Estimates
LND’s October 22 launch candidate brings consideration to a quiet supply of pockets threat: exterior price estimates that software program treats too generously. The 0.21.5 growth notes describe a ceiling for values acquired via an exterior price API, alongside fixes to different node operations.
TL;DR
- The revealed construct is v0.21.5-beta.rc1, a pre-release.
- The price change limits excessive estimates equipped by an exterior service.
- Release verification and utility testing reply completely different questions.
A distant estimate wants limits earlier than it reaches the pockets
The release notes say exterior estimates beforehand had a decrease sure with out the corresponding higher sure. The documented restore limits the estimate earlier than it will possibly move into fee-sensitive pockets operations.
The associated change applies a ceiling of 10,000 satoshis per digital byte and in addition bounds the API’s minimum-relay estimate. That ceiling is an extreme-value guardrail. It is just not a press release that such a price is regular, economical or required by present community situations.
A price estimate is an enter to a call, not an instruction that should be obeyed at any price. A service can return an unusable worth due to an error, a modified information format or a compromised dependency. Bounding the enter limits a method that an upstream downside can affect a pockets.
The bigger operational subject connects with Bitcoin Core’s revised disclosure process: software program that handles cash wants each a way for locating issues and a path for getting repairs into use.
A candidate construct nonetheless wants proof from its deployment setting
The GitHub release page identifies the construct as a pre-release and says it requires no database migration. It supplies signature and binary-verification directions. Those particulars assist checking what was downloaded; they don’t show the way it will behave in each node configuration.
The notes additionally describe a local SQL connection-pool impasse repair. That issues as a result of node reliability will depend on storage habits in addition to community communication. A course of that continues to be working whereas requests cease finishing can nonetheless fail the purposes relying on it.
Testing a candidate subsequently must cowl the service’s precise work: receiving requests, accessing storage, dealing with failures and restarting cleanly. The absence of a database migration removes one class of change, but it surely doesn’t show that each interplay with present information is unchanged.
For cost suppliers, that’s distinct from the custody controls explored in shared-key Bitcoin lending. Keeping signing authority safe and conserving a cost node functioning are separate tasks.
The similar distinction explains why custody and recovery arrangements can not substitute software program upkeep. This candidate affords particular modifications to judge. The closing launch resolution and an operator’s deployment resolution stay further steps.
Written by the News Desk and edited by Samuel Rae.