Solana Cuts Per-Block Compute Limits to Match 350ms Slot Speed

The compute budget reset

Solana's core developers have proposed cutting per-block compute limits by more than half as the network prepares to shrink slot times to 350 milliseconds. The adjustment would reduce the per-slot compute unit budget from 48 million to 18 million, keeping the theoretical 48 million CU-per-second ceiling intact while forcing tighter per-block resource discipline.

The change addresses a throughput mismatch. Faster slots mean more leader handoffs per second, and the current 48M CU budget per slot would allow burst workloads that overwhelm the networking and scheduling layers during transitions. By lowering the per-slot cap, the network prevents any single leader from monopolizing compute during its shortened window.

Validator vote and timeline

Validator operators will vote on the parameter change through the standard feature-gate process. If approved, the new limits activate with the Agave v2.1 release, which targets testnet validation in the coming weeks before mainnet deployment. The proposal does not alter the total compute capacity per second — it redistributes it across more frequent, smaller blocks.

SOL price action reflects broader market momentum rather than the technical proposal alone. CoinGecko data shows SOL at $85.38, up 11% in 24 hours and 13.2% over seven days, with $4.3 billion in daily volume. The token's circulating supply sits at 583 million against a 632.5 million total supply.

The seven-day close series shows a steady climb from $75.54 to $76.83, with intraday ranges tightening in the latter half of the week. Volume has remained above $4 billion daily, suggesting sustained interest beyond speculative positioning.

The compute-limit reduction is a preventive measure, not a response to an observed failure. Testnet trials will validate whether 18M CU per slot provides sufficient headroom for current decentralized application workloads, particularly high-frequency trading programs and compressed NFT mints that operate near the existing ceiling.

Developers building on Solana should audit their compute unit consumption per transaction. Programs that currently request near-maximum budgets may need to optimize or split logic across multiple transactions once the lower per-slot cap takes effect.

The next milestone is the Agave v2.1 testnet deployment, where validator operators will stress the new limits under live traffic conditions. A successful testnet period would clear the path for mainnet activation, likely before the end of Q3 2026.