Solana is preparing to activate Alpenglow, a major overhaul of its consensus layer, on mainnet-beta during epoch 1064. That epoch is expected to begin on Wednesday, October 21, 2026, near 15:00 UTC.
The change replaces the network’s longstanding TowerBFT voting system with a new protocol called Votor and aims to shrink the time required for a transaction to become irreversible from roughly 12.8 seconds to about 150 milliseconds—an improvement the Solana Foundation describes as approximately 99 percent faster.
Under the current design, validators cast votes by submitting on-chain transactions, and a block reaches finality only after sufficient votes accumulate across 32 slots.
Alpenglow discards that approach.
Validators instead exchange votes directly with one another and aggregate those votes into certificates.
A block can finalize after a single round if 80 percent of stake agrees, or after a second round at a 60 percent threshold.
The result is deterministic finality on a sub-second timescale rather than the multi-slot confirmation process used today.
The protocol is also engineered to remain live even when up to 20 percent of stake acts maliciously and another 20 percent is offline.
Importantly, the upgrade does not alter transaction execution.
The Solana Virtual Machine, program behavior, transaction formats, and fee mechanics remain unchanged.
Ordinary users and most application developers therefore require no action; wallets and dApps continue to function as before, with the practical difference that settlement becomes nearly immediate.
Infrastructure providers that stream block data, however, must adapt.
Vote transactions disappear from blocks entirely, which will sharply reduce headline transaction counts and reported throughput figures even if actual user activity stays constant.
Streaming interfaces such as Geyser also gain a bank identifier so consumers can handle the possibility of multiple candidate blocks within a single slot, and Proof of History ceases to pace block production.
The rollout is staged.
Votor, the voting and finalization component, ships with the Agave 4.3 client and constitutes the October 21 activation.
Rotor, a later phase that would replace the Turbine block-propagation mechanism with a single-relay design, remains unscheduled.
The upgrade has already operated on public testnet and on devnet, where it activated in late September.
Mainnet migration follows a carefully sequenced handoff on a live network: a feature gate activates at the epoch boundary, TowerBFT continues for roughly the first 5,000 slots, blocks temporarily stop carrying user transactions, validators form an Alpenglow genesis certificate once 82 percent of stake agrees, and consensus then transfers to Votor.
Anza, the team responsible for the Agave client, has characterized the effort as 18 months of preparation culminating in a one-slot switch.
Validator operators face two concrete requirements before the epoch begins.
They must run an Agave-based client (Agave, Jito-Solana, or Harmonic Salsa) built on version 4.3.0; Firedancer and Frankendancer are not supported during the migration window.
In addition, each vote account must hold at least 0.8 SOL above its rent-exempt minimum to cover a new per-epoch Validator Admission Ticket fee that replaces the prior on-chain vote fees.
Failure to meet the balance means the validator cannot vote or produce blocks in the following epoch.
Collectively, these changes represent the largest modification to Solana’s core consensus machinery since the network’s launch.
By moving votes off-chain, accelerating finality, and preserving the execution environment, Alpenglow is intended to deliver a more responsive network while keeping the developer and user experience largely continuous. Real-world performance will of course depend on live network conditions once the switch occurs.