How few could halt Solana tonight?
Blocks stop finalizing once more than a third of staked SOL goes quiet. This board tallies how many validators, countries, hosting providers, networks and client builds it would take to reach that third, refreshed from the chain every ten minutes.
The count, race by race
Pick what counts as one party. Red is the bloc that clears a third, blue is everyone else, grey is stake we can't place.
Loading…
Stake by country
One tile per country, darker means more stake. Red tiles together already pass the third.
Loading…
Roll call: the superminority
The biggest validators, in order, until their stake tops a third. If all of them dropped at once, the chain would stall.
| Loading… |
Client software race
A single bug lands on every node running the same code. Builds come from what each node announces in gossip, weighted by its stake.
Loading…
Agave lineage: Agave, Jito-Solana, BAM, Harmonic and Rakurai builds all run Agave's runtime. Firedancer lineage: full Firedancer, FireBAM / Harmonic Firedancer and Frankendancer (Firedancer networking on top of Agave's runtime, so only partly separate). "Other" = names we can't match to either; "Unknown(n)" = a bare numeric client id.
Past counts
A snapshot of the headline numbers is filed every hour and kept.
Counting rules
Every input is public; nothing here needs a login or a wallet.
1The threshold
Line parties up from largest stake to smallest and add them until the running total is more than one third of all active stake. That number of parties is the score; lower means more concentrated. We also show the two-thirds figure, the stake that could finalize blocks with nobody else.
2Stake
Activated stake per vote account from Solana RPC getVoteAccounts, both current and delinquent. Accounts with zero active stake are left out. Re-read every 10 minutes.
3Where
Country, city, hosting provider and ASN come from Stakewiz, which geolocates each validator's IP. Geolocation can miss, and nodes move. Stake Stakewiz can't place stays grey and is never treated as one party.
4Software
The clientId a node announces in gossip, matched to stake by identity key. Nodes report it themselves, so it could be faked, but it is exactly what the rest of the network sees.