Alpenglow primary sources
Reviewed: 2026-05-14 UTC
Canonical white paper
- https://www.anza.xyz/alpenglow-1-1
- Canonical primary artifact for the protocol in this pass.
- Used as the official reference point for the project page, though the page itself was not easily extractable as plain text via lightweight fetch tooling.
- Cross-confirmed through the launch blog and SIMD-0326, both of which explicitly point to the v1.1 paper as the main companion document.
Official launch post
- https://www.anza.xyz/blog/alpenglow-a-new-consensus-for-solana
- Best directly readable official source in this pass for the protocol’s architecture and performance framing.
- Used to confirm the split between Votor and Rotor, the one-round 80% versus two-round 60% finalization paths, the median ~150 ms finality claim, and the
20+20resilience framing. - Also useful because it clearly positions Alpenglow as a major replacement for TowerBFT and PoH-era finality logic rather than as a minor optimization.
Solana Improvement Document
- https://github.com/solana-foundation/solana-improvement-documents/blob/main/proposals/0326-alpenglow.md
- https://raw.githubusercontent.com/solana-foundation/solana-improvement-documents/main/proposals/0326-alpenglow.md
- Best source in this pass for rollout scope and operator-visible design surfaces.
- Used to confirm that the reviewed adoption proposal focuses on the Votor portions first while explicitly deferring Rotor and some other Alpenglow subcomponents.
- Also used to capture concrete mechanism details that matter for corpus comparisons: vote types, certificate thresholds, fast-versus-slow finalization rules, off-chain vote aggregation, reward handling, and Validator Admission Ticket policy.
Main takeaways from this pass
- Alpenglow is best treated as a separable fast-consensus stack, not just as a generic
Solana upgradelabel. - The most reusable mechanism is the concurrent one-round 80% fast path plus two-round 60% slow path, alongside off-chain direct voting and aggregate-certificate finalization.
- The most important caveat is staging: current official proposal material narrows initial adoption to the Votor parts of Alpenglow, so comparisons should keep Votor, Rotor, and later subcomponents analytically separate.