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 getprivatebroadcastinfo 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 getprivatebroadcastinfo to inspect transactions currently being broadcast through the optional Tor or I2P private-broadcast mechanism. The no-argument response includes transaction identifiers, complete raw hex and per-peer timing and acknowledgement data.
- Why it matters: getprivatebroadcastinfo makes the privacy queue observable, but its response can itself erode privacy. Use it through tightly controlled tooling that extracts only the minimum operational signal and preserves uncertainty beyond the local node.
- 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 getprivatebroadcastinfo RPC in simple English
Bitcoin Core getprivatebroadcastinfo RPC: The RPC reports the local node’s current private-broadcast queue only. An absent transaction may have completed, been aborted or never entered this queue.
Simple example
A node operator is checking Bitcoin Core getprivatebroadcastinfo RPC. An absent transaction may have completed, been aborted or never entered this queue. Check mempool and chain state separately.
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.
- 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.
Scope
The RPC reports the local node’s current private-broadcast queue only. An absent transaction may have completed, been aborted or never entered this queue; check mempool and chain state separately.
Transaction fields
Each record includes txid, wtxid and serialized transaction hex. Preserve the distinction between witness and non-witness identity and never expose raw hex unnecessarily.
Peer fields
Every peer entry includes address and the epoch time selected for sending, plus an optional received time when the peer acknowledged reception.
Acknowledgement meaning
A received timestamp shows peer acknowledgement in this mechanism; it does not prove network-wide relay, miner receipt, mempool permanence or confirmation.
Privacy risk
Peer addresses and timing can reveal network topology and transaction-origin workflow. Restrict the RPC, minimise retention, redact dashboards and avoid third-party telemetry.
Monitoring
Track queue age, peer attempts and acknowledgement latency using aggregate metrics. Alert on stalls without copying full transaction hex or peer lists into general logs.
Lifecycle
Query before and after send or abort actions, correlate by both identifiers, tolerate entries disappearing during the call and classify completion, abort, error and unknown state separately. 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 getprivatebroadcastinfo RPC?
Bitcoin Core getprivatebroadcastinfo RPC: The RPC reports the local node’s current private-broadcast queue only.
For Bitcoin Core getprivatebroadcastinfo RPC, what should a beginner know about scope?
The RPC reports the local node’s current private-broadcast queue only. An absent transaction may have completed, been aborted or never entered this queue.
For Bitcoin Core getprivatebroadcastinfo RPC, what should a beginner know about transaction fields?
Each record includes txid, wtxid and serialized transaction hex. Preserve the distinction between witness and non-witness identity and never expose raw hex unnecessarily.
For Bitcoin Core getprivatebroadcastinfo RPC, what should a beginner know about peer fields?
Every peer entry includes address and the epoch time selected for sending, plus an optional received time when the peer acknowledged reception.
Conclusion
getprivatebroadcastinfo makes the privacy queue observable, but its response can itself erode privacy. Use it through tightly controlled tooling that extracts only the minimum operational signal and preserves uncertainty beyond the local node.
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.