Bitcoin Core estimatesmartfee RPC: Fee-Mode Operator Guide

This guide explains Bitcoin Core estimatesmartfee RPC in plain English. It shows what the command does, what its result means and what it cannot prove.

Requested and returned targets

conf_target expresses the desired blocks, but the returned blocks field can show a clamped or otherwise supported horizon. Record and display both values. A caller that ignores returned blocks can tell users it priced for one target while the estimator actually supplied evidence for another.

Conservative versus economical

CONSERVATIVE uses longer history and may produce a higher, steadier rate. ECONOMICAL reacts more to short-term drops and can underperform if conditions rise. UNSET defaults to conservative in the historical interface. Choose mode from payment urgency and replacement capability, not as an invisible global cost switch.

Optional result fields

feerate is optional and errors may be present when the estimator lacks enough history. Validate the object schema and branch explicitly on availability. Do not coerce a missing field to zero, and retain error text only after removing information that could reveal private operational context.

Units and rounding

The rate is BTC per kilobyte, based on BIP 141 virtual size. Convert using fixed decimal arithmetic to integer satoshis per virtual byte and round according to relay and application policy. Multiply by final vsize, then independently compare the transaction’s actual input-minus-output fee before signing.

Readiness and independence

Estimator output depends on the node’s observations, uptime, mempool policy and saved history. A newly restored or isolated node may have no useful estimate. Compare a small number of independent, policy-compatible nodes and monitor divergence, but do not outsource final fee choice blindly to a public API.

Fallback and limits

Define bounded fallback rates by urgency, permitted delay and RBF policy, with a maximum total fee as well as a rate ceiling. If no estimate exists, pause high-value automated withdrawals rather than guessing. Cache only with timestamp, target, mode and short expiry so stale weekend or congestion data cannot persist unnoticed.

How specialists test it

Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.

Conclusion

estimatesmartfee provides richer context than its deprecated predecessor, but applications must still handle clamping, missing data and units. The safe fee is a bounded policy decision applied to the final transaction, not an unquestioned RPC number.