Solana has activated a mainnet change that lowers its target slot time to 350 milliseconds from 400 milliseconds, marking the first reduction of its kind since the network launched. The update is designed to shorten confirmation times by reducing the time allocated for each slot.
The network’s explorer shows the SIMD-0525 feature live on Mainnet Beta at slot 440,208,000 in epoch 1019. While the change is now active, it is only the opening move in a phased plan that could eventually bring Solana to 200-millisecond slots.
A staged path rather than a single jump
Solana’s approved sequence moves in four steps: from 400 milliseconds to 350 milliseconds, then to 300, 250 and finally 200 milliseconds. That means validators are not moving straight to the planned endpoint, but into a controlled transition with separate feature gates for each additional 50-millisecond cut.
According to the Solana Foundation, the network will not proceed to the next reduction if block skip rates rise too far. That safeguard is meant to let the network pause between stages rather than forcing the full rollout regardless of performance.
Why shorter slots matter
Reducing slot time compresses several parts of Solana’s block production cycle. Leaders have less time to finish blocks, the next leader has less time to receive transactions through Gulf Stream, and other validators have less time to replay blocks and cast votes.
Solana said improvements in validator clients, especially in Turbine and Replay, made the staged reduction plan possible. The intended effect is faster transaction confirmations for users, though the tighter timing also increases operational demands across the network.
What changes for validators
The upgrade does not alter the number of ticks in each slot, the four-slot leader span, or the number of slots in an epoch. Instead, the same slot structure now passes more quickly in real time because each slot is shorter.
As a result, validators move through epochs in less elapsed time. Solana has also classified the broader upgrade as a breaking change, and said the indexing changes required by the shift are still to be determined.
What remains unsettled
The activation of the 350-millisecond step does not set a confirmed timetable for the rest of the rollout. The Solana upgrade page does not list a calendar date or a specific epoch for the move to 300 milliseconds.
Anza’s tentative Agave v4.2 schedule targets all four staged reductions for mainnet activation, but future cuts remain conditional. For now, the next confirmed point is that any further 50-millisecond reduction will require a separate feature gate and will depend on block skip rates staying within acceptable limits.
Source: thedefiant.io