Solana’s Alpenglow upgrade hits 54ms median finalization on testnet

Solana’s Alpenglow upgrade is live on testnet. It is finalizing blocks in a median of 54 milliseconds.

That is faster than the team’s own target. It is also dramatically faster than Solana’s mainnet today, which previously averaged approximately 12.8 seconds to reach finality.

What actually changed

Alpenglow activated on Solana’s public testnet on September 24, 2026, at slot 444,625,255, after a 17-minute countdown. Devnet followed a day later, on September 25, at slot 504,148,999.

The headline component is Votor, a new consensus mechanism. It replaces TowerBFT, the voting system Solana has relied on for years.

This is the first major consensus overhaul since Solana launched in 2020.

The design target for finality was 100-150 milliseconds. The testnet result of 54 ms landed well under the low end of that range.

How Votor gets there

Validators submitted votes as on-chain transactions, and those vote transactions traditionally consumed 50-75% of block space.

Votor moves voting off the chain. Validators exchange BLS-signed votes directly with one another over a peer-to-peer network.

Those votes get aggregated into certificates. BLS is a signature scheme that allows many individual signatures to be bundled together, so a stack of validator votes can be packaged into one compact proof of agreement.

The upgrade also introduces dual finalization paths, meaning blocks have two possible routes to being finalized. It adds a “20+20” fault-tolerance model as well, which is expected to improve network resilience and performance.

What does not change is just as notable. The Solana Virtual Machine, transaction formats, and fee structures all remain the same.

A long road through governance

The proposal was formalized as SIMD-0326 and went to a validator vote in September 2025.

It passed with 98.27% approval. Stake participation during the vote came in at 52%.

What this means for Solana

The immediate question is mainnet. The activation date there remains undecided.

Mainnet deployment is tied to the Agave 4.3 release, which is expected in late September or October 2026. That timeline depends on what developers observe from the testnet and devnet runs.

The key things to watch are straightforward. First, whether Agave 4.3 ships on its expected schedule. Second, whether testnet and devnet observations surface any issues that delay mainnet activation.

Third, and most important, whether mainnet finality lands anywhere near the testnet’s 54 ms median. A result in the 100-150 millisecond design range would still represent a dramatic leap from approximately 12.8 seconds.