Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.31
EST. MONTHLY
205
DAYS
EST. ROI
This guide explains Bitcoin Core getmempoolcluster RPC in plain English. It shows what the command does, what its result means and what it cannot prove.
TL;DR
- What it is: Bitcoin Core 31.0 introduced getmempoolcluster alongside the new cluster mempool. Given a transaction identifier present locally, the RPC returns its entire connected component, total adjusted weight and transactions grouped into chunks in mining order.
- Why it matters: getmempoolcluster exposes the structure Core 31 uses for policy decisions. Reliable tools preserve its local, dynamic and adjusted-weight context instead of flattening it into a universal transaction ranking.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Bitcoin Core getmempoolcluster RPC in simple English
Bitcoin Core getmempoolcluster RPC: Transactions share a cluster when connected by any combination of in-mempool parent and child relationships. The default policy limits clusters to 64 transactions and 101 kB virtual size.
Simple example
A miner is checking Bitcoin Core getmempoolcluster RPC. It does not promise selection by other miners or even this node’s next template after the mempool changes.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Input
The sole required txid must identify a transaction currently in this node’s mempool cluster. Validate hexadecimal form and handle not-found separately from transport or permission errors.
Cluster meaning
Transactions share a cluster when connected by any combination of in-mempool parent and child relationships. The default policy limits clusters to 64 transactions and 101 kB virtual size.
Adjusted weight
clusterweight is sigops-adjusted weight under BIP 141 and the configured bytespersigop. It is not necessarily raw transaction weight and must retain its exact unit.
Chunks
The chunks array is already in mining order. Each chunk supplies combined fee, adjusted weight and an ordered list of transaction identifiers.
Dynamic snapshot
Arrival, removal, replacement, confirmation, reorganisation and configuration can change membership and ordering immediately. Timestamp and identify the node and tip for every stored result.
Interpretation limits
The output helps explain local mining, eviction, relay and RBF decisions. It does not promise selection by other miners or even this node’s next template after the mempool changes.
Analytics
Use integer fee and weight values, verify every listed txid, avoid sorting away authoritative chunk order, detect duplicates and compare repeated snapshots to explain topology transitions. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Frequently asked questions
What is the main point of Bitcoin Core getmempoolcluster RPC?
Bitcoin Core getmempoolcluster RPC: Transactions share a cluster when connected by any combination of in-mempool parent and child relationships.
For Bitcoin Core getmempoolcluster RPC, what should a beginner know about input?
The sole required txid must identify a transaction currently in this node’s mempool cluster.
For Bitcoin Core getmempoolcluster RPC, what should a beginner know about cluster meaning?
Transactions share a cluster when connected by any combination of in-mempool parent and child relationships.
For Bitcoin Core getmempoolcluster RPC, what should a beginner know about adjusted weight?
clusterweight is sigops-adjusted weight under BIP 141 and the configured bytespersigop.
Conclusion
getmempoolcluster exposes the structure Core 31 uses for policy decisions. Reliable tools preserve its local, dynamic and adjusted-weight context instead of flattening it into a universal transaction ranking.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.