Solana feature gate activations: 1 feature gate queued for the next epoch for the next epoch
Solana ships changes in validator releases, then switches them on one by one with "feature gates" at epoch boundaries (about every two days). We read Anza's public tracker and check each pending gate on-chain.
Gates are switched on by the feature authority; each one activates at the start of the next epoch once queued. Source: Anza: Feature Gate Tracker Schedule (checked 12 Nov 2026).
What do I have to do?
Holders
Nothing to do
Feature activations change validator and program behaviour, not your balance. Wallets update themselves.
Exchange users
Nothing to do
Activations rarely pause SOL deposits.
Stakers
Validators: stay above the version floor
Activations start only after 95% of stake runs the required minor version; validators below the floor risk falling out of consensus. Delegators: nothing to do.
Source: Anza tracker (checked 12 Nov 2026)
Node operators
Run at least the current version floor
The floor (shown below, read live) is the minimum Agave and Firedancer versions supported on mainnet.
Source: Anza tracker (checked 12 Nov 2026)
Developers
Check SIMDs that touch programs
Gates like "Set lamports per byte" (SIMD-0437) or loader changes (SIMD-0433, SIMD-0500) change rent and program deployment. Test on devnet/testnet first.
Source: SIMDs (checked 12 Nov 2026)
Live on-chain view
Next on mainnet
| Feature | Min. client | Activated on (epoch) | Mainnet on-chain |
|---|---|---|---|
| SIMD-0460: Virtual Address Space Adjustments 7VgiehxNxu53KdxgLspGQY8myE6f7UokaWa4jsGcaSz | Agave v4.0.0-beta.0, FD v1.0 | testnet 957, devnet 1073 | Queued for the next epoch |
| Account Data Direct Mapping CR3dVN2Yoo95Y96kLSTaziWDAQT2MNEpiWh5cqVq2pNE | Agave v4.0.0-beta.0, FD v1.0 | testnet 958, devnet 1074 | Not requested |
| SIMD-0449: Direct Account Pointers in Program Input ptr9umikaeAS7ZBBp2fsfRhie16F1V2jCKA2y6gXNAK | Agave v4.1.0-beta.0, FD v1.0 | testnet 981, devnet 1099 | Not requested |
| SIMD-0512: SHA512 Syscall s512oDwgx8hjMnaQjXfqqrZroVj4HvC6TkN3iSSWXCh | Agave v4.1.0-beta.0, FD v1.0 | testnet 977, devnet 1092 | Not requested |
Still on devnet / testnet
| Feature | Min. client | Activated on (epoch) | |
|---|---|---|---|
| SIMD-0599: Remove inactive stakes from stake delegations RMsTKfD6hZnBhhNvgGBeKNrqCNkeoP3DYYxNtcuWtRg | Agave v4.4.0-beta.0, FD v26.10.0 | testnet 1081 | |
| SIMD-0437-3: Set lamports per byte to 2575 rntCigrTppP5JdZz7K8TyN9sMzLdAcXp8SejYpVpX6D | Agave v4.3.0-rc.1, FD v26.10.0 | ||
| SIMD-0317: Enforce the Merkle proof size of a fixed 32:32 FEC set turbzzBJLGMJJikLvgCCJu9e1hTmfxwarrbLndYAsK5 | Agave v4.4.0-beta.0, FD v26.10.0 | ||
| SIMD-0433: Loader V3 Set Program Data to ELF Length EhisBfVtGvEA8bVCVN5VMaYEaX6iTfoUrmcDi8LY7Kxy | Agave v4.4.0-beta.0, FD v26.10.0 | ||
| SIMD-0437-4: Set lamports per byte to 1322 rntD7invRBswCAdKtRsh1G4psKjrPdS3BKqtnA78C7N | Agave v4.3.0-rc.1, FD v26.10.0 | ||
| SIMD-0500: Disable deployment of SBPF v0, v1 and v2 programs B8JJXCy5amZyWG9r7EnUYLwzXSXTxG7GZ1qZ1qggo83g | Agave v4.1.0-beta.0, FD v1.0 |
From Anza's feature-gate tracker (wiki, read every 6 h). "Queued" means the feature account exists on mainnet and the gate switches on at the next epoch boundary; "not requested" means it is still waiting. 250 gates are fully activated on all clusters.
Exchange pause board
Right now
| Network | Binance | KuCoin | Kraken | Coinbase | Gate | Bitget |
|---|---|---|---|---|---|---|
| SOL Solana | Open | Open | Open | Open | Open | Open |
Last check 3 min ago. Coinbase's status page does not split deposits from withdrawals. "—" means the exchange does not list that network or does not report it.
Exchange notices
Also on the Network Desk for Solana
How this works and where the data comes from
Each upgrade page is built from primary sources: client release notes, foundation announcements, governance proposals and Forkcast data for Ethereum. Every curated fact carries its source and the date we checked it. Live data refreshes automatically: exchange flags every 15 minutes, chain heights and governance every 15 minutes, client releases hourly, readiness data every 6 hours.
Countdowns: fixed-time forks use the announced timestamp; Ethereum slots are exact (12 s per slot); height-based forks (Cosmos) are estimated from the average block time of the last 2,000 blocks and will drift. When a target changes we record it as a date slip.
Exchange pauses: we read Binance (deposit/withdraw flags per network), KuCoin (per chain), Kraken (asset funding status) and Coinbase (status page component per network). A pause is any period where deposits or withdrawals are off. Reopen time is measured from the activation time to the first check where both are back on.
Sources: Anza: Feature Gate Tracker Schedule (checked 12 Nov 2026); Tracker JSON (checked 12 Nov 2026)
Information only, not financial advice. Data comes from public sources and can be delayed or wrong; check the primary source before acting.