Solana began activating three feature-gated Agave 4.2 upgrades on mainnet during the week of Aug. 17, marking a broad change to the network’s cost model and performance profile. The release lowers on-chain storage rent by 90%, raises the maximum transaction size by roughly 3.3 times, and starts a staged reduction in slot times from 400 milliseconds toward 200 milliseconds.

The rollout follows Firedancer’s arrival on mainnet in December 2025 and comes ahead of a larger consensus change planned for October. While Agave 4.2 also contains the full Alpenglow codebase, that part is not being turned on yet.

Cheaper on-chain storage

Under SIMD-0437, the lamports-per-byte constant used for rent falls from 6,960 to 696. In practical terms, the rent-exempt deposit for a standard SPL token account drops from about $0.16 in SOL to around $0.016, cutting account storage costs by an order of magnitude.

That shift is modest for a single account but more meaningful for applications that create large numbers of accounts. The source article says the change could materially lower costs for products such as on-chain order books, games with persistent player state, and tokenization platforms managing many holders.

The trade-off is a familiar one: lower storage costs can encourage more accounts and more chain state. According to the source article, Anza has argued that future work on state compression and account lifecycle management will address bloat separately from the rent schedule.

Transaction size expands to 4,096 bytes

A second upgrade, SIMD-0296, lifts Solana’s maximum transaction size from 1,232 bytes to 4,096 bytes through a new v1 transaction format. The change moves compute-budget configuration into the transaction header, freeing more room for instructions and payload data.

The larger format is intended to let more complex operations fit into one atomic transaction. The article identifies three main use cases: zero-knowledge proof verification, large multisig transactions with many signers, and on-chain BLS signature schemes that previously needed workarounds.

Existing applications are not required to migrate. Legacy and v0 transaction formats continue to operate as before, and only developers that want the larger size need to adopt v1. The source article notes that indexers and block explorers parsing raw transaction bytes will need to support the new layout.

A staged path toward 200ms slots

The third change, SIMD-0525, is aimed at cutting slot times from the current 400ms to 200ms. Rather than moving in one step, the plan uses four successive 50ms reductions, with each stage activated separately by validators.

A safeguard is built into the process: if block skip rates move above a defined threshold at any stage, the progression stops. Testnet has already demonstrated 300ms slots, according to the article, but the later reductions depend on how validators perform on mainnet under real-world conditions.

For users, shorter slots would mean quicker confirmations. For validators, the pressure goes in the other direction, because the compute budget per slot stays the same while the time available to process it is reduced.

Firedancer now, Alpenglow later

The article frames Agave 4.2 as part of a stacked infrastructure roadmap. Firedancer, Jump Crypto’s validator client, reached mainnet in December 2025 and now accounts for about 14% of mainnet stake across more than 20% of active validators. Operator data cited by the source says Firedancer has shown lower skip rates, fewer missed voting credits, vote latency around 1.002 slots, and fuller blocks.

Agave 4.2 changes the economics and throughput characteristics of the network those validators run, but the consensus overhaul is still waiting. Although the full Alpenglow codebase ships in this release, mainnet activation is deferred to Agave 4.3 in October 2026.

When enabled, Alpenglow is expected to replace both Proof of History and TowerBFT with the Votor voting algorithm, with a target of roughly 150ms finality and no on-chain vote transactions. The next confirmed step, however, is not that activation itself but the continued, gated rollout of Agave 4.2’s slot-time reductions on mainnet.

Source: crypto.news