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

4.0.2
36.2%
131 val
4.0.3
31.3%
394 val
4.1.0-rc.1
17.7%
97 val
0.911.40002
7.5%
35 val
0.1.1
2.8%
7 val
0.913.40003
1.8%
5 val
0.912.40003
1.5%
26 val
0.1004.0-rc.40101
0.5%
7 val
Unknown
0.2%
9 val
4.1.0
0.2%
1 val
Total: 427.7M SOL · Updated 21:49:51 UTC

Version Adoption by Stake Weight

SIMD-0459 Syscall Parameter Address Restrictions
≥v4.0.0-beta.0 85.6%
638/731 val
✅ ≥66.7% running compatible version (85.6%)
SIMD-0460 Virtual Address Space Adjustments
≥v4.0.0-beta.0 85.6%
638/731 val
✅ ≥66.7% running compatible version (85.6%)
SIMD-0406 Maximum instruction accounts
≥v4.0.0-beta.7 85.6%
638/731 val
✅ ≥66.7% running compatible version (85.6%)
SIMD-0387 BLS Pubkey management in vote account
≥v4.1.0-beta.0 18.0%
104/731 val
48.7% more stake on compatible versions needed
SIMD-0431 Loader V3: Minimum Extend Program Size
≥v4.1.0-beta.0 18.0%
104/731 val
48.7% more stake on compatible versions needed
SIMD-0512 Sha512 Syscall
≥v4.1.0-beta.0 18.0%
104/731 val
48.7% more stake on compatible versions needed
SIMD-0291 Commission Rate in Basis Points
≥v4.1.0-beta.0 18.0%
104/731 val
48.7% more stake on compatible versions needed
SIMD-0337 Markers for Alpenglow Fast Leader Handover
≥v4.1.0-beta.0 18.0%
104/731 val
48.7% more stake on compatible versions needed
SIMD-0357 Alpenglow Validator Admission Ticket
≥v4.1.0-beta.0 18.0%
104/731 val
48.7% more stake on compatible versions needed
SIMD-0186 Loaded Transaction Data Size Specification
≥v4.1.0-beta.1 18.0%
104/731 val
48.7% more stake on compatible versions needed
SIMD-0449 Direct Account Pointers in Program Input
≥v4.1.0-beta.0 18.0%
104/731 val
48.7% 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.