Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£871.52
EST. MONTHLY
203
DAYS
EST. ROI
This guide explains Bitcoin Core getrawmempool 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 0.16.0 getrawmempool returned every transaction ID in the local memory pool. Default mode produced a simple array; verbose mode returned a potentially large object with virtual size, fees, admission metadata, ancestor and descendant aggregates, witness IDs and dependencies for each transaction.
- Why it matters: getrawmempool can expose the complete local pending set, but completeness is precisely why it requires strict access and resource controls. Its output is transient local policy state, not network consensus.
- Current position: Bitcoin Core 0.16.0 getrawmempool returned every transaction ID in the local memory pool.
Bitcoin Core getrawmempool RPC in simple English
Bitcoin Core getrawmempool RPC: Default false returns txids with no guaranteed business ordering. It is appropriate for set comparison and selecting bounded follow-up queries.
Simple example
A miner is checking Bitcoin Core getrawmempool RPC. Stream or page within the consuming service because a busy node can return a large array even if the RPC itself is one response.
Key terms in plain English
- 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.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- 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.
Terse inventory
Default false returns txids with no guaranteed business ordering. It is appropriate for set comparison and selecting bounded follow-up queries. Stream or page within the consuming service because a busy node can return a large array even if the RPC itself is one response.
Verbose cost
Verbose true duplicates a full entry object for every mempool transaction and can consume significant CPU, memory, bandwidth and parser time. Prefer getmempoolentry for known targets. Authenticate RPC and set response, concurrency and timeout limits.
Historical field units
size is virtual bytes; fee is BTC; modified and aggregate fees incorporate local prioritisation deltas; time is local Unix admission time. Counts aggregate node-local ancestor or descendant packages. Preserve these semantics and do not blend them with modern schemas silently.
Snapshot races
The mempool can change while a caller processes the result. A transaction may confirm, be replaced or evicted before a follow-up. Treat each response as an observation with node, tip and time context, and handle not-found without converting it into a false rejection.
Node disagreement
Nodes receive different transactions and apply different local policy. Compare set overlap for diagnostics, not exact equality as a health requirement. Investigate sustained divergence alongside peers, fee floors, restart history and chain state.
Privacy and retention
Bulk inventory can reveal what the node has seen and invite correlation with business activity. Keep access private, minimise retention and separate customer mappings. Do not export peer data with transaction first-seen observations unless an approved incident requires it.
How specialists test it
Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.
Frequently asked questions
What is the main point of Bitcoin Core getrawmempool RPC?
Bitcoin Core getrawmempool RPC: Default false returns txids with no guaranteed business ordering. It is appropriate for set comparison and selecting bounded follow-up queries.
For Bitcoin Core getrawmempool RPC, what should a beginner know about terse inventory?
Default false returns txids with no guaranteed business ordering. It is appropriate for set comparison and selecting bounded follow-up queries.
For Bitcoin Core getrawmempool RPC, what should a beginner know about verbose cost?
Verbose true duplicates a full entry object for every mempool transaction and can consume significant CPU, memory, bandwidth and parser time.
For Bitcoin Core getrawmempool RPC, what should a beginner know about historical field units?
size is virtual bytes. Fee is BTC. Modified and aggregate fees incorporate local prioritisation deltas.
Conclusion
getrawmempool can expose the complete local pending set, but completeness is precisely why it requires strict access and resource controls. Its output is transient local policy state, not network consensus.
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.