Anza Introduces New Alpenglow Consensus Protocol, Aiming to Make Solana Network Faster and More Deterministic

Alpenglow, a new consensus protocol, has been introduced by Anza, a Solana-focused research and development firm. It aims to make the network faster, more deterministic, and safer.

Anza, a Solana-focused research and development firm, has unveiled a new consensus protocol named Alpenglow. This protocol aims to make the Solana network faster, more deterministic, and safer. Described as the biggest consensus redesign since Solana’s launch, Alpenglow is set to replace the existing TowerBFT (Byzantine Fault Tolerance) mechanism and Proof of History with a more easily understandable and efficient system.

Targeting Performance Gains Without Compromising Network Safety

In his X post, Yakovenko further stated that he got nearly everything wrong about consensus, except the important parts. Drawing attention to the design of Alpenglow, he highlighted two critical requirements:

* Consensus should not interfere with block producers using 100% of the available bandwidth at all times.

* Users must experience deterministic finality in a single round.

According to Anza’s blog, Alpenglow drastically reduces transaction finality latency to a median of 100-150 ms. In contrast, TowerBFT takes roughly 12.8 seconds from block creation until finality. This marks a 100x improvement, rendering it competitive with centralized infrastructure.

Alpenglow achieves this by splitting the faults into two categories: full Byzantine and down or unavailable. Based on this fault model, the protocol can guarantee safe finality within one or two rounds. If a fork accumulates 40% of the total stake in votes (20% Byzantine and 20% down), then the node can safely commit to it. The fork will be finalized either in one round with 80% of votes or in two rounds with 60%.

Rotor and Votor: Building for the Future

This approach allows for deterministic finality without slowing down block production. Instead of handling epochs full of unconfirmed blocks, Alpenglow reduces the active state to just two blocks. This simplifies the system for developers and validators, especially when different parts of the network aren't perfectly synchronized.

Yakovenko also noted that the protocol has simplified and formalized Turbine, now renamed Rotor. Together with Votor, Alpenglow's voting component, these components lay the foundation for enhancing scalability features, such as support for multiple concurrent leaders and increased validator efficiency.

Although still a proposal, if approved, Alpenglow could be a major step in Solana's ongoing evolution.