Bitcoin Core testnet receives major memory upgrade with cluster mempool design in v31.0rc4

Bitcoin’s mempool is the queue where transactions wait before miners pick them up and add them to a block. When the network gets busy, this waiting room becomes a competition for space, usually settled by fees.

Cluster-based mempool design

The new design changes how Bitcoin Core organizes that queue. Instead of relying on older transaction handling rules that could be clunky around related transactions, the updated system groups transactions into clusters. The default cap is 64 transactions per cluster and 101 kB in size.

Grouping related transactions gives nodes a cleaner way to judge which transaction packages are worth including, particularly when fees and dependencies become complex.

What developers say it improves

The cluster mempool model is intended to improve three areas at once: block transaction selection, fee efficiency, and handling for more complex transaction packages.

In practical terms, nodes should be better at choosing transactions that make economic sense without getting tripped up by package complexity. This is relevant for wallet software, miners optimizing block revenue, and developers working with advanced transaction flows.

Tighter replacement-by-fee rules

The update also tightens how replacement transactions work. Users can still swap out a pending transaction with a higher-fee version, but the replacement now has to improve the mempool’s overall fee profile. The change is designed to make the replacement-by-fee process more disciplined, potentially reducing some edge-case spammy behavior while preserving fee bumping as a practical tool.

Beyond “memory”: smarter transaction handling

Calling it a memory upgrade is accurate, but it also reflects a broader shift. The focus is on making the mempool smarter by moving to cluster-based logic.

Bitcoin Core is testing a framework that could better support transaction package relay and more nuanced fee markets over time. For infrastructure providers, the key point is that improved internal mempool logic can affect downstream outcomes such as wallet user experience, miner incentives, and transaction reliability during congestion.

Privacy-oriented networking improvements

Early coverage of the release notes also points to privacy-oriented networking improvements involving Tor and I2P. These tools are intended to help users and nodes connect more privately across the internet.

While fee mechanics may draw more attention, the privacy and resilience aspects are part of the same broader effort to refine network “plumbing” rather than focus on headline-grabbing changes.

Why it matters

A mempool redesign may not immediately translate into visible market charts, but it targets one of the network’s most important pressure points: how transactions compete for inclusion. If testnet feedback is positive, the cluster mempool approach could become an under-the-hood change that improves fee handling and transaction management across the stack.