preferred on
Points of Focus
- Solana has activated the 350ms mainnet gate, with the change taking effect in epoch 1020.
- SIMD-0525 cuts slots from 400ms toward 200ms in four stages.
- Compute limits scale down with faster slots, keeping capacity broadly steady.
Solana has activated the first mainnet gate in its plan to halve target slot times, but the chain is still operating on the 400-millisecond target. Anza CEO Brennan Watt said in an X post that the 350ms setting will take effect in epoch 1020, currently expected to begin on Aug. 21.
The feature gate is already active onchain, but its new parameters begin after a one-epoch delay. SIMD-0525 moves Solana through 350ms, 300ms, 250ms, and 200ms stages rather than cutting directly from 400ms to 200ms. The proposal remains classified as a draft as the later stages move through testing.
🚨we're activating 1st slot time reduction on mainnet
help ensure devs are ready because the transition period is wonky…
1. We have NOT updated some sdk constants like `DEFAULT_MS_PER_SLOT` to reflect new values. Note we will push a release with updated values post activation…
— Brennan Watt (@bw_solana) August 18, 2026
350ms slots shorten Solana leader windows
Moving from 400ms to 350ms cuts the target slot duration by 12.5% and raises slot opportunities from 2.5 to 2.86 per second. Solana keeps four consecutive slots per leader, so a leader’s nominal block-production window falls from 1.6 seconds to 1.4 seconds at 350 ms. At 200ms, that window drops to 0.8 seconds.
The Solana Foundation’s roadmap says shorter slots reduce confirmation latency and shorten the period in which one leader can delay, reorder, or selectively include transactions. The staged rollout also gives client teams time to identify timing and operational problems before the network reaches the 200ms target.
Faster slots don’t double compute capacity
Lower slot times don’t mean Solana immediately doubles execution throughput. The protocol scales per-slot work limits down as blocks arrive more often.
Solana raised its mainnet block limit from 60 million to 100 million compute units on July 29. That upgrade forms the active baseline for SIMD-0525, which maps the maximum to 87.5 million CUs at 350 ms, 75 million at 300 ms, and 50 million at 200 ms. Those limits keep the theoretical ceiling near 250 million CUs per second through each stage.
Watt also noted that some SDK constants, including “DEFAULT_MS_PER_SLOT,” still reflect the old 400 ms timing. Applications that rely on those values to estimate mainnet timing may need to account for the active feature and epoch boundary until the constants are updated.
The four-stage rollout keeps epochs fixed at 432,000 slots. At the final 200ms target, that would cut an epoch’s nominal wall-clock duration from about 48 hours to 24 hours.
Share
Most read articles
