Bitcoin Core development already includes the final integration of Cluster Mempool for a future version 31.0. This week, a merge for pull request #34616 was performed on the main code branch of the software. Changes led by developer Suhas Daftuar.
This is an update that replaces the currently pending transaction management system. For group-based data structures. The purpose is to organize the node’s memory. More efficient and technological.
From a technical perspective, Cluster Mempool changes the way nodes process transactions. Currently, software tracks individual “ancestor-descendant” relationships. this Imposing strict limits such as up to 25 linked transactions.
The new architecture is Related transactions within a cluster Independent. This structure allows nodes to scan the entire group without current count limits. This makes it easier to handle complex operations, especially in upper layer protocols that rely on multiple linked transactions.
system efficiency exists within the linearization algorithm. This process reorders transactions within each cluster to prioritize transactions that maximize fees for miners. For users, this solves the problem of calculating the RBF (replacement by fee) and CPFP (child pays father) functions.
In this way, having an optimized fill order allows the wallet to accurately calculate the required fees, reducing the risk of overpayment.
When will Bitcoin Core 31.0 be available?
Bitcoin Core version 31.0 is Late 2026following normal software update cycles.
The development team is working carefully Because we need to reduce risk. As reported by CriptoNoticias, an error was identified during the version 30 cycle that affected the management of transactions in certain wallets. Therefore, the possibility of downloading was eliminated.
This error can also lead to loss of funds, highlighting the importance of following the pre-launch testing phase.
Currently version 30.1 is already available in the repository,the Bitcoin.org portal actively maintains version 28.1 As the main download recommendation. This is because we prefer to recommend versions that have been widely tested over a long period of time, with thousands of nodes running without any major issues reported.
Version 28.1 (released in January 2025, with subsequent patches) If you have accumulated more than one year of actual usage on the network.This makes it more reliable for new users and for those running critical nodes (full node).
It is common practice in the ecosystem to suggest versions with longer validation times to ensure users are working with software that is widely known to be stable before moving to a new architecture.
