Solana activates Alpenglow, targeting 150ms transaction finality

Solana activated Alpenglow on its main network on Oct. 21, replacing the consensus system it had used since 2020 with one designed to make transactions final in about 150 milliseconds, according to the Solana Foundation’s Alpenglow upgrade page. The change could let exchanges, merchants and applications treat completed transactions as irreversible much sooner. The 150ms figure is a target; it is not an independently confirmed measure of performance after launch.

Under the previous system, TowerBFT, finality took about 12.8 seconds. Solana’s Foundation describes Alpenglow as live from epoch 1064, which began on Oct. 21. The shift was built by core development team Anza. Decrypt reported that validators retired TowerBFT at slot 459,653,000, carrying the existing ledger into the new consensus system.

How does Alpenglow change transaction confirmation?

Alpenglow changes how validators agree that a block is final: instead of sending votes as transactions on Solana, validators send votes directly to one another and combine them into certificates. The Foundation says a block can then become final after one or two rounds of voting. That replaces TowerBFT’s process, in which validator votes accumulated over 32 slots.

For users, faster finality narrows the gap between seeing a transaction confirmed and knowing it can no longer be reversed. That can matter to an exchange crediting a deposit, a merchant accepting payment or an application settling a trade. The improvement is distinct from Solana’s separate reduction in slot time, which the Foundation says went from 400 milliseconds to 200 milliseconds. Slot time measures the pace of block production; finality measures when a transaction is irreversible.

The upgrade does not change how transactions execute. The Foundation says the Solana Virtual Machine, programs and fees remain the same, and wallets and apps continue to work as before. Users do not need to change how they sign, send or approve transactions.

What changes for validators and developers?

Validators must run a supported Agave-based client and keep at least 0.8 SOL in their vote account above its rent-exempt minimum to pay the Validator Admission Ticket. For developers and data providers, the transition carries more work: the Foundation flags changes to streaming data, block handling and the meaning of “confirmed” and “finalized.” Vote transactions also leave blocks, so transaction counts that include votes will no longer be directly comparable with earlier counts.

Those requirements make the transition more involved for network operators than for ordinary wallet users. The protocol’s stated fault model allows it to tolerate stake representing 20% of the network acting maliciously and another 20% offline. That is a design claim, not evidence that the system has faced those conditions on mainnet.

What should Solana users watch next?

The first signal is whether observed finality on mainnet matches Anza’s roughly 150ms target across ordinary network conditions. The launch establishes that the new consensus is active; it does not, by itself, show how consistently applications or exchanges will experience that speed.

The next protocol change to track is Rotor, which the Foundation says is planned for a later release but has no scheduled date. It would replace Turbine, Solana’s system for spreading block data across the network. For now, Alpenglow’s trade-off is clear: a faster path to irreversible settlement, alongside new operating and data-handling requirements for validators and infrastructure providers. The practical test is whether that faster finality holds while the network continues to operate reliably.

Source material

• Solana Foundation’s Alpenglow upgrade page — solana.com