Dataset · Network · CC BY 4.0

Solana validators: stake concentration and client mix

How many validators it takes to pass 20%, 33.3% and 40% of Solana's stake, which validator software holds the stake (by codebase and by block-building layer), and how commission is spread.

The number

On 2026-11-16, 8 Solana validators held more than 20% of all stake, 18 more than a third and 25 more than 40% (read from getVoteAccounts); Agave-based clients ran 81.6% of voting stake and Firedancer-based ones 18.1%.

Data as of Source: Solana JSON-RPC (api.mainnet-beta.solana.com, solana-rpc.publicnode.com): getVoteAccounts, getClusterNodes. Hosting and countries: stakewiz (api.stakewiz.com/validators, geo-IP), read 2026-11-16. CSVJSON CC BY 4.0
Validators voting
662
662 with stake
Delinquent (not voting)
38
0.08% of stake
Validators needed to exceed 20% of stake
8
Alpenglow's Byzantine bound
Validators needed to exceed 33.3%
18
the classic one-third rule
Validators needed to exceed 40%
25
Alpenglow's crash bound (20% + 20%)
Largest validator
3.94%
of all activated stake
Top 10 validators hold
24.8%
Agave-based clients
81.6%
of voting stake
Firedancer-based clients
18.1%
of voting stake

The table

11 rows, 7 columns. Click a column heading to sort. The plain-English explanation is on its page.

Client (clientId)CodebaseBlock-building layerValidatorsStake (SOL)Share of voting stake (%)Main versions
AgaveBamAgaveBAM360165,114,45338.494.4.1, 4.4.0
HarmonicAgaveAgaveHarmonic5091,974,76421.444.4.1, 4.4.0
JitoLabsAgaveJito12282,993,21819.354.4.1, 4.4.0
HarmonicFiredancerFiredancerHarmonic4446,992,48310.9526.10.8, 26.10.6
FiredancerFiredancernone3421,931,2945.1126.10.8, 0.1.1
FireBAMFiredancerBAM218,537,7911.9926.11.0, 26.10.8
RakuraiAgaveRakurai85,229,2521.224.4.1, 4.4.0
AgaveAgavenone184,249,8720.994.4.1, 5.0.0-alpha.0
unknown idotherother31,355,4050.320.0.0, 4.4.1
RaikuAgaveRaiku1402,5800.094.4.1
not in gossipotherother1186,7230.04—

Showing all 11 rows. Full table as CSV

History

7 readings kept in the file, newest first.

DateEpochVotingDelinquentNeeded for 20%Needed for 33.3%Needed for 40%Top 10 share (%)Agave-based (%)Firedancer-based (%)
2026-11-161087662388182524.7781.5818.06
2026-11-151086662378182524.7281.5918.05
2026-11-141085661388182524.5481.3418.34
2026-11-131085659408182524.5481.3418.34
2026-11-121084661378182524.4881.2318.46
2026-11-111083659408182524.5681.3918.29
2026-11-101083658418182524.5683.4316.26

Showing all 7 readings. Full history in the JSON

How this is measured

Total stake = activated stake of every vote account, voting or delinquent. Validators are sorted by stake; the count needed to exceed X% is the smallest number of the largest validators whose stake sums to more than X% of the total. Client mix: each voting validator's node is looked up in getClusterNodes and its self-reported clientId is joined to its stake; shares are of voting stake. Codebase groups the clients by whose code they are built from (Agave or Firedancer); block-building layer groups them by what orders their blocks (BAM, Harmonic, Jito's original client, none). Commission is the inflation-reward commission in basis points (SIMD-0291), for validators with stake.

What would make it wrong

  • Counts are per validator, not per operator. One company can run several validators, so the true number of independent parties needed is lower. Nakaflow, which groups validators by entity, published 6 against a one-third threshold on 2026-11-10.
  • clientId is self-reported in gossip and can be wrong; a validator missing from gossip at the moment of the call is counted as "not in gossip".
  • Hosting and country come from geo-IP via stakewiz: they place the server, not the operator, and some hosts are mislabelled.
  • Which threshold matters is a judgement. Under Alpenglow the protocol's stated safety bound is 20% malicious stake (SIMD-0326); 33.3% is the bound most published figures use; 40% is the stated crash tolerance.
  • Shares move every epoch as stake is delegated and withdrawn.

Sources

Every number here is read (from the network or a public API, at the time shown), computed from reads by the formula above, or stated by its source; the methodology page explains the three. SolPilled is independent and unofficial, not the Solana Foundation. Nothing here is financial advice.

Cite or reuse this data

Free to reuse with attribution under CC BY 4.0. Machine-readable: /data/network-validators.json (everything, including history and the method) and /data/network-validators.csv (the table). Agents can also read it through our MCP server.

Suggested citation:

SolPilled, "Solana validators: stake concentration and client mix", https://solpilled.com/data/network-validators/ (data as of 2026-11-16T00:42:46.855Z). CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/), attribute SolPilled (solpilled.com).

More Solana data

All datasets · Methodology · MCP server