Solana’s Alpenglow Consensus Upgrade Heads to Testnet With 150ms Finality Target
Solana is preparing to move Alpenglow into public testnet, beginning a staged replacement of TowerBFT that could reduce transaction finality from roughly 12.8 seconds to as little as 100–150 milliseconds.
Solana is preparing to activate Alpenglow, the network’s largest consensus upgrade to date, on public testnet this week. The migration will begin replacing TowerBFT with a new consensus system designed to bring finality down to roughly 100–150 milliseconds.
Alpenglow Begins Its Staged Migration
Anza CEO Brennan Watt indicated that the testnet activation is expected during Epoch 1042, which Solana Beach data projected to arrive within days of the announcement. The move is the first formal stage of a migration that has already been rehearsed for more than four months on a dedicated community cluster.
Alpenglow will move through testnet, Devnet and eventually Mainnet-beta. Each cluster must complete the migration before the upgrade advances to the next stage. Anza’s current schedule lists September 28 as a tentative date for activating features included in Agave v4.3 on Mainnet-beta, but that date is not a confirmed Alpenglow mainnet launch.
The upgrade does not require a new chain, network restart or token migration. Instead, Solana will change its consensus mechanism while the network continues operating.
Votor Targets Faster Finality
Alpenglow replaces TowerBFT with Votor, which changes how validators coordinate and record votes. Rather than writing consensus votes as blockchain transactions, validators exchange votes directly, reducing consensus traffic and freeing additional blockspace.
Votor can finalize blocks through two voting paths:
- One-round finality when validators representing 80% of stake participate.
- Two-round finality when participation reaches 60% of stake.
Anza estimates that the change could reduce finality from approximately 12.8 seconds to between 100 and 150 milliseconds. Finality is the point at which the network considers a transaction irreversible under its consensus rules, making the improvement relevant to exchanges, bridges and merchants that wait before crediting deposits, releasing assets or confirming payments.
The change is separate from Solana’s slot-time improvements. SIMD-0525 recently reduced slot time to 250 milliseconds, with a future stage targeting 200 milliseconds. Alpenglow instead focuses on how quickly validators confirm blocks as final.
Validator Requirements and Client Changes
Testnet validators participating in the migration must run Agave v4.3.0. Anza recommended Agave v4.3 for Mainnet-beta validators after a staged rollout covering operators representing 10% and then 25% of stake.
Firedancer and Frankendancer do not currently support the Alpenglow migration, so operators using those clients must switch to Agave v4.3.0 before the feature gate activates. The Firedancer team plans to end Frankendancer support when Alpenglow reaches mainnet, citing its maintenance and security burden, and will focus instead on the full Firedancer client.
What This Means
If the staged migration succeeds, Solana could offer near-instant economic finality without changing how users submit transactions or how applications execute them. Faster confirmation would improve settlement workflows for exchanges, bridges and payments, while freeing blockspace could support network efficiency. However, the upgrade remains a testnet deployment, and its mainnet timing depends on successful validation across every stage.