Agave 4.2 target date arrives; Solana gates still pending

Anza, the developer of the Agave validator client for Solana, recommended Agave 4.2 for general mainnet adoption on Aug. 11 and set Aug. 17 as the tentative start for mainnet feature activations. The project’s release schedule left the delivery field empty and its feature-gate tracker shows multiple gates still pending on mainnet.

The tracker records the 350-millisecond and 300-millisecond slot-time gates as active on testnet at epochs 1000 and 1002, and on devnet at epochs 1115 and 1118, respectively. Neither gate has a listed mainnet activation epoch. The 250-millisecond gate is active on testnet at epoch 1004 but remains pending on devnet, and the final 200-millisecond gate is pending on testnet. Solana’s slot-time plan reduces the target slot duration in four 50-millisecond steps from 400 ms to 200 ms and permits pausing reductions if block skip rates increase.

The rent change follows a five-stage path for lamports_per_byte, the parameter that sets refundable balances for on-chain storage. The staged values are 6,960, 6,333, 5,080, 2,575 and 1,322, moving toward a target of 696. The rent overview showed all five gates inactive when checked on Aug. 17, so the advertised 90% reduction describes the full sequence rather than a single immediate cut.

Solana’s v1 transaction format would raise the maximum payload for new transactions from 1,232 bytes to 4,096 bytes. Documentation indicates the increase applies to the new v1 format only; legacy and v0 transaction size limits remain unchanged. The feature tracker does not list a confirmed mainnet activation epoch for the transaction-size change.

Agave 4.2 includes code to test Alpenglow, the planned consensus overhaul, but the overhaul is not part of the 4.2 mainnet activation. The Solana Foundation’s release information targets Alpenglow for inclusion in Agave 4.3, currently aimed for October 2026.

With the delivery field blank and several gates marked pending, the Aug. 17 target date does not by itself indicate which Agave 4.2 features are active on mainnet. A listed mainnet activation epoch for each gate is needed to record when particular changes move into production.