Why This Matters
For most of Bitcoin's existence, the mempool — the waiting room where unconfirmed transactions sit before being mined into a block — has operated on the same basic architecture. Transactions were evaluated mostly in isolation, fee bumps were clunky, and block construction left money on the table.
Bitcoin Core version 31.0, officially released on April 19, 2026, changes that. It ships cluster mempool, a ground-up redesign of how nodes organize, prioritize, and evict pending transactions. Alongside it comes private broadcasting — a single configuration flag that routes all transaction announcements through Tor or I2P, removing clearnet IP exposure entirely.
Neither feature is flashy. Neither will move the price tomorrow. But together, they represent the most significant upgrade to Bitcoin's transaction infrastructure in years.
Cluster Mempool: What Actually Changed
Under the old model, Bitcoin nodes tracked individual transactions and their parent-child relationships through a topology-limited structure. This created problems. Replace-by-fee (RBF) decisions were imprecise. Block template construction — the process by which miners select which transactions to include — often missed optimal fee combinations. Complex transaction packages were difficult to evaluate correctly.
Cluster mempool replaces this with a new paradigm: transactions are organized into bounded clusters of up to 64 transactions or 101 kilobytes. Within each cluster, the node can compute the optimal ordering and fee structure far more efficiently.
What This Means in Practice
- Better block construction. Miners using v31 nodes will build more profitable blocks, capturing fee revenue they were previously leaving behind.
- Smarter eviction. When the mempool is full, the node can now drop the genuinely least valuable clusters instead of making rough approximations.
- Cleaner RBF. Replacement transactions are evaluated against their entire cluster context, not just the single transaction being replaced. This makes fee bumping more reliable for users and wallets.
- Package relay foundations. Cluster mempool sets the stage for future improvements in how multi-transaction packages are relayed across the network, a prerequisite for more advanced Lightning Network and Layer 2 settlement patterns.
The cluster mempool was opt-in during the release candidate phase but ships as the default in the production release. Every v31 node runs it.
Private Broadcasting: IP Privacy by Default
The second headline feature is the -privatebroadcast option. When enabled, a node will send all transaction announcements exclusively through Tor or I2P anonymity networks. Your IP address never touches the clearnet when you broadcast a transaction.
This matters because transaction broadcasting has long been a privacy weak point. Sophisticated observers could correlate a transaction's first appearance on the network with the IP address of the node that broadcast it — linking on-chain activity to real-world identity.
Previous versions of Bitcoin Core supported Tor connections, but configuring them correctly required manual setup. v31 reduces it to a single flag in bitcoin.conf. The release also adds two new RPCs: getprivatebroadcastinfo to monitor privately broadcast transactions, and abortprivatebroadcast to remove transactions from the private broadcast queue.
Other Notable Changes
- Default database cache increased from 450 MiB to 1024 MiB on systems with more than 4 GB of RAM, improving initial block download and general node performance.
- GUI upgraded to Qt 6.8, modernizing the desktop interface.
- Embedded ASMap data (created March 5, 2026) ships with the binary for the first time, enabling autonomous system-aware peer diversification without needing an external file.
-paytxfeeandsettxfeeremoved after deprecation in v30.0. Wallets should use per-transactionfee_ratearguments or rely on the built-in fee estimator.
Who Needs to Act
Node operators: Upgrade when comfortable. The cluster mempool is a consensus-compatible change — it doesn't alter block validation rules — so there's no hard fork or soft fork involved. But running v31 means your node makes better decisions about transaction relay and block construction.
Miners and mining pools: The improved block template algorithm is a direct revenue optimization. Pools still running v30 or earlier are leaving sats on the table.
Wallet developers: The removal of settxfee means any wallet still using that RPC will break. Migrate to per-transaction fee rate specification.
Privacy-conscious users: Enable -privatebroadcast if you run a full node. It's the lowest-effort privacy upgrade Bitcoin has ever shipped.
Bitcoin Gate Take
Bitcoin Core v31.0 is the kind of release that won't generate headlines on trading desks but will be cited in technical retrospectives for years. Cluster mempool solves a class of problems that have constrained fee market efficiency since Bitcoin's early days. Private broadcasting lowers the privacy floor for every node operator willing to flip a switch. For anyone running a node — and if you're serious about Bitcoin, you should be — this upgrade is not optional. It's overdue.