Skip to content
Satoshi Gazette
Glossary

Reachable node

A Bitcoin node that accepts incoming connections at an address a crawler can reach. Published node counts are counts of these; nodes that only connect outward go unseen.

Protocol and network

Definition dated

also listening node

A full node can run without accepting connections: it connects out to peers, validates every block and serves its owner. Only a node that listens for incoming connections, at an address others can reach, can be found and counted from outside.

Crawlers such as the one run by KIT's Decentralized Systems and Network Services group connect to every address they learn about and record what each node announces in its handshake: its protocol version, its user agent, the services it offers. Their totals are counts of reachable nodes at a moment, and they differ with the crawler, the networks it covers and how recently a node must have answered to be counted.

A reachable-node count is a population measured by a stated method, never the number of nodes.

Common misreadings3

  • People say

    There are N bitcoin nodes

    Precisely

    A crawler counts the nodes it could reach. Nodes behind firewalls or with listening turned off are not counted, and crawlers that do or do not cover Tor get different totals.

  • People say

    A node count measures support for a rule

    Precisely

    Nodes are cheap to run and to fake. A count of user agents is a population, not a vote, and carries no hashrate.

  • People say

    One reachable address is one operator

    Precisely

    One operator can run many nodes, and one node can be reachable at several addresses, over IPv4, IPv6 and Tor.