Solana’s Alpenglow consensus protocol is now live on mainnet. The Solana Foundation’s official upgrade record says activation occurred at the start of epoch 1064 on October 21 at approximately 13:36 UTC.
The final TowerBFT-era block was slot 459,652,999, certified by votes from 446 of the network’s 654 validators. Alpenglow consensus began at slot 459,653,000. The verified transition converts yesterday morning’s scheduled upgrade into a completed mainnet event.
Alpenglow replaces TowerBFT voting with Votor, which sends votes directly among validators and aggregates them into certificates. The Foundation targets roughly 150-millisecond finality, down from about 12.8 seconds under the prior system. Execution, programs, transactions and fees were not replaced.
Only the Votor component is live. Rotor, the planned replacement for Solana’s Turbine block-distribution protocol, has not been scheduled. Claims that the entire Alpenglow architecture is fully deployed are therefore premature.
Moving routine validator votes off-chain will also change familiar activity metrics. A decline in vote transactions is mechanical and should not be reported as an equivalent decline in user demand. Indexers and analytics providers must separate consensus traffic from application activity before comparing pre-upgrade and post-upgrade transaction counts.
TOKEN RECON ASSESSMENT
The network crossed the highest-risk moment without a reported halt, but activation is not the same as proven performance. The useful postmortem will measure achieved certificate finality, skipped-slot behavior, validator participation and client stability over several epochs. If finality approaches the 150-millisecond target while applications remain stable, Alpenglow will be a genuine latency upgrade. If dashboards show falling transactions without removing old vote traffic from the baseline, the market will misread the network.
Sources
Solana Foundation: Alpenglow is live on mainnet
Solana Foundation: Alpenglow transition dashboard
