Solana Moves Alpenglow Consensus Upgrade to Public Testnet

Solana has begun deploying its Alpenglow consensus upgrade to the public testnet, a milestone that opens the change to the network's broader validator community ahead of a redesign intended to cut transaction finality to a fraction of its current duration.

Anza, the development firm behind the Agave validator client, released Agave v4.3.0 on September 18 as a stable build it deems suitable for testnet, devnet and mainnet beta. After first shipping the release to operators controlling 10% and then 25% of staked SOL, Anza instructed all mainnet validators to run the version on September 21. The upgrade ranks among Solana's most consequential in years: it aims to shorten finality from roughly 12.8 seconds to about 150 milliseconds.

How the consensus model changes

Finality is the point at which a transaction can no longer be undone. It is the condition exchanges await before crediting deposits and bridges await before releasing funds. Cutting that wait from seconds to milliseconds directly shortens the hold on deposits and cross-chain transfers.

Solana currently reaches finality through TowerBFT, which stacks validator votes recorded on-chain across 32 slots before a block is considered settled. Alpenglow replaces that mechanism with Votor, a protocol in which validators transmit votes directly to one another and can agree on a block within a round or two. Eliminating the drawn-out on-chain voting chain, which accounts for most of the delay, trims the wait to about 150 milliseconds.

A staged path to the main network

The new code has run for more than four months on a separate, smaller network set up specifically for the upgrade. Moving it to Solana's public testnet, where tokens carry no real value, tests whether the full set of computers and services already running the chain can migrate in concert.

September 28 sits in Anza's calendar as the tentative date for enabling the Agave 4.3 features on the main network. Anza has not confirmed a launch, and its tracker still marked the testnet switch itself as pending early Wednesday. From here, the indicators to follow are the tracker clearing its pending status and whether Anza confirms September 28 as the enablement date.

Client readiness and what changes users

Applications will keep processing transactions as they do now, and holders do not need to change wallets or how they move funds.

The first Alpenglow migration will run entirely through Agave, because Firedancer and Frankendancer, the two alternative validator clients built by Jump Crypto, do not yet support the test. Those alternatives exist to reduce Solana's dependence on a single codebase, so that a bug in Agave does not hit every validator at once. Their absence leaves the first migration concentrated on one codebase — the very dependence the alternative clients were built to relieve.

The shift follows a run of steady network upgrades, ranging from a larger maximum transaction size to faster testnet slot times. Alpenglow reaches deeper: rather than adjusting limits or timings, it replaces the mechanism by which the network settles blocks.