How scoring works
Every public node is scored on its own record over the last 30 days. Its place on the leaderboard comes from that score alone, so running more nodes never lifts a place.
The four parts
Seen online
The share of complete crawls in the last 30 days that the node answered.
Connection checks
Between crawls we check known nodes again. The share of those checks it passed.
Peer store
How many other nodes' addresses it keeps, against the typical node: the typical number scores 50, twice that or more scores 100.
Software version
How close it is to the newest release other nodes run too. Each version behind scores less, never below 10; widely run versions get a small bonus.
Each part is a percentage, and the score is their weighted average out of 100. A part we could not measure for a node is left out, and the others share its weight.
Getting a place
A node joins the leaderboard once it has been seen online on 10 separate days in the last 30. Until then it is listed without a place. Places come only from complete crawls, so the leaderboard starts once there are 10 days of them.
When a new release comes out, older versions are scored gently for a week while operators upgrade.
The latest crawl
A node's page also shows a reading from the latest crawl alone, worked out the same way. It shows how the node is doing right now; only the 30-day score sets its place.
Claiming a node
Running a node and claiming it puts your name on its row. Claiming never changes a score: every node, claimed or not, is measured the same way.