Solana activates Alpenglow on testnet, targeting 150ms finality

Solana has activated the Alpenglow consensus upgrade on testnet, beginning a broader migration test for a system designed to cut finality from about 12.8 seconds to roughly 150 milliseconds. CoinDesk reported the testnet move; the Solana Foundation’s upgrade tracker now lists the testnet feature gate as active, while mainnet remains inactive.

The target is about 85 times faster than Solana’s current finality, when a transaction can no longer be reversed. That could shorten the wait for exchanges crediting deposits, bridges releasing funds and merchants accepting payments. It is a protocol target under testing, not a demonstrated mainnet result.

How does Alpenglow change Solana’s finality process?

Alpenglow replaces TowerBFT, which records validator votes as transactions and finalizes a block after enough votes accumulate across 32 slots. Its first phase, Votor, sends votes directly between validators and bundles them into certificates; a block can become final after one or two voting rounds, according to the Foundation.

The upgrade changes consensus, the process validators use to agree on blocks. It leaves transaction execution, programs and fees unchanged, so ordinary users are not expected to change how they send funds. The 150-millisecond target measures time to finality, not how often Solana produces blocks; slot timing is being reduced separately.

What has to work before the change reaches mainnet?

The public testnet checks whether Solana’s wider set of validators and services can migrate together. CoinDesk reported that participating validators need Agave 4.3, the main Solana validator software maintained by Anza. It also reported that Jump Crypto’s Firedancer and Frankendancer clients do not yet support this test, leaving the initial migration dependent on Agave.

That limits how much the test can show about client diversity. Those alternative clients are intended to reduce reliance on one validator software implementation; their absence means the test does not yet demonstrate that multiple implementations can make the transition together.

There is also work for infrastructure that reads Solana’s block data. The Foundation says vote transactions will leave blocks under Alpenglow, and streaming consumers will need to handle a new bank identifier in Agave 4.3. Transaction execution stays the same, but tools that count transactions or assume one block per slot may need changes.

When could Alpenglow reach Solana mainnet?

The Foundation lists Q3 2026 as the expected mainnet activation window, but its tracker still marks mainnet inactive. CoinDesk reported Sept. 28 as a tentative date for enabling Agave 4.3 features, not a confirmed Alpenglow launch date.

The next signals are the mainnet feature-gate status, whether the testnet migration runs reliably across validators, and when Firedancer or Frankendancer add support. The Foundation says Rotor, a separate block-propagation phase, is planned for later and has no schedule yet.