getaddr gossip. Includes
Paces itself adaptively — it speeds up on its own the more peers actually answer and backs off when they
don't. Addresses are recorded the moment we hear of one; reachability is tracked separately, because
hearing about a node is cheap and confirming one is not (most advertised addresses never answer, and a peer
already holding a connection from our address will refuse a second).
.onion peers through a local SOCKS proxy, but Zcash has no way
to discover them — zcashd implements no addrv2 at all, and Zebra only ever sends the legacy
addr message, which cannot represent an onion address. Hidden-service nodes exist but are invisible
to peer gossip, so the Tor series stays at zero unless an address is supplied out of band.
One dot per node, placed at its city region — never finer. Click a legend entry to toggle it. A node answering on both IPv4 and IPv6 is one dot where we can tell (our own fleet); for other operators the protocol carries no node identity, so a dual-stack node may appear twice.
Loading…
| # | Country | Nodes | At tip | Out of sync | Unknown |
|---|
Each bar is every node confirmed reachable at least once that week. Weekly rather than daily because one day is not one crawl cycle — the crawler takes far longer than 24h to work through its address book, so a daily series tracks our own cadence rather than the network's.
Loading…
Which implementation each reachable node is running — the aggregate that makes this map worth publishing.
Loading…
| Network | Node | Range | Location | Client | Version | Sync (when indexed) | First Seen | Last Seen |
|---|
Loading…
| Status | What it means | Addresses |
|---|