Solana merges the final flag to start turning on Alpenglow, with a Testnet target of July

Solana's official developer changelog, published July 2, 2026, reports that Anza's Agave validator client v4.1.0 has "merged the final feature flag for turning on Alpenglow" — the consensus redesign that has been in development for months. Per the post, this is "the first step of validators switching to Alpenglow in v4.3."

The rollout is staged, and the changelog is explicit about the limits. Only the Votor portion of Alpenglow ships first, "starting in v4.3." The activation mechanism, called Alpenswitch, is "expected on Testnet in July and on Mainnet in August," gated behind an epoch-based feature flag that this pull request turns on. Those dates are the team's own projection, not confirmed shipping dates.

The same changelog covers a wide release week beyond Alpenglow. Agave v4.1.0 shipped alongside Solana Kit v7.0.0, Cloudbreak v0.1.2, Superbank v0.5.0, Solana Go v1.22.0, the Stake Rust SDK v4.3.1, OtterSec's Anchor v1.1.2 and v1.0.3, and Anza's Mollusk v0.13.4. On the "RPC 2.0" track, Cloudbreak added getTokenSupply, getVoteAccounts, and getTokenLargestAccounts, while Superbank added gRPC streaming, getEpochInfo, and transaction-version support. Anza also continued cross-client conformance fuzzing across Agave, Firedancer, and Mithril, targeting syscalls and transaction costs so clients behave identically.

Key facts

• Agave v4.1.0 merged the final feature flag to begin activating Alpenglow; first step toward the v4.3 switch. (Solana developer changelog, Jul 2, 2026)
• Only the Votor portion of Alpenglow releases first, starting in v4.3. (Same)
• Alpenswitch "expected" on Testnet in July, Mainnet in August — projected, not confirmed. (Same)
• Other releases: Solana Kit v7.0.0, Cloudbreak v0.1.2, Superbank v0.5.0, Solana Go v1.22.0, Anchor v1.1.2/v1.0.3, Mollusk v0.13.4. (Same)
• RPC 2.0: Cloudbreak added three RPC methods; Superbank added gRPC streaming, getEpochInfo, and transaction versions. (Same)

The real-world read

This is Solana's own engineering blog — a primary source for what code merged, but a self-published one, so its framing and timeline should be read as the project's account, not independent confirmation. A merged feature flag is not a live network upgrade: nothing about Alpenglow is running in production yet. The changelog itself flags this by shipping only Votor first and using "expected" for both the Testnet and Mainnet windows — language that leaves room to slip, as consensus rollouts often do. The post lists no benchmarks, no finality-time figures, and no risk discussion for Alpenglow, so any performance claims circulating elsewhere do not trace to this source. What it does show is method, not marketing: continued cross-client fuzzing between Agave, Firedancer, and Mithril to keep independent validator implementations consistent before a consensus change lands.

Opinion, and whose

The changelog offers no forecasts or valuations — only the team's own timing estimate that Alpenswitch reaches Testnet in July and Mainnet in August. Treat those as Anza/Solana projections, subject to change.

Sources

• Solana developer changelog (solana.com/news, Jul 2, 2026) — primary/Tier 1; provided all release versions, the Alpenglow flag merge, the Votor-first and Alpenswitch timeline, and the RPC 2.0 and conformance details. Self-published by the project; engineering release notes, not independent verification and not sponsored marketing.

This is news coverage, not financial advice. Nothing here is a recommendation to buy or sell anything.