NBAndroidCRYPTO NEWS & MARKETS
← All analysis

MARKET ANALYSIS

Bitcoin Core 31.0: How Cluster Mempool Changes Transaction Handling

Bitcoin Core 31.0 groups connected unconfirmed transactions into clusters, changing how its mempool assesses transaction packages and replacements.

Published

Bitcoin Core 31.0 introduces a redesigned mempool, the node’s collection of unconfirmed transactions. The release notes say the cluster mempool is intended to support decisions about block-template construction, transaction eviction, relay and replacement. These are node policy and transaction-handling changes; the release notes do not present them as a change to Bitcoin’s consensus rules.

A cluster groups transactions connected through parent-child relationships. The previous ancestor and descendant size and count limits are replaced by limits on the connected cluster: by default, up to 64 transactions and 101 kB of virtual size. Operators can override these defaults. This means a transaction’s place in a connected group matters when the node evaluates the applicable limit.

The mempool also orders transactions using the fee rate at which they are expected to be mined, accounting for sets of transactions that would be included together. This ordering informs selection for block templates, eviction when the mempool is full and announcements to peers. The practical assessment therefore considers related transactions together rather than treating every transaction as an isolated fee bid.

Replacement-by-fee validation now requires a replacement to make the resulting mempool fee-rate diagram strictly better, according to the release notes. Bitcoin Core also adds RPCs for inspecting a transaction’s cluster and the mempool fee-rate diagram. These changes describe the software’s policy and tools; they do not guarantee confirmation time, fees or identical behavior across all nodes. Operators and application developers should consult the full release notes for policy details and configuration options.

Sources