Solana Activates 250ms Slot Time at Epoch 1037, Fourth Step of SIMD-0525

Solana SOL$105.34+2.8% mainnet-beta crossed the epoch 1037 boundary at 05:06 UTC on September 18, activating 250ms slot times across the network. Anza confirmed the transition on X, quoting back its September 16 announcement that the feature gate was pending.

The activation marks the fourth step in SIMD-0525, Anza's five-stage slot-time reduction from 400ms toward a 200ms final target, authored by Brennan Watt. The network has now passed through 350ms and 300ms before reaching 250ms. One stage remains.

SIMD-0525's Three-Epoch Activation Sequence

Feature gates under SIMD-0525 take effect one epoch after they activate, not in the same epoch. For the 250ms reduction: the gate first appeared as pending at epoch 1035, became active at the epoch 1036 boundary, and first applied to block production at epoch 1037. The one-epoch lag is required so Turbine and shred-fetch filtering can apply revised per-slot shred limits before block production begins enforcing them, preventing valid shreds from being discarded during the boundary.

What 250ms Slots Change: Compute Limits, Epochs, and Leader Windows

Each slot-time stage under SIMD-0525 proportionally scales per-slot resource limits so the per-second execution budget stays approximately constant. At 250ms, the maximum block compute units are 37.5 million, down from 60 million at the 400ms baseline. Maximum data and coding shreds per slot fall from 32,768 to 20,480, per the SIMD-0525 specification.

With epochs fixed at 432,000 slots, the epoch wall-clock duration also contracts. An epoch at 250ms completes in roughly 30 hours, compared with about 48 hours at 400ms. Each leader window (four consecutive slots) is now 1.0 second, down from 1.6 seconds at the baseline.

SIMD-0525 identifies the shorter leader window as a market-structure improvement: a leader holding a 1.0-second window has less time to delay or reorder transactions before the next leader takes over. For oracle consumers and market makers that track freshness by slot count, 250ms granularity narrows the slot-time quantization error on time-sensitive decisions.

Solana developer Jacob Creech put it plainly: "Once again, Solana just got faster. 250ms slots are now live on Solana. See you at 200ms."

For Alpenglow validators, the Validator Admission Ticket scales with each stage. At 250ms, the VAT is 1.0 SOL per epoch, down from 1.6 SOL per epoch at the 400ms baseline. The reduction preserves the original ~0.8 SOL-per-day target as epochs shorten from 48 hours to 30 hours.

The 200ms Stage Ahead

The 200ms step is the final planned reduction under SIMD-0525. No activation date for the 200ms gate has been announced. The staged approach is deliberate: each step is observed under production conditions before the next feature gate is queued for activation.