Solana’s Alpenglow Is Active on Testnet, While Anza’s Tracker Still Shows Pending

Solana’s Alpenglow Is Active on Testnet, While Anza’s Tracker Still Shows Pending

Key Takeaways

• A direct testnet RPC query now returns Alpenglow’s genesis certificate, while Anza’s tracker still lists the activation as pending.
• Votor aims to shorten consensus finality without changing transaction execution.

Details

Anza added Solana’s Alpenglow consensus upgrade to its pending testnet activation schedule. The tracker, edited on September 22, lists Agave v4.3.0 for the change and marks Firedancer and Frankendancer unsupported. Its Alpenglow row remains under pending testnet activation, with the activation field blank.

A direct getAgGenesisCert query to the testnet returned a genesis certificate at slot 444625255 on September 25, 2026, at 02:24 China Standard Time. Solana’s RPC documentation says the certificate is present once a cluster has migrated to Alpenglow consensus. The response therefore confirms the migration observed on testnet, even though Anza’s tracker, last edited September 22, still shows the activation as pending.

Alpenglow changes how validators agree that a block is final. Under SIMD-0326, the first phase replaces TowerBFT voting with Votor. Validators exchange votes directly and aggregate signatures into certificates, rather than placing votes in onchain transactions. One voting round can finalize a block with 80% of stake; the alternative uses two rounds with 60% thresholds. Rotor, a separate change to block propagation, comes later.

The Foundation describes expected finality of about 150 milliseconds, varying with stake distribution and network conditions. Transaction execution remains unchanged.

Market Analysis

For services waiting on final settlement, faster consensus could shorten one part of processing time. Exchange deposits and cross-chain transfers also depend on processes outside Solana consensus, so finality is only one part of their total completion time.

For operators, the RPC response provides verifiable evidence that the testnet cluster has migrated. Anza’s tracker still contains a pending row that does not reflect that response; mainnet activation remains a separate phase.

Anza’s Agave v4.3 schedule tentatively targets September 28 for resuming mainnet feature activation. That general milestone does not confirm an Alpenglow activation date for mainnet. A mainnet-specific activation and successful migration are the next verifiable steps for that network.

Sources

• Solana RPC: getAgGenesisCert — documentation says a present certificate indicates cluster migration; the testnet query returned slot 444625255 on September 25, 2026, at 02:24 China Standard Time.
• Anza: Feature Gate Tracker Schedule, edited September 22, 2026.
• Solana Foundation: Alpenglow upgrade guide, September 2026 update.
• SIMD-0326: Alpenglow, protocol design.
• Anza: Agave v4.3 release schedule, edited September 21, 2026.

Prepared with AI assistance from published protocol and rollout documents. The cover is an editorial illustration.

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