Bitcoin Core estimatefee RPC: Deprecated Fee Estimate Guide

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

Deprecated interface

The release documentation explicitly directed users to estimatesmartfee. Historical integrations may still expose estimatefee, but new code should not build policy around its scalar result. Version-pin any legacy caller and create a migration test that compares availability, units and fallback decisions rather than merely renaming the method.

Target meaning

nblocks is the intended horizon for beginning confirmation, not a service guarantee. A block interval is stochastic and fee markets change after estimation. Record requested target, node time, chain height, estimator age and returned value so a later confirmation outcome can be interpreted rather than blamed on one opaque number.

BTC per kilobyte units

The returned numeric rate is BTC per kilobyte and uses virtual size for witness discounting. Convert once to integer satoshis per virtual byte under an explicit rounding rule, then multiply by final vsize. Never treat the result as a total fee, BTC per byte or satoshis per kilobyte.

Negative sentinel values

Any negative result signals that the estimator lacks adequate history; minus one for target one is expected. Reject all negative rates before arithmetic or JSON serialisation. A fallback should be a reviewed fee policy with maximum and minimum limits, not zero, absolute value or the last indefinitely cached estimate.

Estimator data quality

A newly started, isolated or low-traffic node may have insufficient local observations. Mempool eviction, restart and fee-estimate file compatibility affect data. Monitor estimator readiness and compare multiple independent nodes, but avoid averaging incompatible modes or stale observations into a number that appears more certain.

Transaction-size dependency

A fee rate becomes a total only after input types, outputs, signatures and witness are known closely enough to estimate vsize. Coin selection can change size after the rate is chosen. Recalculate on the fully funded and signed candidate, verify fee and change, and reject totals above an approved exposure ceiling.

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

estimatefee is a historical scalar estimator with important sentinel and unit traps. Safe legacy handling rejects unavailable values, uses virtual-size arithmetic and moves deliberately to a richer estimator with explicit fallback policy.