Solana cuts blockchain slot time to 350 milliseconds
Solana cuts blockchain slot time to 350 milliseconds for the first time since the network launched, according to Solana Foundation technology VP Jacob Creech. The move is step one toward a 200-millisecond target meant to cut latency and speed up confirmations, with average slots near 360ms versus the old 400ms goal.
Key Takeaways
- Solana reduced its target slot time to 350ms, the first cut since genesis.
- The network is aiming for 200ms overall, with three further 50ms steps planned.
- Jacob Creech said the next stop is 300ms after this “new era of 350ms.”
- SIMD-0525, which sets the shorter slots, was approved and merged on May 14.
- All four stages are targeted for Agave v4.2 mainnet activation on a tentative schedule.
What happened to Solana’s slot time?
Solana has shortened its blockchain slot time to 350 milliseconds, marking the first reduction since the network’s inception. The update was confirmed by Jacob Creech, vice president of technology at the Solana Foundation.
In a Friday post on X, Creech wrote: “We’re in a new era of 350ms. Next stop, 300ms.” Average slot times stood at about 360ms at press time, below the network’s original 400ms target, according to the Solana slot time explorer cited by Cointelegraph.
Why does a faster Solana slot time matter?
Shorter slots are meant to reduce network latency and accelerate transaction confirmations. In June, the Solana Foundation outlined plans to move from 400ms down to 200ms for that reason.
For traders, DeFi users, and apps that need quick confirmation signals, even a 50ms step can tighten how quickly the chain advances. Follow more market-moving updates in our Fintech & Crypto Alerts hub.
What comes after the 350ms change?
Three further 50-millisecond reductions are planned after the 350ms step, pointing toward the 200ms end goal. All four stages are targeted for mainnet activation in Agave v4.2, a validator client developed by Anza, though the schedule remains tentative.
The governing proposal, SIMD-0525, was approved and merged on May 14. That roadmap frames the 350ms cut as the opening stage of a broader latency push rather than a one-off tweak.
How does this fit Solana’s broader speed push?
Since genesis, Solana had kept a 400ms slot target. Moving first to 350ms—and signaling 300ms next—shows the foundation is willing to change a core timing parameter as it chases lower latency.
Whether the remaining steps land on the Agave v4.2 timeline will depend on how the network handles the new pace. For now, the headline is clear: Solana has entered its 350ms era and is already looking at the next cut.