Solana’s first major consensus upgrade, Alpenglow, activated on mainnet on Wednesday at about 1:54 pm UTC, according to the Solana Foundation’s Alpenglow dashboard. The upgrade is designed to meaningfully shorten transaction finality—moving Solana’s target from roughly 12.8 seconds to about 150 milliseconds—a shift aimed at making blockchain interactions feel closer to real-time applications.
Alpenglow will roll out in phases. Its first stage, Votor, replaces Solana’s existing voting and finalization mechanism with direct validator voting and a certificate-based approach. A later phase called Rotor is expected to introduce a new block data-distribution protocol intended to replace Turbine.
Key takeaways
- Alpenglow activated on Solana mainnet at ~1:54 pm UTC, per the Solana Foundation’s live dashboard.
- The upgrade targets reducing transaction finality to ~150 milliseconds from around 12.8 seconds.
- Votor is the first phase, switching to direct validator voting and certificates to achieve faster finality.
- Rotor is planned as a later phase to change block data distribution by replacing Turbine.
- At press time, Solana’s mainnet metrics on the dashboard showed 6.6-second finality and 4,721 TPS.
A near-real-time finality target goes live
Solana’s consensus model is moving away from TowerBFT as Alpenglow becomes the network’s first major consensus upgrade. In practical terms, the upgrade is meant to shrink the time users wait for transactions to be considered final—an improvement that can influence everything from payment reliability to how quickly trades can settle and how responsive decentralized applications feel under load.
The Solana Foundation’s July announcement framed the goal as a dramatic reduction in transaction finality, with the expected outcome of about 150 milliseconds. That target is ambitious compared with the previous finality level of roughly 12.8 seconds, and it reflects Solana’s broader push toward lower latency at multiple layers of the stack.
However, the early mainnet numbers shown in the dashboard suggest that the network is still ramping toward the end-state performance. At the time of publication, the Alpenglow dashboard reported 6.6 seconds for transaction finality and 4,721 transactions per second. That gap between the target and the current measurement matters: it signals that real-world behavior may depend on operational conditions, network dynamics, and how quickly the system converges under varying traffic patterns.
Votor replaces the old finalization path
Alpenglow’s first phase, Votor, is focused on altering how consensus reaches finality. Instead of relying on the earlier voting and finalization mechanism, Votor introduces direct validator voting coupled with a certificate-based system. The design is intended to cut transaction finality to the targeted ~150-millisecond range.
For developers and operators, the significance is straightforward: faster finality typically allows apps to build user flows that depend less on “wait and verify” behavior and more on near-immediate confirmation. This can be particularly relevant for applications that require tight feedback loops, such as high-frequency trading interfaces, payment flows, or interactive on-chain experiences.
For investors and traders, faster finality is not a price catalyst by itself, but it can improve market microstructure over time—especially if it supports more reliable settlement and reduces the time windows in which uncertainty can affect execution.
Next phase Rotor aims to modernize block distribution
Alpenglow is not limited to consensus finality. The later phase, Rotor, is expected to introduce a new block data-distribution protocol meant to replace Turbine. While the immediate activation brings Votor online, the broader roadmap implies that Solana intends to improve performance through both consensus mechanics and how block data propagates through the network.
That matters because block distribution and finality are tightly linked in real deployments. Even if finality logic is improved, delays or inefficiencies in data propagation can still translate into sluggish confirmation under certain network conditions. By treating Rotor as a follow-on upgrade, Solana is effectively tackling latency at multiple points rather than relying on consensus changes alone.
Why Solana’s consensus upgrade is framed as “biggest since genesis”
The scale of Alpenglow is emphasized by researchers from Anza, who described it as the “biggest change” to Solana’s core protocol since genesis. In a May blog post, Anza researchers—Quentin Kniep, Kobi Sliwinski, and Roger Wattenhofer—argued that a target latency of around 150 milliseconds could place Solana in a position to compete with Web2 infrastructure on responsiveness, potentially enabling new classes of applications.
This narrative fits with prior performance work by the Solana Foundation. In August, Solana reduced slot time for the first time since genesis as part of a plan to halve slot times to 200 ms, and the foundation said the fourth stage of that slot reduction plan was completed in October. That earlier change targeted faster confirmations through timing adjustments, while Alpenglow now aims to reduce how long transactions remain pending before being treated as final.
Looking beyond the consensus upgrade, Solana validators are expected to continue working on Agave 4.5, an upgrade proposed for a versioned transaction account limit increase—from 64 to 96 accounts. According to the Solana Foundation, expanding the supported account range could enable better swap routes and execution prices. Agave 4.5 is currently in development and is described as planned for December 2026.
What to watch from here
With Alpenglow now live, the key question is how quickly mainnet performance converges toward the upgrade’s ~150-millisecond finality target under real traffic. Readers should monitor the Solana Foundation’s Alpenglow dashboard for changes in finality and throughput over time, and watch whether the network’s behavior narrows the gap between today’s 6.6-second measurement and the intended near-instant finality experience.
