Solana activates final 200-millisecond slots at epoch 1053

Solana cut its slot time to 200 milliseconds on Oct. 9, the fourth and final step of a rollout that halved block times from 400 milliseconds. The change took effect at epoch 1053, slot 454,896,000, at about 14:35 UTC, according to Solana's upgrade page.

The schedule comes from SIMD-0525, titled Reduce Slot Times and authored by Anza's Brennan Watt. It was first discussed in SIMD Discussion 469 and formally proposed in May. It laid out four 50-millisecond cuts: 350 milliseconds on Aug. 21 at epoch 1020, 300 on Aug. 28 at epoch 1024, 250 on Sept. 18 at epoch 1037, and 200 on Oct. 9 at epoch 1053. All four feature gates now show as live on mainnet, the page says. The page carries an October 2026 update stamp. The Agave 4.2 overview dates to August 2026 and the Alpenglow page to September 2026. Compass noted that no epoch-wide 200-millisecond average existed as of 15:21 UTC on Oct. 9, with the epoch less than an hour old.

CoinDesk previewed the final step hours before the boundary, writing that the network would move from 250 to 200 milliseconds at epoch 1053 around 15:00 UTC on Oct. 9, in its Oct. 9 report. The piece, by Shaurya Malwa and published at 1 a.m. EDT, used Anza's pre-estimate, which is why its 15:00 UTC differs by minutes from the 14:35 to 14:40 UTC times confirmed after the fact. Anza confirmed completion at 14:42 UTC, shortly after the network crossed into the epoch, Solana Compass reported at 15:25 UTC.

What changes for the network

Five block-production opportunities per second replace the previous two and a half. An epoch now takes about a day instead of two. "Blocks land twice as often. An epoch now takes about a day instead of two," Anza said, in remarks CryptoSlate carried in its Oct. 10 confirmation.

Faster slots mean smaller blocks. The per-block limit drops to 30 million compute units at 200 milliseconds from 37.5 million at 250, keeping total capacity roughly flat while a leader's four-slot window shrinks from 1.6 seconds to 800 milliseconds. Measured times run above the targets: the 250-millisecond stage averaged about 266 to 269 milliseconds in practice, and an early 200-millisecond sample across 1,413 slots came in near 222 milliseconds, CryptoSlate reported.

Each cut had its own feature gate, activated independently and taking effect about an epoch later. Core developers spaced the steps to watch cluster performance, with block skip rates as the gating check. The network would not move to the next reduction if skip rates ran too high, according to the SIMD-0525 proposal. The GitHub file still carries a Draft status label, which looks stale against the live activation, so this report treats the status field as outdated rather than current. No validator vote count for the reductions appears in the opened sources. Measured history shows targets running warm: Compass records stage averages of 415 to 423 milliseconds under the 400 target, 365 to 367 under 350, 315 to 317 under 300, and 266 to 269 under 250, in its Oct. 9 confirmation.

This is distinct from the Sept. 18 move to 250 milliseconds covered earlier. The 200-millisecond activation is a new event at a new epoch, confirmed after the fact rather than scheduled.

Alpenglow stays separate

Solana Foundation vice president of technology Jacob Creech celebrated the completion and named Alpenglow as the next milestone, CryptoSlate reported. The slot-time cut changes block-production cadence. Alpenglow, tracked as SIMD-0326, replaces the TowerBFT consensus with a design called Votor and targets about 150 milliseconds to finality against roughly 12.8 seconds today, leaving execution unchanged. Agave 4.2 ships Alpenglow code without activating it on mainnet, with activation expected in Agave 4.3 targeted for October, Solana's release overview says. Testnet and devnet runs are done. No mainnet date has been announced, as noted Oct. 10. Blockhash expiry now sits at 30 seconds, or 150 blocks, against 60 seconds at the old 400-millisecond cadence.