فا
← BACK TO THE WIRE
N°0193Solana2 MIN3 SOURCES

A Bigger Block, Not a Bigger Hot Spot: Solana’s 100M-CU Upgrade

Solana has activated a 100 million compute-unit block limit. The important design detail is that it expands aggregate, parallel capacity while leaving the per-account write ceiling unchanged.

SHARE
Solana
A Bigger Block, Not a Bigger Hot Spot: Solana’s 100M-CU Upgrade
IMAGE: AI-GENERATED

Solana Has More Room—But Only in Parallel

Solana activated SIMD-0286 on mainnet on July 29, 2026, at the start of epoch 1009. The upgrade raises the maximum compute budget of a block from 60 million to 100 million compute units (CUs), which the Solana Foundation describes as a 66% increase in block capacity.

The useful way to read that number is not “every application is now 66% faster.” It is that a block can carry more total work. The upgrade changes the maximum block-CU limit, while the maximum writable-account budget remains 12 million CUs and the maximum account-data-size delta remains 100 MB.

Why the Per-Account Limit Matters

That unchanged 12M-CU ceiling is the story. A heavily used account or program can still reach its per-block write limit at the same point as before. What changes is the amount of unrelated work that can fit beside it.

In other words, this is primarily a parallel-capacity upgrade. A busy market, payment rail, or popular program should crowd out less activity on separate accounts, but the upgrade does not remove contention inside a single hot account. The original SIMD makes this intent explicit: holding the writable-account limit flat while increasing the block limit is meant to create additional parallel capacity.

For builders, that makes account-layout choices more consequential, not less. Systems that distribute writes across independent accounts are positioned to benefit more directly than workflows concentrated on one shared state account.

What Changes for Infrastructure

Solana’s upgrade page says the change is not a breaking change and requires no indexing-format change. That lowers migration friction, but it does not remove operational work. Larger blocks take longer to execute and replay, so validators, RPC providers, indexers, and exchanges should test sustained 100M-CU conditions rather than assume a format-compatible upgrade is cost-free.

The near-term gain is headroom during demand spikes: more aggregate compute can be included in a block without changing how applications are built. The longer-term test is whether the surrounding infrastructure continues to propagate, execute, and replay larger blocks reliably.

Important Caveats

Capacity headroom is not a guarantee of a 66% gain in any application's throughput or lower fees: the 12M-CU writable-account ceiling remains, and demand and transaction mix still determine user outcomes.

The GitHub SIMD document still displays a “Review” status despite Solana Foundation pages reporting the feature as mainnet-live; readers should treat the document status as stale metadata unless the repository is updated.

TAGSSolanaSIMD-0286block capacityvalidatorsdeveloper infrastructure
Grounded sources3 REFS
  1. [01]100M CU Blockssolana.com
  2. [02]Solana Changelog: Mainnet raises block limits to 100M CUssolana.com
  3. [03]SIMD-0286: Increase Block Limits to 100M CUsgithub.com
Read next

Get the wire in your inbox

Every new signal, straight from the generator. No noise, unsubscribe anytime.

RSS AVAILABLE · NO SPAM