Solana’s next consensus upgrade, Alpenglow, activates on mainnet in epoch 1064 on Wednesday, October 21, 2026, at about 15:00 UTC, cutting transaction finality from roughly 12.8 seconds to a target of around 150 milliseconds. The headline number is easy to misread. Finality is not block production: 150 milliseconds is how quickly a transaction becomes irreversible, not how often the network makes blocks. Block time was already reduced separately, from 400 to 200 milliseconds, in a staged rollout completed in October.
What finality actually measures
Finality answers one question: when can a transaction no longer be reversed. Today Solana reaches that point through TowerBFT, where validators vote by sending transactions and a block becomes final only after enough votes stack up over 32 slots, a process that takes about 12.8 seconds. During that window a transaction is visible but not yet settled. Alpenglow collapses the gap so confirmation and settlement happen almost together.
What Votor changes
Alpenglow replaces TowerBFT with a voting protocol called Votor, the first major replacement of Solana’s consensus layer since TowerBFT. Under Votor, validators send votes directly to one another instead of recording them as on-chain transactions, bundle those votes into aggregate certificates, and finalize a block in one or two voting rounds rather than 32 slots. Solana says the result is about 99% faster than TowerBFT and is designed to tolerate up to 20% malicious stake plus 20% offline stake.
What does not change
Execution is untouched. The Solana Virtual Machine, transaction formats, programs, and fee mechanics stay the same, and applications that only send transactions and read account state need no migration. For most users the effect is simple: wallets and apps keep working as they do today, while transactions settle almost immediately.
What operators must do
The work falls on validators and infrastructure providers. Before epoch 1064, validators must run an Agave-based client, such as Agave, Jito-Solana, or Harmonic Salsa on a release built on Agave 4.3.0; Firedancer and Frankendancer are not supported during the migration. Each validator must also hold at least 0.8 SOL in its vote account, above the rent-exempt minimum, to pay a Validator Admission Ticket fee that is charged at the start of each epoch.
What the metrics will show
Because vote transactions leave blocks entirely, any metric that counted them will report lower transaction totals without reflecting less real user activity. The confirmed and finalized commitment levels converge into one, and Geyser and gRPC consumers must handle a new bank_id field because a slot can now carry more than one candidate block. The rollout is phased: Votor ships first, while Rotor, the later replacement for Turbine’s block-propagation layer, is not yet scheduled.
The practical lesson is that speed arrives in layers, and each number means something specific. Block time, finality, and execution are separate properties. Alpenglow accelerates settlement without changing how transactions run, and that distinction is what users, operators, and people reading the metrics should track.
Source: BlockchainReporter.