The Aug. 17 goal date for beginning Agave 4.2 mainnet characteristic activations arrived and not using a confirmed supply replace. Agave is Anza’s validator consumer for the Solana community.
Anza’s v4.2 launch schedule nonetheless reveals Aug. 17 because the tentative begin date however left the supply area clean. The empty area doesn’t show a delay or rule out a later replace. It means the goal date alone can’t set up {that a} characteristic gate is reside.
Anza really useful Agave 4.2 for normal mainnet adoption on Aug. 11. Its characteristic tracker individually continued to categorise the primary 4.2 slot-time gates as pending on mainnet, distinguishing software program adoption from the staged protocol rollout.
Terrifying Solana flaw simply uncovered how simply the “always-on” community may have been stalled by hackers
The replace mattered much less for what it shipped than for how briskly the community may really undertake it.
Agave 4.2’s greatest modifications stay staged
Anza’s Agave 4.2 feature-gate tracker, final up to date 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 didn’t listing a mainnet activation epoch for both gate.
The 250-millisecond gate was nonetheless pending on devnet after activating on testnet at epoch 1004, whereas the ultimate 200-millisecond gate remained pending on testnet. Solana’s slot-time plan requires 4 separate 50-millisecond reductions from the present 400-millisecond goal, with the community in a position to pause if block skip charges rise.
Within the Agave 4.2 rollout, lease follows a five-gate path. Solana plans to scale back lamports_per_byte, the fixed behind the refundable stability required for onchain storage, from 6,960 to 696. The intermediate values are 6,333, 5,080, 2,575 and 1,322. The Solana Basis’s lease overview stated all 5 gates have been inactive when accessed on Aug. 17, so the marketed 90% lower describes the finished sequence moderately than step one.
The obtainable materials additionally lacked a confirmed activation for the transaction change. Solana’s v1 transaction plan raises the utmost payload from 1,232 bytes to 4,096 bytes just for the brand new format. Legacy and v0 transaction limits stay unchanged.
Agave 4.2 contains code wanted to check Alpenglow, however the consensus overhaul is just not a part of the 4.2 mainnet activation. The Solana Basis’s launch overview says Alpenglow is predicted in Agave 4.3, focused for October 2026.
For customers and builders, the Aug. 17 date doesn’t make the 90% lease lower, 4,096-byte transactions and 200-millisecond slots reside as one package deal. A confirmed gate and its mainnet activation epoch would set up which a part of the roadmap has really moved into manufacturing.
