Solana moves Alpenglow Upgrade to testnet, Targeting 150ms Finality

Solana's Alpenglow upgrade moved to the network's public testnet on Tuesday, with developers aiming to cut payment finality from 12.8 seconds to 150 milliseconds.

The 150ms figure is a target, not a measured result. Developers "will try" to reach that level as part of the testnet phase, which follows more than four months of Alpenglow running on a smaller, dedicated devnet created specifically for the upgrade.

What sub-second finality actually changes

Finality is the point at which a payment becomes irreversible. Today, exchanges, bridges and merchants wait for it before crediting deposits, releasing funds on another chain or accepting a payment. At 12.8 seconds, that wait is short enough for retail flows but long enough to shape how trading apps, bridges and automated systems behave.

At 150ms, that wait effectively disappears. Alpenglow would let exchanges, bridges and merchants treat payments as irreversible almost immediately, per the report. The narrower window opens room for application designs that were not practical at 12.8 seconds: order books and matching engines that settle in the same breath as a trade, bridges that release liquidity within a market data tick, and automated strategies whose edge depends on faster confirmation than the chain used to allow.

How Alpenglow gets there

The speed comes from replacing Solana's current TowerBFT consensus with a voting protocol called Votor. Under TowerBFT, validators record their votes on the blockchain and stack enough of them across 32 slots before a block becomes final. Under Votor, validators send votes directly to one another and can settle on a block after one or two rounds, removing the long chain of onchain votes.

The application layer does not change. Applications keep executing transactions as they do today, and users will not need to change wallets or how they send funds, per the report.

Where the rollout actually stands

Validators taking part in the testnet migration need Agave 4.3, the main Solana client maintained by Anza. Anza recommended Agave 4.3 to all mainnet validators on Sept. 21, after first rolling it out to operators responsible for 10% and then 25% of staked SOL.

The initial testnet migration will not support Firedancer or Frankendancer, the alternative clients intended to reduce Solana's reliance on a single piece of software. Their absence means the first Alpenglow migration runs entirely through Agave. The report does not state whether Firedancer or Frankendancer support is planned for a later migration phase.

Sept. 28 appears in Anza's schedule as a tentative date for turning on Agave 4.3 features on the main network. It is not a confirmed Alpenglow launch date, and Anza's tracker still listed the testnet switch itself as pending early Wednesday.