Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£867.74
EST. MONTHLY
203
DAYS
EST. ROI
This guide explains Bitcoin Core getmempoolentry 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 getmempoolentry returned the local mempool record for one transaction ID. Its historical fields covered virtual size, actual and modified fees, admission time and height, ancestor and descendant package aggregates, witness transaction ID and direct unconfirmed dependencies.
- Why it matters: getmempoolentry is a precise local-policy record when sampled carefully. Reliable use preserves historical units and inclusive package semantics while treating membership and every returned value as transient.
- Current position: Bitcoin Core 0.16.0 getmempoolentry returned the local mempool record for one transaction ID.
Bitcoin Core getmempoolentry RPC in simple English
Bitcoin Core getmempoolentry RPC: Validate a 32-byte transaction ID and expect not-found when the transaction confirms, is evicted, replaced or was never accepted locally.
Simple example
A miner is checking Bitcoin Core getmempoolentry RPC. Recheck the active chain and replacement evidence before classifying failure. Repeated retries cannot restore a record that policy has removed.
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.
Membership requirement
Validate a 32-byte transaction ID and expect not-found when the transaction confirms, is evicted, replaced or was never accepted locally. Recheck the active chain and replacement evidence before classifying failure. Repeated retries cannot restore a record that policy has removed.
Virtual size and fees
size is BIP 141 virtual size, while fee is BTC and modifiedfee includes local mining-priority deltas. Keep units explicit and calculate fee rates consistently. Do not use modified fees for customer accounting or confuse virtual bytes with serialised network bytes.
Admission context
time is the node-local Unix admission time and height is the chain height at admission. Neither is a network broadcast timestamp. Restarts and mempool persistence can affect interpretation, so retain node version, uptime and tip context with incident evidence.
Package aggregates
Ancestor and descendant counts include the described transaction in their aggregate totals. Size and fee aggregates cover the local in-mempool package. They help diagnose policy and selection but do not supply a topological order or guarantee that the whole package will be mined.
Dependencies and identity
depends lists direct unconfirmed parent txids and wtxid identifies witness-inclusive serialisation. Build deeper graphs through bounded queries and verify decoded inputs. A txid match alone cannot distinguish witness variants in every diagnostic workflow.
Races and access
Mempool state can change immediately after the response. Avoid long-lived caches and unrestricted public lookups that expose local inventory or invite expensive polling. Authenticate RPC and record a coherent snapshot time across related calls.
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 getmempoolentry RPC?
Bitcoin Core getmempoolentry RPC: Validate a 32-byte transaction ID and expect not-found when the transaction confirms, is evicted, replaced or was never accepted locally.
For Bitcoin Core getmempoolentry RPC, what should a beginner know about membership requirement?
Validate a 32-byte transaction ID and expect not-found when the transaction confirms, is evicted, replaced or was never accepted locally.
For Bitcoin Core getmempoolentry RPC, what should a beginner know about virtual size and fees?
size is BIP 141 virtual size, while fee is BTC and modifiedfee includes local mining-priority deltas.
For Bitcoin Core getmempoolentry RPC, what should a beginner know about admission context?
time is the node-local Unix admission time and height is the chain height at admission.
Conclusion
getmempoolentry is a precise local-policy record when sampled carefully. Reliable use preserves historical units and inclusive package semantics while treating membership and every returned value as transient.
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.