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.
Bitcoin Core getaddrmaninfo RPC: new counts potential peers the node has learned but not successfully connected to. A large count can be healthy discovery or low-quality inventory.
A node operator is checking Bitcoin Core getaddrmaninfo RPC. Pin the 26.0 schema because later releases may add or alter network families. Record source commit, binary hash, network, chain identity, configuration and dependencies.
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 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 counts addresses with a successful historical connection. It does not say a peer is currently reachable, honest, recent or suitable for an outbound slot.
Each family reports new, tried and total, with all_networks aggregating them. Compare sums and track trends while allowing for normal address-manager churn.
Use the RPC with getpeerinfo, getnetworkinfo and configured reachability to distinguish known-address diversity from active connection diversity.
Aggregate counts are safer than dumping addresses, but RPC access still exposes node topology and operational behaviour. Keep it authenticated and off public dashboards.
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.
Bitcoin Core getaddrmaninfo RPC: new counts potential peers the node has learned but not successfully connected to.
The RPC accepts no parameters and returns a map keyed by network.
new counts potential peers the node has learned but not successfully connected to.
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.
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.
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Bitcoin Core 23 getblockfrompeer guide covering known headers, peer IDs, scheduled requests, peer replacement, validation, monitoring and failure recovery.
Bitcoin Core 0.16 stop RPC guide covering authority, service draining, state persistence, process supervision, shutdown verification and restart readiness.
Bitcoin Core 0.16 setnetworkactive guide covering full P2P disable and enable, service impact, stale state, maintenance sequencing, recovery and monitoring.
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.