Solana has begun moving its Alpenglow consensus upgrade onto the public testnet, a milestone that lets the network’s wider validator community exercise a change designed to shrink transaction finality to a fraction of its current time. Anza, the firm behind the Agave validator client, published Agave v4.3.0 on September 18 as a stable build it calls suitable for testnet, devnet and mainnet beta. On September 21 it told all mainnet validators to run the version, after first delivering it to operators in charge of 10% and then 25% of staked SOL. The move is one of Solana’s most consequential in years: it targets a cut in finality from roughly 12.8 seconds to about 150 milliseconds.
How the consensus model changes
Finality is the point at which a transaction cannot be undone, and it is what exchanges wait for before crediting deposits and bridges wait for before releasing funds. Solana reaches it today through TowerBFT, which stacks validator votes recorded on-chain across 32 slots before a block is considered settled. Alpenglow swaps that for Votor, a protocol in which validators pass votes straight to one another and can agree on a block within a round or two. That removes the drawn-out on-chain voting chain that makes up most of the delay, trimming 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 for the upgrade. Shifting it to Solana’s public testnet, where tokens carry no real value, tests whether the full set of computers and services that already run the chain can move over in concert. September 28 sits in Anza’s calendar as the tentative date for enabling the Agave 4.3 features on the main network, though Anza has not confirmed a launch and its tracker still marked the testnet switch itself as pending early Wednesday.
Client readiness and what changes for users
Applications 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. The shift follows a run of steady network upgrades, from a larger maximum transaction size to faster testnet slot times.