Solana is scheduled to swap out its consensus engine today. The Alpenglow upgrade is set to activate at approximately 13:20 UTC, with a target of shrinking finality from 12.8 seconds to 150 milliseconds.
The activation is pegged to epoch 1064 on October 21, 2026. If it goes as planned, the network retires TowerBFT, the voting system it has relied on for a long time, and moves to a new protocol called Votor.
What Alpenglow actually changes
Under TowerBFT, deterministic finality on Solana took about 12.8 seconds. Alpenglow aims to bring that down to roughly 150 milliseconds.
The engine behind that jump is Votor. Instead of validators recording their votes as transactions inside blocks, Votor collects direct votes from validators off-chain. It then bundles them using BLS signatures, a cryptographic method that compresses many signatures into one compact proof.
Block production time is also expected to tighten to around 200 milliseconds after the upgrade.
Notably, the change sits at the consensus layer only. The existing transaction execution layer and user interfaces are meant to stay the same, so wallets and apps shouldn’t need to relearn how Solana works.
Testing gave the upgrade a strong preview. On public testnet and devnet, median finality came in as low as 54 milliseconds, well under the 150-millisecond mainnet target.
How Solana got here
Alpenglow didn’t arrive by surprise. Validators approved the core consensus proposal, SIMD-0326, in September 2025 with 98.27% support.
The roughly year-long gap between approval and activation reflects how cautious blockchain teams have to be with consensus changes. Unlike a feature update, swapping the voting mechanism touches the part of the network that decides what counts as true.
To participate under the new system, operators need to run Agave-based clients, typically version 4.3.2. They also need to cover a Validator Admission Ticket, or VAT, fee totaling 0.8 SOL per epoch.
On the security side, the new design is built to keep running even if 20% of stake behaves maliciously and another 20% is offline.
What this means for Solana users, validators, and SOL
The most immediate thing to watch may look like bad news but isn’t. Reported transactions per second may drop temporarily after activation.
That dip has a simple explanation. Under TowerBFT, vote transactions were counted inside blocks, inflating throughput numbers. Once those votes move off-chain, the headline TPS figure loses that padding, even as more block space opens up for actual user transactions.
For validators, the trade-off is clear. They get a leaner consensus process but take on a client upgrade requirement and the 0.8 SOL per-epoch VAT cost.
Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.