Solana begins testnet testing of Alpenglow upgrade, targeting 150-millisecond finality

The upgrade could slash transaction finality from 12.8 seconds, but testing currently relies solely on Agave validator software as alternative clients remain unsupported

By LineZotpaper
Published
Read Time2 min
Solana has started testing the Alpenglow upgrade on its testnet, a step that could eventually reduce transaction finality from 12.8 seconds to 150 milliseconds. The test comes after more than four months of testing on a smaller dedicated network and moves the upgrade to Solana's broader test environment.

The Solana blockchain has begun testing a significant upgrade, Alpenglow, on its testnet. Alpenglow aims to dramatically reduce transaction finality—the time it takes for a transaction to be considered irreversible—from the current 12.8 seconds to just 150 milliseconds.

According to a report from CoinDesk, Alpenglow has spent more than four months running on a smaller network created specifically for the upgrade. Moving it to Solana's established testnet checks whether the broader group of computers and services already running the blockchain can switch together.

Validators taking part in the test must use Agave 4.3, the main software used to run Solana, maintained by Anza, one of the companies responsible for developing the network. Anza recommended Agave 4.3 to all mainnet validators on September 21, after initially rolling it out to operators responsible for 10% and then 25% of the SOL used to secure the network.

September 28 appears in Anza's schedule as the tentative date for turning on features included in Agave 4.3 on the main network. However, it is not a confirmed Alpenglow launch date, and Anza's tracker still listed the testnet switch itself as pending early Wednesday.

Notably, Firedancer and Frankendancer—two alternative validator programs built by Jump Crypto—do not yet support the Alpenglow test. Those alternatives are intended to reduce Solana's reliance on a single piece of software, so a fault in Agave does not affect every validator at once. Their absence from the test means the first Alpenglow migration will run entirely through Agave.

According to Anza, applications will keep executing transactions as they do today, and users will not need to change wallets or how they send funds.

§

Analysis

Why This Matters

  • A drop from 12.8 seconds to 150 milliseconds would make Solana transactions feel near-instant, significantly improving user experience for DeFi, gaming, and payments.
  • The upgrade signals Solana’s continued push for higher performance, but reliance on a single validator client (Agave) during initial testing introduces a concentration risk.
  • If successful, Alpenglow could set a new benchmark for blockchain finality, pressuring competing networks to accelerate their own performance upgrades.

Background

Solana is a high-performance blockchain designed for decentralized applications and cryptocurrencies. Transaction finality—the time before a confirmed transaction cannot be rolled back—has been a focal point for scalability improvements. The Alpenglow upgrade targets one of the remaining bottlenecks in Solana’s architecture, aiming to bring finality closer to that of traditional financial settlement systems.

Key Perspectives

Solana developers (Anza): Pushing forward with Agave 4.3 as the primary client for the upgrade, confident that the testnet migration will validate the changes needed for mainnet deployment. Jump Crypto: Responsible for the Firedancer and Frankendancer validator clients, which are not yet ready for Alpenglow. This means the first deployment will be single-client, undermining the intended diversification of validators. Validators and node operators: Must upgrade to Agave 4.3 to participate in the test; they face a coordination challenge to ensure seamless migration.

What to Watch

  • The September 28 deadline for activating Agave 4.3 features on mainnet—whether it proceeds on schedule or is delayed.
  • When Jump Crypto’s Firedancer and Frankendancer add Alpenglow support, which will determine how quickly the network can move to a multi-client setup.
  • Any unexpected issues during testnet migration that could push back the timeline for Alpenglow’s mainnet launch.

Sources

Zotpaper

Written by software from the reporting listed above, scored by an automated standards desk, and published without a person reading it first. If something here is wrong, tell the editor and it will be put right.