preferred on
Points of Focus
- Solana’s Alpenglow consensus upgrade activated on testnet on Sept. 22.
- It targets ~150ms finality, down from roughly 12.8 seconds under TowerBFT.
- Mainnet activation is tentatively targeted for Sept. 28 on Anza’s schedule.
Solana’s Alpenglow consensus upgrade went live on the network’s testnet on Sept. 22, Anza confirmed, marking the first point at which validators and developers can observe its core behavioral change on a live cluster rather than through documentation alone.
The activation also retires Frankendancer, an interim validator client combining Firedancer’s networking layer with Agave’s runtime, from testnet.
Alpenglow is coming.
See the detailed upgrade guide and migration checklist here: https://t.co/DA1hih7dhU
— Solana Developers (@solana_devs) September 21, 2026
Under the current TowerBFT system, a transaction can reach a “confirmed” status in roughly one slot. Still, that status carries a weaker guarantee than “finalized,” which takes about 12.8 seconds to achieve.
Alpenglow is coming to testnet this week. 🧵
Testnet exercises the exact migration devnet and mainnet-beta will run.
The Alpenglow community cluster rehearsed the migration numerous times and has been running Alpenglow for over 4 months.
Now Alpenglow moves to the formal…
— Anza (@anza_xyz) September 22, 2026
Alpenglow’s Votor consensus collapses that gap entirely. Today’s testnet activation is the first time that behavior, confirmed and finalized as the same state, is observable on a live cluster rather than described in a specification.
What Alpenglow actually changes
Alpenglow is Solana’s first full consensus replacement since its 2020 mainnet launch, replacing both proof-of-history and TowerBFT with two new components. Votor, the voting and finality layer activating now, targets finality around 150ms, according to Solana’s upgrade page, down from roughly 12.8 seconds today, a reduction the page itself describes as 99% faster. Rotor, a second phase that will replace Turbine’s block propagation mechanism, is planned for a later release once Votor is established and remains unscheduled.
The new system also raises the network’s fault tolerance. Votor is designed to reach consensus while tolerating 20% adversarial stake plus 20% offline stake simultaneously, a meaningfully wider margin than TowerBFT’s roughly one-third combined threshold.
That margin is not a theoretical improvement dreamed up in isolation: An August routing outage at infrastructure provider Teraswitch reportedly pushed close to 29% of staked Solana (SOL) offline, within a few percentage points of the threshold that would halt finality under the current system. Alpenglow passed with 98.27% of the validator stake in a September 2025 governance vote, an unusually decisive mandate for a change this fundamental to how the network operates.
Solana’s Alpenglow testnet step is separate from mainnet timing
Alpenglow’s mainnet activation is a distinct, later milestone from today’s testnet news, and the two should not be read as the same event. Solana’s upgrade page lists mainnet activation only as expected in “Q3 2026,” without a specific date.
Anza, the company that develops Solana’s validator client, maintains a separate engineering document. This Agave v4.3 release schedule currently targets Sept. 28 for the start of mainnet-beta feature activation for Agave 4.3, the release that carries Alpenglow toward mainnet. That date is explicitly labeled tentative on Anza’s schedule and has shifted before on prior Agave releases.
Anza reinforced that target on Sept. 21, issuing a public call recommending all mainnet-beta validators adopt Agave 4.3, with CEO Brennan Watt confirming “v4.3.0 is a go for mainnet.”
Separately, Anza published a release schedule for Agave 4.4 on the same day as today’s testnet activation, targeting a Nov. 9 mainnet feature gate for an unrelated set of changes on a separate track from Alpenglow’s rollout, a distinction worth keeping clear given how easily the two version numbers get conflated in casual coverage.
What Solana’s Alpenglow upgrade changes for users
For ordinary Solana users and most application developers, Alpenglow requires no action. Sending transactions, signing, and interacting with wallets remain unchanged since the upgrade leaves execution and the Solana Virtual Machine untouched.
The changes fall on infrastructure that reads consensus and block data: Validators must register a BLS public key to remain in the admitted validator set, a requirement already enforced on mainnet since July 22, and indexers, exchanges, and block explorers that stream block data face genuine migration work, including adapting to blocks that can temporarily contain more than one candidate version during consensus.
The testnet is where that migration work is tested under real conditions before it reaches the mainnet. Whether the current testing surfaces issues that affect the Sept. 28 mainnet target remains an open question that today’s activation, not Anza’s published schedule alone, will help answer.
Share
Most read articles
