Problem
fee_rate_sat_vb is currently defined statically in the configuration file. Updating it requires changing the configuration and restarting or redeploying the node.
Bitcoin network fees can change significantly over time, so a static value can quickly become outdated. This may result in transactions being overpaid, underpriced, or delayed.
Proposed solution
Allow fee_rate_sat_vb to be provided or updated dynamically at runtime instead of relying exclusively on the configuration file.
Possible approaches:
Accept fee_rate_sat_vb as an API request parameter for operations that create Bitcoin transactions.
Expose an API endpoint for updating the node’s current fee rate.
Retrieve the fee rate from a configurable fee estimator.
The existing configuration value should remain available as a default or fallback for backward compatibility.
Expected behavior
Bitcoin transactions can use a dynamically supplied fee rate.
Updating the fee rate does not require restarting the node.
A dynamically supplied value takes precedence over the configured fallback.
Invalid or out-of-range values are rejected with a clear error.
Existing deployments using only the configuration file continue to work.
Tests and API documentation are updated accordingly.
Problem
fee_rate_sat_vb is currently defined statically in the configuration file. Updating it requires changing the configuration and restarting or redeploying the node.
Bitcoin network fees can change significantly over time, so a static value can quickly become outdated. This may result in transactions being overpaid, underpriced, or delayed.
Proposed solution
Allow fee_rate_sat_vb to be provided or updated dynamically at runtime instead of relying exclusively on the configuration file.
Possible approaches:
Accept fee_rate_sat_vb as an API request parameter for operations that create Bitcoin transactions.
Expose an API endpoint for updating the node’s current fee rate.
Retrieve the fee rate from a configurable fee estimator.
The existing configuration value should remain available as a default or fallback for backward compatibility.
Expected behavior
Bitcoin transactions can use a dynamically supplied fee rate.
Updating the fee rate does not require restarting the node.
A dynamically supplied value takes precedence over the configured fallback.
Invalid or out-of-range values are rejected with a clear error.
Existing deployments using only the configuration file continue to work.
Tests and API documentation are updated accordingly.