Solana Plans to Activate Alpenglow on Mainnet on October 21, 2026
The Solana Foundation plans to activate the Alpenglow consensus upgrade at the start of epoch 1064. The goal is to reduce transaction finality from approximately 12.8 seconds to 150 milliseconds.
Alpenglow on mainnet is planned for activation by the Solana Foundation on Wednesday, October 21, 2026, at approximately 15:00 UTC, at the start of epoch 1064. The upgrade changes Solana’s consensus mechanism and, according to its stated goal, is intended to significantly reduce the time needed to finalize transactions.
The timing is tied to the start of the epoch, so the exact switchover moment may not match the stated time to the second. In addition, after the epoch begins, the network is expected to operate with the current TowerBFT consensus for approximately 5,000 more slots. At the time of the announcement, Alpenglow had not yet been activated on mainnet; the upgrade had already been deployed on devnet and testnet.
Alpenglow on Mainnet Will Replace TowerBFT
The core of the upgrade is replacing the TowerBFT protocol with the new Votor consensus. Under it, validators send votes directly, and a block is expected to be finalized after one or two rounds of voting. This changes the rules by which the network reaches agreement that a transaction or block is irreversible.
Solana states a target finality of approximately 150 milliseconds, while TowerBFT is reported at approximately 12.8 seconds. However, 150 milliseconds is not a guaranteed constant. Only operation on mainnet under real-world load will show what times can be achieved over the long term.
Finality differs from the creation of a block itself or the initial display of a transaction in an application. It marks the point from which the result is considered definitive. The planned change is therefore relevant, for example, to exchanges, blockchain bridges, and payment applications that work with transaction confirmations.
Validators Need Agave 4.3
The deployment is classified as a breaking change, meaning an intervention by infrastructure operators is required. Validators must use a client built on Agave 4.3. Firedancer and Frankendancer clients are not supported during the migration.
The change does not affect validators alone. The project also points to adjustments related to vote processing and certain interfaces used for indexing. The readiness of services using Geyser, gRPC, or block indexing will need to be monitored.
The scope of the intervention is what distinguishes Alpenglow from a routine client update. The migration’s impact on network availability, applications, and data infrastructure has not yet been confirmed and will only become clear after activation on the production network.
What to Monitor During Activation
- whether epoch 1064 begins as planned on October 21 and whether the consensus switchover takes place,
- confirmation of the migration through the getAgGenesisCert RPC method,
- mainnet stability and the actual finality times measured after launch,
- validator readiness and the compatibility of indexing and data services.
The Solana Foundation has set the activation date, but the time remains approximate because it is tied to the epoch. It will also be important to see whether the target finality of approximately 150 milliseconds appears in normal mainnet operation, not only on test networks.
Sources
- Solana Foundation — Alpenglow – Confirms the planned activation in epoch 1064 on October 21, 2026, at approximately 15:00 UTC, the 150 ms target, technical changes, testnet/devnet status, and validator requirements.
- CoinDesk – Independently corroborates the timing and describes the importance of finality for exchanges, bridges, and payment use cases.
- Solana Changelog – Documents the recent release of Agave v4.3.0 and October changes to protocol infrastructure.
Verified and updated: October 14, 2026 06:22
