Dashboard

Protocol radar

What changes next on Solana — and when

Every protocol upgrade, watched on-chain across mainnet, testnet and devnet. Queued upgrades get a live countdown; the ones that break things get a plain-English guide.

chain last read

Up next

SIMD-0385

Transaction V1

Pending testnet activation on Anza's official schedule

Network readiness95.0% of stake · threshold 95%

Mainnet activations begin two full epochs after 95% of stake adopts the release.

No official date exists. Once 95% is crossed, mainnet activations begin two full epochs later — ≈ 3.2 days at today’s pace.

4,096-byte transactions in a new wire format: resource limits move into the message, lookup tables are gone, and un-upgraded readers start failing the moment it activates.

mainnet · not scheduledtestnet · activedevnet · active
Read the deep dive →
Telegram alertsKnow the moment an upgrade is queued — join @xrootdev_updates or message the bot /start for a DM.

Queued 0

Nothing queued right now — activations appear here the moment they are requested on-chain.

On deck 18

  1. Slot time step 3 of 4: a block every 250ms, down from the 300ms running today — faster confirmations for everything on Solana.

    officially scheduled · at this pace ≈ within a day or two
  2. Slot time step 4 of 4: the 200ms target — halving block times from where the year started.

    officially scheduled · at this pace ≈ Sep 8
  3. A native SHA512 syscall for on-chain programs.

    officially scheduled
  4. Programs read account inputs through direct pointers instead of copies — faster account access.

    officially scheduled
  5. 4,096-byte transactions in a new wire format: resource limits move into the message, lookup tables are gone, and un-upgraded readers start failing the moment it activates.

    officially scheduledRead the guide ↗
Show 13 more ↓Show less ↑
  1. Maps account data directly into program memory instead of copying it on every load.

    officially scheduled
  2. Adjusts the SVM's virtual address space layout.

    officially scheduled
  3. Lowers rent to 5,080 lamports per byte.

    officially scheduledRead the guide ↗
  4. Lowers rent to 2,575 lamports per byte.

    not scheduledRead the guide ↗
  5. Lowers rent to 1,322 lamports per byte.

    not scheduledRead the guide ↗
  6. The final step: 696 lamports per byte, completing the 90% rent cut.

    not scheduledRead the guide ↗
  7. The safety valve for the rent cut: restores the legacy 6,960 lamports-per-byte rate if a reduction step needs reverting.

    not scheduled
  8. Alpenglow

    SIMD-0326

    The new consensus algorithm — the largest consensus change since launch, targeting dramatically faster finality.

    not scheduled
  9. Alpenglow companion gate: fast leader handover between slots.

    not scheduled
  10. Raises the cross-program-invocation depth limit from 4 to 8, unblocking deeper program composition.

    not scheduled
  11. Disables deployment of programs targeting the legacy SBPF v0, v1 and v2 bytecode formats.

    not scheduled
  12. In-protocol sharing of block revenue between validators and their stakers.

    not scheduled
  13. A new vote-account initialization instruction.

    not scheduled

Activated 18

  1. Lowers rent from 6,960 to 6,333 lamports per byte — the first of five feature-gated reductions on the way to a 90% cut.

    active since epoch 1028 · 2 days agoRead the guide ↗
  2. Relaxes the post-execution minimum-balance check.

    active since epoch 1027 · ≈ 4 days ago
  3. Upgrades the BPF stake program to v5.1.0 with fixed-point warmup and cooldown math.

    active since epoch 1026 · ≈ 5 days ago
  4. Slot time step 2 of 4: blocks every 300ms.

    active since epoch 1023 · ≈ 10 days ago
  5. Slot time step 1 of 4: blocks every 350ms instead of 400ms.

    active since epoch 1019 · ≈ 2 weeks ago
Show 13 more ↓Show less ↑
  1. Raises the per-block compute limit to 100 million compute units — more work per block.

    active since epoch 1009 · 5 weeks ago
  2. Defines fee-only semantics: transactions that fail account loading still pay their fee, deterministically.

    active since epoch 1008 · 5 weeks ago
  3. Alpenglow VAT

    SIMD-0357

    Alpenglow groundwork: the VAT implementation lands ahead of the consensus switch.

    active since epoch 1006 · 6 weeks ago
  4. Markers for Alpenglow fast leader handover and shred placement rules.

    active since epoch 1005 · ≈ 5 weeks ago
  5. Validator commission moves from whole percents to basis points — finer-grained rates.

    active since epoch 1003 · 7 weeks ago
  6. A minimum extend size for Loader V3 program deployments.

    active since epoch 1002 · 7 weeks ago
  7. Enforces a protocol-level cap on accounts per instruction.

    active since epoch 1000 · 8 weeks ago
  8. BLS public keys in vote accounts — consensus groundwork for Alpenglow.

    active since epoch 999 · 2 months ago
  9. Tightens which memory addresses syscall parameters may reference.

    active since epoch 995 · 2 months ago
  10. Enables deployment and execution of SBPFv3 programs (with SIMD-0189 and SIMD-0377).

    active since epoch 993 · 2 months ago
  11. Validates the chained block id across a slot's shreds.

    active since epoch 992 · ≈ 8 weeks ago
  12. The encompassing check completing chained block id validation.

    active since epoch 992 · ≈ 8 weeks ago
  13. Validator commission changes take effect at the next epoch instead of immediately.

    active since epoch 991 · 2 months ago

What a feature gate is

Solana ships protocol changes behind on-chain switches. Each switch is a tiny account anyone can read — which is exactly what this page does.

Why "queued" means days, not months

Once an upgrade is queued, the network activates it at the next epoch boundary — at most about two days away. That is why queued upgrades get a countdown.

Testnet goes first

Upgrades usually activate on testnet before mainnet, so the testnet column is a preview of what mainnet does next.

Read from the chain, not from announcements

The status here comes from reading the switches themselves, refreshed about every minute. When nothing is scheduled, we say so — no invented dates.