Solana has activated its first major consensus upgrade, Alpenglow, on mainnet on Wednesday at approximately 1:54 pm UTC, according to the Solana Foundation’s Alpenglow activation dashboard at https://solana.com/upgrades/alpenglow/dashboard.

The upgrade is designed to dramatically tighten transaction finality—Solana says the network aims to reduce finality from roughly 12.8 seconds to about 150 milliseconds. As the new mechanism beds in, the foundation’s dashboard showed, at press time, about 6.6 seconds of transaction finality and a throughput of roughly 4,721 transactions per second.

Key takeaways

Alpenglow is live on Solana mainnet as of 1:54 pm UTC, marking the network’s first large consensus overhaul since genesis.
Solana targets ~150 ms finality, though early mainnet readings still show finality closer to seconds.
The first phase, Votor, replaces the existing voting/finalization approach with direct validator voting and certificate-based finality.
A later phase, Rotor, is expected to introduce a new block data distribution protocol intended to replace Turbine.
Beyond Alpenglow, Solana validators are expected to continue work on Agave 4.5, which would raise versioned-transaction account limits from 64 to 96.

What Solana’s Alpenglow changes on-chain

Alpenglow is Solana’s first major consensus upgrade, moving the network away from its existing consensus model, TowerBFT. The core objective is to reduce transaction finality by a reported 99%, cutting the expected time to reach finality to roughly 150 milliseconds.

Solana has said the upgrade consists of multiple phases. In the initial phase, Votor, the network changes how votes translate into finality. Instead of the prior voting and finalization mechanism, Votor uses direct validator voting paired with a certificate-based system—a design intended to achieve the targeted fast finality.

After Votor, Solana plans to follow with Rotor, which will focus on block data distribution. Rotor is described as a new block data-distribution protocol intended to replace Turbine, highlighting that Alpenglow’s performance goals extend beyond consensus logic into how blocks and related data propagate across the network.

For users and developers, the practical promise of this architecture is near-immediate confirmation behavior—something Solana expects could improve payments, trade settlement, and the responsiveness of interactive applications that depend on fast transaction certainty.

Early mainnet results: finality improves, but not instantly

While Solana’s published target is around 150 ms, real-world performance can take time to reflect the full effect of an upgrade, especially as validator participation, network conditions, and client behavior settle. At the time of reporting, Solana’s mainnet dashboard associated with Alpenglow indicated 6.6 seconds of transaction finality and approximately 4,721 TPS.

The gap between the mainnet readouts and the aspirational finality number matters because it sets expectations for how quickly applications can rely on the new speed. Faster finality is most useful when it is consistent and observable under load; early metrics provide a first signal, but traders and integrators are likely to watch for continued convergence toward Solana’s targets over subsequent epochs.

Cointelegraph sought additional perspective from the Solana Foundation on how finality measurements behave in testnet environments and what performance is expected in real-world application conditions. (As of press time, no further performance figures beyond the public dashboard were provided in the source material.)

Why Solana’s team frames Alpenglow as a “biggest change”

Solana researchers affiliated with Anza characterized Alpenglow as the “biggest change” to Solana’s core protocol since genesis. In a May blog post referenced in the report, researchers wrote that a target around 150 ms latency could help Solana compete with Web2 infrastructure on responsiveness, potentially enabling blockchain-based “entirely new categories of applications.”

This message ties Alpenglow to a broader performance roadmap Solana has been pursuing. Earlier coverage in the source points to Solana reducing slot time for the first time since genesis as part of a plan to halve slot times toward 200 ms; the foundation’s plan is described as having progressed through later stages and completed the fourth stage in October.

Seen together, the slot-time effort and Alpenglow’s finality work suggest Solana is tackling responsiveness from two directions: how quickly blocks are produced and how quickly transactions become final. While slot time reduction targets confirmation speed, the finality reduction changes how soon clients can treat transactions as irreversible—an important distinction for application design, liquidity operations, and settlement workflows.

What comes next: Agave 4.5 and continued validator work

Alpenglow does not appear to be the end of Solana’s infrastructure upgrades. Following the consensus change, the source notes that validators are expected to keep working on Agave 4.5. Solana’s planned upgrade would increase the number of accounts supported by a versioned transaction from 64 to 96.

The Solana Foundation’s reasoning, as described in the source, is that higher account limits could enable better swap routes and potentially improve execution prices. If accurate, this kind of change can be meaningful for decentralized exchange routing logic, where complex multi-hop transactions often stress account limits.

Agave 4.5 is described as currently in development and planned for December 2026. For builders and operators, that timeline implies that even after consensus finality improves, performance and user experience gains may continue to depend on follow-on upgrades to transaction capabilities and execution behavior.

Investors and active ecosystem participants should watch how quickly Alpenglow’s measured finality stabilizes on mainnet under typical traffic—especially whether network conditions move steadily toward the cited ~150 ms goal—and whether application-level integration teams can rely on the new finality characteristics for settlement and payment flows.