Solana’s Alpenglow upgrade entered a broader validation phase in September 2026, moving onto the public testnet after months of testing on a dedicated community cluster. The Solana Foundation says the upgrade targets roughly 150-millisecond consensus finality, compared with approximately 12.8 seconds under TowerBFT. That comparison is provisional: the 150-millisecond figure is a target for public testing, not a measured mainnet result, according to Crypto.News . Alpenglow reaches Solana public testnet Alpenglow’s public-testnet move is a further testing stage, not a completed mainnet deployment of every component. The upgrade is designed to change validator consensus and later block distribution across Solana. It targets consensus finality of about 150 milliseconds, versus approximately 12.8 seconds under TowerBFT. Finality is when a transaction or block is treated as settled by network consensus ; public testing will assess performance beyond the earlier dedicated cluster, and Crypto.News said the 150ms figure is a target rather than a measured mainnet result. Solana’s staged rollout starts with Votor, which replaces on-chain vote transactions with direct validator votes and aggregate certificates. Rotor—the planned block-propagation replacement for Turbine—comes later. Votor arrives before Rotor The initial rollout introduces Votor, which replaces on-chain vote transactions with direct validator votes and aggregate certificates, the Solana Foundation said. Votor is therefore the consensus-facing portion of the early deployment. Rotor is distinct from Votor. It is planned as a replacement for Turbine, Solana’s block-propagation mechanism, and will arrive later under the Alpenglow plan. The first phase of the public-testnet migration focuses on the validator-voting changes. In light of that split, it should not be read as the simultaneous replacement of TowerBFT voting and Turbine propagation; the broader networking overhaul remains ahead. Finality thresholds depend on stake participation Under the Alpenglow consensus proposal published through Solana Improvement Documents, finalization depends on stake participation: 80% in one voting round enables the fast route, while 60% across two rounds provides a slower route. The public testnet offers a setting to assess these conditions and the 150ms objective before a mainnet feature activation. Agave schedule shows tentative September 28 milestone Anza’s Agave v4.3 release schedule lists testnet feature activation as completed on August 19, 2026. It also sets out a September testnet restart and identifies September 28 as a tentative mainnet feature-activation milestone. Although the September public-testnet migration is an important operational step, it does not confirm a September 28 activation: the schedule explicitly warns that its dates may change, leaving the mainnet timing provisional. For now, Solana’s rollout sequence is clear: Votor is entering the public-testnet stage first, Rotor follows later, and the advertised 150ms finality figure remains a target awaiting validation. The Agave schedule provides the current mainnet milestone, subject to revision. Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
