Solana Agave 4.2 hits Aug. 17 target with mainnet gates pending

Solana's Agave 4.2 hit its Aug. 17 activation target with mainnet feature gates for slot-time cuts, rent reduction, and larger transactions still pending confirmation.

Anza's v4.2 release schedule still lists Aug. 17 as the tentative start date for feature activations but leaves the delivery field blank, according to the GitHub wiki. The Solana Foundation's feature-gate tracker, updated Aug. 14, classifies the first two slot-time gates as pending on mainnet.

The 350-millisecond and 300-millisecond slot gates recorded testnet activation epochs of 1000 and 1002 and devnet epochs of 1115 and 1118, but no mainnet epoch. The 250-millisecond gate remains pending on devnet after activating on testnet at epoch 1004, while the final 200-millisecond gate is still 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.

For users and developers, the Aug. 17 date does not make the 90 percent 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, while Alpenglow — the consensus overhaul targeting 150-millisecond finality — is expected in Agave 4.3 in October.

Rent and transaction gates remain staged

The rent reduction 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 — a 90 percent cut. 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 percent cut describes the completed sequence rather than the first step.

The transaction change also lacks a confirmed activation. 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.

Alpenglow targets October via Agave 4.3

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. Anza released Agave 4.2.0 as a stable version suitable for mainnet beta on Aug. 7, with a 4.2.1 pre-release following on Aug. 13. Agave 4.3 remains in alpha testing, with version 4.3.0-alpha.3 released Aug. 5 and explicitly marked as unsuitable for production use.

Alpenglow replaces TowerBFT with Votor, removing onchain vote transactions. Validators will exchange votes directly, while BLS signatures allow thousands of validator votes to be aggregated into compact certificates. The protocol targets finality near 150 milliseconds, down from roughly 12.8 seconds under TowerBFT. Anza opened a security competition offering up to 50,000 SOL, with a submission window running Aug. 5 through Aug. 19.

SOL traded at $75.54, down 1.2 percent over 24 hours, with a market cap of $44 billion, according to CoinGecko data.

The distinction between software adoption and protocol activation matters for Solana's roadmap credibility. Validators running Agave 4.2 carry the Alpenglow codebase but not the activation flag, which ships in 4.3. Until a confirmed gate and mainnet activation epoch appear, the Aug. 17 date marks a milestone on paper rather than a live protocol change.

This article is for informational purposes only and does not constitute investment advice.