Solana has reduced its target slot time from 400 milliseconds to 350ms for the first time since the network launched. The change opens a four-stage plan under SIMD-0525 that could eventually bring slots down to 200ms, with resource limits adjusted proportionally at each step.
Solana has cut its target slot time from 400 milliseconds to 350ms, the first such reduction since the network launched. Solana Foundation vice president of technology Jacob Creech announced the change on Aug. 21, saying the network had entered "a new era of 350ms".
Average slot times were running at around 360ms at the time of writing, compared with the network's original 400ms target, according to Solana's slot time explorer.
SIMD-0525 targets four progressively shorter slots
The change is the first step under SIMD-0525, a Solana improvement proposal approved and merged on May 14 that introduces four progressively shorter slot configurations at 350ms, 300ms, 250ms and 200ms. Rather than moving immediately to the final target, Solana plans to activate each reduction separately, giving validator operators and client developers a chance to test network behavior as block production becomes faster.
Shorter slots mean block-production opportunities pass between validators more frequently. SIMD-0525 keeps the network's 64 ticks per slot and its four-slot leader window, but the amount of real time represented by each leader window falls with every reduction. At the previous 400ms target, four slots gave a leader a nominal 1.6-second window; a 350ms slot cuts that to 1.4 seconds, while 300ms would lower it to 1.2 seconds.
Resource limits scale down alongside slot duration so that processing demands over a given period do not rise simply because more slots are produced. At the original 60 million compute-unit baseline used in the proposal, the per-slot limit falls to 52.5 million CUs at 350ms, 45 million at 300ms, 37.5 million at 250ms and 30 million at 200ms.
Faster confirmations and shorter epochs follow
Confirmation latency is one of the main areas targeted by the change because Solana measures several parts of network operation in slots. With validators moving through slots more quickly, slot-based confirmation thresholds can be reached in less real-world time, and applications that rely on slot numbers to gauge how recent on-chain data is can receive finer timing intervals. SIMD-0525 identifies oracle users and automated market makers among applications that could benefit, particularly when decisions depend on the age of on-chain data.
Epoch duration will also fall because Solana plans to retain 432,000 slots per epoch. An epoch with 400ms slots runs about 48 hours; the move to 350ms cuts that to roughly 42 hours, while 300ms would bring an epoch to about 36 hours. Solana's annual slot calculations are adjusted alongside the change so protocol issuance stays based on real-world time rather than rising simply because more slots occur each year.
The network's next stop is 300ms
With the 350ms setting now active, SIMD-0525 identifies 300ms as the next stage in the sequence. The change would reduce the nominal four-slot leader window from 1.4 seconds to 1.2 seconds and bring an epoch down from roughly 42 hours to 36 hours. Each remaining stage, however, still requires its own separate feature activation before it takes effect.
Source: crypto.news
Trading involves risk.
Risk Disclaimer
