Solana’s Alpenglow testnet switch remains pending

Solana’s Alpenglow consensus upgrade has not yet switched on across the public testnet, according to Anza’s feature gate tracker, edited September 22, which lists the activation as pending. The upgrade targets finality in roughly 150 milliseconds, down from about 12.8 seconds under the current TowerBFT system. That would shorten the wait for exchanges, bridges and merchants that need a transaction to be irreversible, but the target is not a live mainnet result.

How would Alpenglow change Solana’s finality?

Alpenglow replaces TowerBFT’s voting process with Votor, in which validators send votes directly to each other and combine them into certificates. Under TowerBFT, votes are recorded as transactions and accumulate across 32 slots before a block is final. Votor can finalize a block after one or two rounds of voting, according to the Solana Foundation’s Alpenglow upgrade guide.

The Foundation describes 150 milliseconds as an expected finality time, not a fixed guarantee. The actual time depends on stake distribution and whether a block finalizes in one round or two. Under the proposed system, “confirmed” and “finalized” would describe the same state; today, “confirmed” can arrive earlier, while “finalized” carries the longer TowerBFT wait.

What is confirmed about testing and rollout?

The tracker lists Alpenglow under pending testnet activation, with Agave 4.3 as the required version. It also marks Firedancer and Frankendancer as unsupported for this activation. That makes client readiness a practical condition for the first testnet switch: unlike the main Agave validator software, those alternative clients cannot yet take part in this Alpenglow test.

Solana’s upgrade guide says validators and developers have been testing the consensus algorithm on a separate community cluster for months, using restarts to rehearse the transition. That is distinct from activation on the established public testnet. The guide places the expected mainnet activation in the third quarter of 2026, but the tracker’s pending status means the public testnet switch remains a milestone to watch.

What should users and operators watch next?

The next signal is a change in Anza’s tracker from pending testnet activation, followed by evidence that validators can migrate together on Agave 4.3. Operators will also need to watch whether Firedancer and Frankendancer gain support before any broader rollout. Solana’s guide says transaction execution, programs and fees are intended to stay the same, while consensus and finality change; a separate phase, Rotor, would later replace the Turbine block-propagation system.

For now, the comparison is between a stated target and a live baseline: Alpenglow aims for roughly 150ms finality, while TowerBFT takes about 12.8 seconds. Whether that gap holds on the public testnet—and when the feature gate advances toward mainnet—are the next concrete measures of progress.