Solana has begun the first stage of a planned reduction in block time, moving from 400 milliseconds toward 200 milliseconds through a four-step rollout built into Anza’s Agave software. The first reduction, to 350 milliseconds, is scheduled for epoch 1020, part of the network’s roughly two-day operating windows used to coordinate changes.

If the full sequence is completed, Solana would increase its output from about 144 blocks per minute to 300. The network’s developers have presented the shift as a speed increase without a rise in total throughput, because each block is expected to shrink in line with the shorter timing so that the overall load remains unchanged.

Four stages, each activated separately

The rollout is structured as four 50-millisecond cuts: 400ms to 350ms, then 300ms, 250ms, and finally 200ms. Rather than switching all at once, each stage is enabled separately, allowing operators to assess performance before the next reduction is turned on.

At the end of the process, Solana would produce a new block every one-fifth of a second. That would roughly double block production from around two and a half blocks per second today to about five per second, or 300 blocks each minute.

Validators can stop the timetable if reliability slips

The plan is not fixed. Validators can pause the sequence at any point if the network begins skipping too many blocks, and Anza has described the schedule as tentative for that reason.

A live tracker published for the change showed 96.7% of stake already running the required software. The same tracker indicated that 690 validators representing 435 million SOL in active stake were behind the upgrade. Reliability remains a central concern as the network tests whether shorter block intervals can be sustained without increasing instability.

Recent incidents keep pressure on network stability

That caution follows a difficult period for network operations. In August, Solana came close to a network halt after a routing fault took 28.83% of staked SOL offline. Earlier in 2026, validators were also slow to adopt an urgent patch.

Those episodes have left stability as the main open question around the block-time reduction. The technical case for faster blocks may be straightforward, but the practical test is whether the chain can maintain a steady skip rate while blocks arrive more frequently.

Speed comparisons do not settle the finality question

The planned timing change would widen Solana’s lead over older blockchains on raw block production. Bitcoin produces one block roughly every 10 minutes, while Ethereum runs at about 12 seconds per block. At 200 milliseconds, Solana would generate around 3,000 blocks in the time Bitcoin produces one, and the gap with Ethereum would also increase.

Even so, faster block production is not the same as faster final settlement. The source article noted that Solana needs about 13 seconds for transaction finality, compared with roughly 13 minutes for Ethereum and about an hour for Bitcoin. Anza is separately working on Alpenglow, a consensus overhaul aimed at 150ms finality, with a first phase penciled in for the third quarter through the Agave 4.3 release.

Next step is the first cut at epoch 1020

Solana co-founder Anatoly Yakovenko said an earlier reduction from 800 milliseconds to 400 milliseconds took two days, offering a loose point of reference for how quickly the remaining stages might proceed. However, no firm dates have been committed for the rest of the sequence.

For now, the confirmed milestone is the first move to 350 milliseconds at epoch 1020. From there, progress will depend on validator support and on whether the network can absorb each step without a meaningful rise in skipped blocks.

Source: beincrypto.com