Solana’s faster finality is live. What changes for users?
Oct 27, 2026
Solana has been running Alpenglow on mainnet since October 21, replacing a voting system that could take several seconds to finalize a block with one designed to finish in a fraction of a second. The Solana Foundation records the switch in epoch 1064, after 446 of 654 validators certified a genesis block.
The switch has happened, but 150 milliseconds is a target
Alpenglow replaced TowerBFT, Solana’s old consensus process, on October 21. In the old system validators put vote transactions onchain and a block gathered enough votes across later slots to become final. Votor, the live part of Alpenglow, carries votes directly between validators and combines them into certificates. A block can be finalized in one or two voting rounds.
The Foundation uses 12.8 seconds as a reference for old finality and roughly 150 milliseconds as the new target. Those numbers describe a protocol comparison, not two measurements taken from the same wallet under identical conditions.
The October 21 preparation report warned that unstaked RPC nodes could hear about finality later than participating validators, sometimes after another block is produced. Internet latency and an application’s chosen node add to what the user sees.
A wallet has more than one clock
Imagine paying for a coffee with a Solana wallet. The user first approves a transaction locally. The wallet sends it through an RPC service, the network includes it in a candidate block and validators certify that block.
The merchant’s system receives a status update and decides whether to hand over the coffee. Alpenglow changes the certification stage, not the time taken to open the wallet or the merchant’s own policy.
Fewer transactions on the chart can mean the same amount of use
Under TowerBFT, validator voting was part of the onchain transaction stream. Alpenglow’s validators communicate directly and put certification information in block footers, so those vote transactions no longer appear in the ordinary block transaction count.
A dashboard that displayed all transactions per second can drop after the switch without a drop in transfers, swaps or payments made by users.
Data services have to follow the winning block
A fast voting decision does not make every proposed block the winner. Solana’s updated data streams can expose more than one candidate bank for a slot, and Agave 4.3 tags events with a bank_id so clients can keep candidates separate.
An indexer grouping all data under a slot number can accidentally mix transactions from competing candidates into a record of a block that never existed in that form.
Validators have a new recurring bill
Removing onchain vote transactions alters validator costs. The Solana Foundation says voting previously cost about 1 SOL per epoch in transaction fees, paid from a validator’s identity account.
The new Validator Admission Ticket burns 0.8 SOL per epoch from its vote account, on top of the rent-exempt minimum. The ticket purchased at the start of one epoch admits the validator for the next.
The upgrade solves a narrower problem than payment apps do
Solana’s case for Alpenglow is powerful: if finality arrives much sooner, services that need irreversible settlement can stop waiting through several seconds of uncertainty.
The October 23 outside measurements support a material improvement on mainnet even though their 404-millisecond median was slower than the design target. Merchants and exchanges can choose to rely on that stronger, quicker status.
What remains to be measured
There is no single finality number that captures every user’s wait. Validator certificates, public RPC observations, wallet status and exchange credit times measure different steps.
The Foundation dashboard supplies live network readings, while outside monitors observe from their own nodes. Agreement across methods and providers over several days would show whether the quick results hold beyond launch week and how often the slow tail appears.
View sources >> Solana’s faster finality is live. What changes for users?
