Anza Sets August Target for 200ms Slots, Larger Transactions, and Rent Reduction as XDP Clears Supermajority

Anza published the Agave v4.2 release schedule on June 30, targeting August 17 mainnet feature activations that include the first stage of 200ms slot times, larger transactions, and rent reduction. Hours later, Anza validator engineer Tim Garcia confirmed that a supermajority of mainnet stake had enabled XDP, the networking layer that is a prerequisite for 100 million compute unit blocks.

The schedule and the XDP threshold arrived the same day, giving the protocol's most consequential upgrade cycle both a calendar and a confirmed network-level precondition.

Agave v4.2 Release Schedule: Eight Steps to August Mainnet Activations

Jacob Creech, Anza's developer relations lead, published the release schedule on June 30 pointing to the official Anza GitHub wiki. The schedule itself is a tentative eight-step plan spanning roughly seven weeks. Key dates:

The schedule explicitly notes that all dates are subject to change and is provided for informational purposes only.

The August 17 feature activation window targets three protocol changes. The lead change is the opening stage of SIMD-0525, a five-step slot-time reduction from the current 400ms toward an eventual 200ms, with each step (400ms, 350ms, 300ms, 250ms, 200ms) activated separately via feature gate; August targets step one. Alongside it: larger transactions, which raise the current 1,232-byte transaction size limit to support more complex multi-program interactions, and rent reduction, a gradual decrease in lamports-per-byte costs for on-chain accounts.

XDP Reaches Supermajority on Mainnet: What the Threshold Enables

As the schedule published, Anza engineer Alessandro Decina was flagging a parallel milestone. His June 30 post called it a "LAST CALL" for validators yet to enable XDP on mainnet. By 18:36 UTC, Garcia's confirmation put the count above the supermajority bar.

XDP (eXpress Data Path) is a kernel-bypass networking approach that cuts Turbine retransmit latency from roughly 250ms to sub-millisecond levels. It has been shipping in Agave since v3.0 and was present on over two-thirds of validator leaders at the time of the Agave 4.1 release last week. The supermajority matters because 100M compute unit blocks, a 66% increase over the current 60M CU limit, require XDP to be effective at the network level. With supermajority stake now running it, the networking substrate for that capacity increase is in place across the validators handling the bulk of block production.

Agave v4.2 as the Convergence Point: Slot Times, XDP Default, and Alpenglow Groundwork

The Agave 4.1 release identified v4.2 as the convergence point for three threads: XDP becoming the network default, the first slot-time reduction stage, and groundwork for Alpenglow activation. The schedule published June 30 gives those threads a concrete calendar, and XDP reaching supermajority stake the same day means the network has cleared one of the three prerequisites before testnet adoption even begins.

The 4.2 branch was cut June 29 per the schedule. The next visible checkpoint is July 6, when Anza plans to recommend v4.2 adoption for testnet validators. The mainnet volunteer phases in late July provide a staged rollout before the general adoption recommendation arrives August 10.

The throughput implication of the slot-time work is significant. All five SIMD-0525 stages activating successfully would double the number of blocks per second, compounding with the 100M CU limit increase. Both timelines are subject to change, but August 17 is now the stated target for the first stage.

Anza has been running a six-week major release cadence since the 4.0 cycle. If the 4.2 schedule holds, the August feature activations would arrive roughly on that pace from the 4.1 release of June 26.