Solana Cuts Slot Time to 250ms at Epoch 1037, Capacity Flat

Solana's target slot time fell to 250 milliseconds on Friday morning, the third of four staged cuts written into SIMD-0525. The network now aims at four slots a second, up from about 3.3, which CoinDesk called a speed increase of nearly 17%. Throughput does not move at all. Each slot is allowed proportionally less computation than the one it replaces, so blocks arrive faster while the ceiling on work stays where it was. Solana Compass and CryptoTicker both time the change to the epoch 1037 boundary, about 05:01 UTC; CoinDesk and crypto.news date it to Friday without naming an epoch or a clock time.

What shrinks along with the slot

The block compute limit is now 37.5 million units, the meter Solana bills execution against. Solana Compass and CryptoTicker give the figure it replaces as 45 million, the ceiling that applied at 300-millisecond slots, and crypto.news arrives at the same 37.5 million by scaling a 60 million baseline. That ladder does not square with this desk's own reporting. In July the network lifted the block ceiling to 100 million units at epoch 1009, and on the August reading of the first cut the 250-millisecond rung would sit at 62.5 million. The 100 million figure appears in none of Friday's accounts, and we could not establish which ladder the proposal is being scaled against. One further cap moves with it. The writable-account limit, which bounds how much compute a single hot account can absorb in one block, drops to 15 million from 18 million.

A shorter clock for wallets and indexers

A validator's turn at producing blocks now lasts one second, down from 1.2, and an epoch still holds 432,000 slots but completes in about 30 hours instead of 36. The window that matters to anyone signing a transaction is the blockhash. It expires after 150 blocks, so its wall-clock life falls to about 37 seconds, a figure Solana Compass puts at 37.5 and CryptoTicker at roughly 38 against about 48 before. Offline signing, hardware approvals and anything with a human pause in the middle now have less room. Infrastructure ingests more individual blocks for the same throughput, and applications that hard-code a slot duration need updating.

"The amount of computation and data permitted in each slot falls by the same proportion as the slot duration," the proposal said.

On the other side, applications read fresher chain data, the window in which a quoted price can slip narrows, and fewer transactions should fail. crypto.news names oracle-fed markets and automated market makers as the clearest beneficiaries. The cadence of upgrades has been quick: Solana set 9 September for Transaction V1 and a 4,096-byte transaction ceiling less than two weeks ago.

Two versions of what validators were asked to do

The instruction to operators does not read the same way twice. Solana Compass says Anza, the firm behind the Agave client, asked for 25% of mainnet-beta stake to be running Agave v4.3 by the end of Friday, with the v4.3.0-rc.1 release published on 11 September. CryptoTicker says operators must upgrade to that release candidate by the end of 18 September. A stake threshold and a blanket upgrade requirement are not the same instruction, neither account corrects the other, and they do not reconcile. Anza's own line, carried by Solana Compass, was that 250ms slots activation was "now pending on mainnet-beta".

The last fifty milliseconds

One rung is left. At 200 milliseconds the network would produce five slots a second and an epoch would complete in about 24 hours, and that stage is already live on devnet and testnet. No mainnet date has been set for it. Progression depends on the block skip rate, the share of slots that pass with no block produced, staying acceptable at 250. Solana's own upgrades page had not caught up on Friday afternoon: read at 11:30 UTC it still listed the 250-millisecond stage as devnet and testnet only, with a mainnet date to be determined, hours after four outlets reported the activation. The page that settles the compute ladder is the same one that has not yet recorded the change.