BTC: Reachable Nodes: Bitcoin Core vs Bitcoin Knots
Reachable Nodes: Bitcoin Core vs Bitcoin Knots: daily data through 9 Nov 2026.
The share of reachable nodes in our crawler's sample running Bitcoin Core and running Bitcoin Knots.
Why use it. Bitcoin Core and Bitcoin Knots follow different relay and mining-policy defaults, so their shares say which policies most listening nodes apply and how a contested change might go. How to read it. The two lines rise and fall against each other; the share of other software is small. A rise in Knots' line is more nodes switching to it, or nodes running Knots being added to the sample.
Calculation. Each node's reported software name, in each snapshot, as in the Node Software chart. Observed by CryptoKeyhole's own crawler. Twice an hour it re-contacts every node in its sample (every Bitcoin node it reached over IPv4 in the last 24 hours), completes the version handshake and disconnects. It reads only what a node announces about itself in that handshake: its software name and version, its service flags, its protocol version, whether it wants transactions relayed and its fee filter. Addresses are used only to connect and are never stored or published. A node counts once per snapshot (by address and port); an hour or a day shows the mean of its snapshots, and the latest hour and day are partial. Reachable nodes are a sample, not every node. Nodes that do not accept incoming connections (most nodes), and nodes reachable only over Tor, I2P, CJDNS or IPv6, are not counted, because our host connects over IPv4 only. Our crawler has also not found every IPv4 node that accepts connections: it finds nodes from the addresses our own node knows and the addresses other nodes announce, and our Internet connection lets it try only a few new addresses a second, so the sample grows over its first days. Each snapshot re-contacts every node in the sample (up to three tries within minutes) and is published only if it reached at least 90% of them within 25 minutes and the sample holds at least 1,000 nodes. Software names, versions and flags are self-reported and cannot be verified. Collection began on 22 October 2026; no earlier values are reconstructed.