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.
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%.
- 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) | Codebase | Block-building layer | Validators | Stake (SOL) | Share of voting stake (%) | Main versions |
|---|---|---|---|---|---|---|
| AgaveBam | Agave | BAM | 360 | 165,114,453 | 38.49 | 4.4.1, 4.4.0 |
| HarmonicAgave | Agave | Harmonic | 50 | 91,974,764 | 21.44 | 4.4.1, 4.4.0 |
| JitoLabs | Agave | Jito | 122 | 82,993,218 | 19.35 | 4.4.1, 4.4.0 |
| HarmonicFiredancer | Firedancer | Harmonic | 44 | 46,992,483 | 10.95 | 26.10.8, 26.10.6 |
| Firedancer | Firedancer | none | 34 | 21,931,294 | 5.11 | 26.10.8, 0.1.1 |
| FireBAM | Firedancer | BAM | 21 | 8,537,791 | 1.99 | 26.11.0, 26.10.8 |
| Rakurai | Agave | Rakurai | 8 | 5,229,252 | 1.22 | 4.4.1, 4.4.0 |
| Agave | Agave | none | 18 | 4,249,872 | 0.99 | 4.4.1, 5.0.0-alpha.0 |
| unknown id | other | other | 3 | 1,355,405 | 0.32 | 0.0.0, 4.4.1 |
| Raiku | Agave | Raiku | 1 | 402,580 | 0.09 | 4.4.1 |
| not in gossip | other | other | 1 | 186,723 | 0.04 | — |
Showing all 11 rows. Full table as CSV
History
7 readings kept in the file, newest first.
| Date | Epoch | Voting | Delinquent | Needed for 20% | Needed for 33.3% | Needed for 40% | Top 10 share (%) | Agave-based (%) | Firedancer-based (%) |
|---|---|---|---|---|---|---|---|---|---|
| 2026-11-16 | 1087 | 662 | 38 | 8 | 18 | 25 | 24.77 | 81.58 | 18.06 |
| 2026-11-15 | 1086 | 662 | 37 | 8 | 18 | 25 | 24.72 | 81.59 | 18.05 |
| 2026-11-14 | 1085 | 661 | 38 | 8 | 18 | 25 | 24.54 | 81.34 | 18.34 |
| 2026-11-13 | 1085 | 659 | 40 | 8 | 18 | 25 | 24.54 | 81.34 | 18.34 |
| 2026-11-12 | 1084 | 661 | 37 | 8 | 18 | 25 | 24.48 | 81.23 | 18.46 |
| 2026-11-11 | 1083 | 659 | 40 | 8 | 18 | 25 | 24.56 | 81.39 | 18.29 |
| 2026-11-10 | 1083 | 658 | 41 | 8 | 18 | 25 | 24.56 | 83.43 | 16.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
- solana.com /docs/rpc/http/getvoteaccounts
- solana.com /docs/rpc/http/getclusternodes
- github.com /solana-foundation/solana-improvement-documents/blob/main/proposals/0326-alpenglow.md
- api.stakewiz.com /validators
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
- Exit cost of Solana staking tokens by size
- The SOL holder ledger: what each way of holding SOL pays
- Bridging USDC to Solana: what $100, $1,000 and $10,000 land as
- Solana account deposits (rent-exempt minimums), read live
- Solana transaction fees, sampled from recent blocks
- Where Solana fees go: apps, the chain itself and Jito tips, 30 days
- Solana epoch length, measured
- Solana incidents: the official status page record, and what we measure
- Solana protocol changes, 2025 to 2026, dated from the chain
- Solana speed, measured: slot time and real transactions per second
- Solana supply, inflation and staked share
- The Solana ecosystem by category
- Solana's headline numbers, one reading a day