Dashboard

Adoption

Stake-weighted version distribution · Feature support signals · Not governance votes

Stake-Weighted Version Distribution

⚠ Adoption signal — shows which versions validators run, not a governance vote

3.1.13
40.2%
387 val
3.1.14
33.0%
196 val
4.0.0-beta.7
5.3%
3 val
4.0.0-rc.0
4.8%
30 val
0.821.30114
4.7%
22 val
0.821.30113
3.2%
2 val
0.1.1
2.7%
10 val
0.820.30113
1.8%
40 val
3.1.10
1.8%
18 val
0.906.0-rc.40000
1.2%
7 val
Total: 427.8M SOL · Updated 18:32:22 UTC

Version Adoption by Stake Weight

SIMD-0312 CreateAccountAllowPrefund
≥v4.0.0-beta.0 10.5%
46/769 val
56.2% more stake on compatible versions needed
SIMD-0458 Stop special-casing of Vote CU cost
≥v4.0.0-beta.0 10.5%
46/769 val
56.2% more stake on compatible versions needed
SIMD-0284 Alt-BN128 Little Endian compatibility
≥v4.0.0-beta.0 10.5%
46/769 val
56.2% more stake on compatible versions needed
SIMD-0302 BN254 G2 Arithmetic Syscalls
≥v4.0.0-beta.0 10.5%
46/769 val
56.2% more stake on compatible versions needed
SIMD-0388 BLS12-381 Elliptic Curve Syscalls
≥v4.0.0-beta.2 10.5%
46/769 val
56.2% more stake on compatible versions needed
SIMD-0490 Upgrade BPF Stake Program to v5.0.0
≥v4.0.0-beta.3 10.5%
46/769 val
56.2% more stake on compatible versions needed
SIMD-0249 Delay Commission Updates
≥v4.0.0-beta.0 10.5%
46/769 val
56.2% more stake on compatible versions needed
SIMD-0340 Validate chained block id
≥v4.0.0-beta.6 10.5%
46/769 val
56.2% more stake on compatible versions needed
SIMD-0178 SBPF Static Syscalls
≥v4.0.0 10.5%
46/769 val
56.2% more stake on compatible versions needed
SIMD-0459 Syscall Parameter Address Restrictions
≥v4.0.0-beta.0 10.5%
46/769 val
56.2% more stake on compatible versions needed
SIMD-0460 Virtual Address Space Adjustments
≥v4.0.0-beta.0 10.5%
46/769 val
56.2% more stake on compatible versions needed
⚠ Important: This is an adoption signal, not a governance vote. Support % shows what fraction of total stake runs a version ≥ the feature's minimum requirement. 66.7% is the typical activation threshold, but reaching it doesn't mean validators explicitly voted for the feature — they may have upgraded for other reasons. Data: mainnet getVoteAccounts + getClusterNodes RPC.