We are upgrading our Bitcoin infrastructure from Bitcoin Core v31.1 to v32.1. This is a new major release (v32.0 was tagged but never formally released, so v32.1 is the first official 32.x version). It contains no consensus changes and carries no fork or chain split risk. It includes performance improvements, a faster fee estimator, and several RPC response changes that may affect applications parsing mempool, fee, or deployment data. Please review the RPC changes below before the maintenance window. During the maintenance window, brief interruptions to RPC availability may occur.
RPC Changes: • Mempool RPCs — deprecated fields removed. getrawmempool, getmempoolancestors, getmempooldescendants, and getmempoolentry no longer return the bip125-replaceable field. getmempoolinfo no longer returns the fullrbf field. Full RBF has been the default behavior since v28. • Mempool RPCs — new vsize fields. getrawmempool, getmempoolentry, testmempoolaccept, and submitpackage now return vsize_adjusted (sigop-adjusted virtual size, used for policy) and vsize_bip141 (raw BIP141 virtual size). The existing vsize field is now deprecated; it has always returned the sigop-adjusted value. Use vsize_adjusted to keep current behavior or vsize_bip141 for the true BIP141 size. • getrawtransaction — new field. Now includes vsize_adjusted when the transaction is in the mempool. • estimatesmartfee — new estimator. Fee estimates now combine the existing block-policy estimator with a new mempool-based estimator, returning the lower of the two. Users may see lower fee estimates than before. A new optional options argument accepts fee_rate_estimator (auto, block_policy, or mempool_policy) and verbosity; pass block_policy to keep the previous behavior. Successful auto responses now include an estimator field. • sendrawtransaction, testmempoolaccept, submitpackage — richer errors. The bad-txns-nonstandard-inputs rejection now includes additional debug detail explaining why the inputs are non-standard. The error code itself is unchanged.