What happened
The Solana mainnet has deployed an update to increase throughput, accompanied by new versions of key client implementations.
Why it matters
Increasing the computational unit limit directly impacts network scalability, enabling developers to deploy more complex decentralized applications and reducing the risk of transaction rejections during periods of high load.
The Solana mainnet has successfully activated the SIMD-0286 improvement proposal, which officially raises the computational unit (CU) limit per block to 100illion. This change took effect on July 30, 2026, marking a significant expansion of the network's technical parameters.
Alongside the protocol activation, updated versions of major client implementations, including Agave and Firedancer, were released, as well as new releases of the SDK and LiteSVM. Synchronizing these components is necessary for the correct processing of the increased volume of computations in the new blocks.
This update aims to increase the blockchain's overall throughput, allowing the network to process more complex and resource-intensive transactions within a single time interval without changing the duration of the block itself.
Confirmed facts
- SIMD-0286 has been activated on the Solana mainnet.
- The computational unit (CU) limit per block has been raised to 100illion.
- New versions of the Agave and Firedancer clients have been released.
- New versions of the SDK and LiteSVM have been released.
- The date of publication of the change information is July 30, 2026.
Context
Changing block parameters is part of the ongoing work to optimize Solana's performance. The CU limit determines the maximum number of computational operations validators can perform when processing a single block, which is a bottleneck for complex smart contracts.
What remains unknown
- How quickly will network validators update their hardware and software to support the new limits?
- Will the immediate increase in the limit lead to higher transaction fees or network instability in the first hours after activation?
Editorial context
Confidence: high
The most likely consequence will be an increase in the complexity of deployable contracts and an increase in the volume of data in blocks. The next observable signal will be statistics on the usage of the new CU limits in real-world conditions and the absence of network downtime incidents. Material uncertainty remains regarding the impact on node hardware requirements, which could affect the composition of validators in the long term.