Agave 4.2 Mainnet Feature Activations Arrive Without Confirmed Delivery Update

The Aug. 17 target date for starting Agave 4.2 mainnet feature activations arrived without a confirmed delivery update. Agave is Anza’s validator client for the Solana network.

Anza’s v4.2 release schedule still shows Aug. 17 as the tentative start date but left the delivery field blank. The empty field does not prove a delay or rule out a later update. It means the target date alone cannot establish that a feature gate is live.

Anza recommended Agave 4.2 for general mainnet adoption on Aug. 11. Its feature tracker separately continued to classify the first 4.2 slot-time gates as pending on mainnet, distinguishing software adoption from the staged protocol rollout.

Agave 4.2’s biggest changes remain staged

Anza’s Agave 4.2 feature-gate tracker, last updated Aug. 14, listed the gates for 350-millisecond and 300-millisecond slots as pending mainnet activation. The tracker recorded their testnet activation epochs as 1000 and 1002, respectively, and their devnet activation epochs as 1115 and 1118. It did not list a mainnet activation epoch for either gate.

The 250-millisecond gate was still pending on devnet after activating on testnet at epoch 1004, while the final 200-millisecond gate remained pending on testnet. Solana’s slot-time plan calls for four separate 50-millisecond reductions from the current 400-millisecond target, with the network able to pause if block skip rates rise.

In the Agave 4.2 rollout, rent follows a five-gate path. Solana plans to reduce lamports_per_byte, the constant behind the refundable balance required for onchain storage, from 6,960 to 696. The intermediate values are 6,333, 5,080, 2,575 and 1,322. The Solana Foundation’s rent overview said all five gates were inactive when accessed on Aug. 17, so the advertised 90% cut describes the completed sequence rather than the first step.

The available material also lacked a confirmed activation for the transaction change. Solana’s v1 transaction plan raises the maximum payload from 1,232 bytes to 4,096 bytes only for the new format. Legacy and v0 transaction limits remain unchanged.

Agave 4.2 includes code needed to test Alpenglow, but the consensus overhaul is not part of the 4.2 mainnet activation. The Solana Foundation’s release overview says Alpenglow is expected in Agave 4.3, targeted for October 2026.

For users and developers, the Aug. 17 date does not make the 90% rent cut, 4,096-byte transactions and 200-millisecond slots live as one package. A confirmed gate and its mainnet activation epoch would establish which part of the roadmap has actually moved into production.