Alpenglow consensus

≈12.8 sec 150 msec

A faster path from transaction to certainty. Follow live Solana activity through streaming, confirmation, and finality.

Explore Alpenglow
Drag to rotate · Ctrl + scroll to zoom

RPCConnecting— total TPS— non-vote TPSslot —— tx in latest block

Each small cube is one transaction, grouped by its ledger block. The timing control models how many transactions remain in flight at about 12.8 seconds versus 150 milliseconds; incoming mainnet data stays live.

What Alpenglow changes

Consensus, rewritten.
Execution, untouched.

Consensus is how validators agree on which block comes next and when it can no longer be undone. Alpenglow replaces TowerBFT with a faster path to that agreement while leaving the way transactions execute exactly as it is.

Unchanged
SVM & programs
Unchanged
Transactions & fees
For users
No action needed

Phase one · Votor

Votes become certificates.

Validators send votes directly to one another instead of placing vote transactions inside blocks. Those votes combine into a quorum certificate that finalizes a block in one or two rounds.

Alpenglow tolerates 20% malicious stake plus 20% offline stake while still reaching consensus.

Fast path

One round
80%

of stake votes to notarize

Block finalizes immediately.

Fallback path

Two rounds
60%

stake threshold for certificates

A second round finalizes or skips.

The rollout

Two protocols. One transition.

  1. Agave 4.3 · Q3 2026

    Votor

    Replaces TowerBFT voting with direct validator votes and aggregate certificates. This is the phase that targets roughly 150ms finality.

    In development
  2. Later release · Unscheduled

    Rotor

    Follows Votor to replace Turbine's tree-based block propagation with a single relay layer designed to reduce network latency.

    Follows Votor

What it means for you

The transition by role.

Users

No migration.

Signing, sending, and approving transactions stay the same. Finality simply arrives much sooner.

Developers

Execution stays put.

Apps that only send transactions and read account state need no changes. Block stream consumers should prepare for multiple banks per slot and the new bank_id field.

Validators

Prepare for Votor.

Operators need a registered BLS public key and Agave 4.3 to join Alpenglow consensus.

Go deeper

Migration details, breaking changes, and the full protocol story.

Read the Alpenglow upgrade guide
© 2026 Solana Foundation. Alle Rechte vorbehalten.