Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
Bitcoin Core getaddrmaninfo RPC: Peer Inventory Guide
Bitcoin Core 26 getaddrmaninfo guide covering new and tried address-manager tables, per-network counts, diversity monitoring, privacy and diagnostic limits.
This guide explains Bitcoin Core getaddrmaninfo 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 26.0 introduced getaddrmaninfo to report how the node address manager distributes known addresses across new and tried tables for IPv4, IPv6, onion, I2P, CJDNS and all networks. New addresses are discovered but not yet successfully connected; tried addresses have succeeded before.
- Why it matters: getaddrmaninfo is a compact diagnostic for the breadth and history of peer discovery. It becomes operationally useful only when paired with live peer, reachability and long-term trend evidence.
- 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.
What this means in simple English
An RPC is a command sent to one Bitcoin Core node. It can ask that node for information or request a local action. A successful reply describes that node; it does not automatically prove what happened across the Bitcoin network.
Beginners can focus on the input, the result and the limit of that result. Operators should test the command on the exact Bitcoin Core version they run before relying on it.
Simple example
Think of the transaction as a form passed between several authorised signers. Each person or device checks the same payment details before adding approval. Passing the form around does not make the payment safe unless every signer checks what it contains.
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.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
No arguments
The RPC accepts no parameters and returns a map keyed by network. Pin the 26.0 schema because later releases may add or alter network families.
New table
new counts potential peers the node has learned but not successfully connected to. A large count can be healthy discovery or low-quality inventory; it is not availability proof.
Tried table
tried counts addresses with a successful historical connection. It does not say a peer is currently reachable, honest, recent or suitable for an outbound slot.
Network totals
Each family reports new, tried and total, with all_networks aggregating them. Compare sums and track trends while allowing for normal address-manager churn.
Diversity
Use the RPC with getpeerinfo, getnetworkinfo and configured reachability to distinguish known-address diversity from active connection diversity.
Privacy
Aggregate counts are safer than dumping addresses, but RPC access still exposes node topology and operational behaviour. Keep it authenticated and off public dashboards.
Alerts
Alert on sustained disappearance of expected networks, zero tried inventory, abrupt resets or mismatch with active peers, then investigate peers.dat, configuration and network reachability. 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 Bitcoin Core getaddrmaninfo RPC?
Bitcoin Core 26.0 introduced getaddrmaninfo to report how the node address manager distributes known addresses across new and tried tables for IPv4, IPv6, onion, I2P, CJDNS and all networks. New addresses are discovered but not yet successfully connected; tried addresses have succeeded before.
Is Bitcoin Core getaddrmaninfo RPC active or supported today?
Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Why does Bitcoin Core matter?
getaddrmaninfo is a compact diagnostic for the breadth and history of peer discovery. It becomes operationally useful only when paired with live peer, reachability and long-term trend evidence.
Do beginners need to use the technical details?
No. The command is mainly for people who operate Bitcoin Core or software connected to it. Other readers can use the article to understand what an operator or service is measuring.
Conclusion
getaddrmaninfo is a compact diagnostic for the breadth and history of peer discovery. It becomes operationally useful only when paired with live peer, reachability and long-term trend evidence.
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.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 Explained made simple. See the main facts, costs, risks and practical checks before you make a decision.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.