Solana’s Agave 4.2 validator-client release is recommended for mainnet adoption in August 2026. Feature activations are expected to start during the week of August 17. The changes affect transaction costs, payload capacity, and target slot timing, while Alpenglow remains inactive on mainnet.
Lower rent and expanded transaction capacity
Agave 4.2 introduces a phased reduction of rent costs, reaching 90% according to the release overview. The change is relevant to applications and users whose Solana activity depends on account-related storage economics.
The upgrade also raises the maximum transaction size from 1,232 bytes to 4,096 bytes through transaction v1. Larger payloads can provide more room for transaction instructions and associated data, subject to application support.
Shorter target slots and Alpenglow status
The release lowers target slot times from 400 milliseconds to 200 milliseconds. This is a validator and network-timing parameter rather than a guarantee of execution or settlement outcomes for every transaction.
Agave 4.2 contains code for testing Alpenglow. The consensus-related feature is not activated on Solana mainnet as part of this release.
What this means for PRIZRAK AI traders
For PRIZRAK AI traders, the relevant context is infrastructure: lower rent can change the cost profile of Solana-based activity, while the larger transaction limit may support more complex transaction construction. The reduced target slot time and the planned activation schedule are operational details to monitor. None of these changes provides a basis for a price conclusion, and Alpenglow should not be treated as active on mainnet in Agave 4.2.
Key points
- Agave 4.2 is recommended for Solana mainnet adoption in August 2026.
- Feature activations are expected to begin in the week of August 17, 2026.
- Rent costs are planned to fall in phases by 90%, and the transaction limit rises to 4,096 bytes through transaction v1.
- Target slot times move from 400 milliseconds to 200 milliseconds; Alpenglow testing code is included but not activated on mainnet.