Bitcoin Core 0.21 -netinfo guide covering detail levels, peer and network RPC inputs, privacy-safe diagnostics, snapshot limits, monitoring and incident evidence.
This guide explains Bitcoin Core netinfo peer dashboard in plain English. It focuses on what the subject is, why it matters and what a beginner should remember.
Bitcoin Core netinfo peer dashboard: -netinfo is a bitcoin-cli command, not a node RPC. Automation needing structured data should call versioned getpeerinfo and getnetworkinfo schemas instead of scraping terminal columns.
A node operator is checking Bitcoin Core netinfo peer dashboard. Reserve -netinfo for humans, capture it during incidents and compare before and after controlled changes.
-netinfo is a bitcoin-cli command, not a node RPC. Automation needing structured data should call versioned getpeerinfo and getnetworkinfo schemas instead of scraping terminal columns.
The optional integer zero to four increases displayed detail. Use the lowest level that answers the diagnostic question and document the exact Core version and invocation.
Counts and rows describe currently observed inbound and outbound connections. They can change immediately and do not prove chain synchronisation, block relay or transaction relay health.
Network address, direction, services and timing are operational signals, not identities. A diverse-looking list can still share infrastructure or adversarial control; use multiple eclipse-resistance measures.
Higher-detail output can contain peer addresses and operational topology. Restrict access, redact external incident artefacts and never publish a raw dashboard alongside customer or infrastructure records.
Correlate the snapshot with chain tip, headers, last block and transaction times, connection type, warnings and logs. Distinguish no peers from stalled peers, block-relay-only peers and disabled networking.
For alerts, consume structured RPC fields with schema tests, bounded polling and time-series context. Reserve -netinfo for humans, capture it during incidents and compare before and after controlled changes. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Bitcoin Core netinfo peer dashboard: -netinfo is a bitcoin-cli command, not a node RPC.
-netinfo is a bitcoin-cli command, not a node RPC. Automation needing structured data should call versioned getpeerinfo and getnetworkinfo schemas instead of scraping terminal columns.
The optional integer zero to four increases displayed detail. Use the lowest level that answers the diagnostic question and document the exact Core version and invocation.
Counts and rows describe currently observed inbound and outbound connections. They can change immediately and do not prove chain synchronisation, block relay or transaction relay health.
The 0.21 -netinfo dashboard made peer diagnosis faster for humans. Reliable operations still require structured RPC monitoring, privacy controls and separate checks for chain progress, relay health and network diversity.
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 22 I2P guide covering SAM configuration, inbound and outbound sessions, address relay, privacy boundaries, reachability tests, monitoring and rollback.
Bitcoin Core 0.21 Tor v3 guide covering BIP 155 address relay, listenonion migration, key files, permissions, reachability, rollback and privacy tests.
Bitcoin Core 0.20 whitelist guide covering bloomfilter, noban, forcerelay, relay and mempool permissions, implicit defaults, CIDR scope and safe peer trust.
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.