SOLANA·HUB
DE

Network upgrade, checked status

Alpenglow: Votor is active on Testnet and Devnet

Mainnet Beta is still running TowerBFT. No official date has been announced for activating Alpenglow Votor on Mainnet.

Last verified:

Status as JSON

The status in one sentence

Alpenglow Votor is active on Testnet and Devnet; the official feature-gate tracker still lists Mainnet Beta as “Pending Mainnet Beta Activation.”

Status by network

Slots are sourced from the official feature-gate tracker and on-chain read-backs through the public Solana RPCs. “Genesis certificate” is the technical transition record; it does not automatically mean the first Alpenglow block.

Testnet

Votor active
Current consensus
Alpenglow Votor
Activation epoch
1,042
Feature activation slot
444,620,256
Genesis-certificate slot
444,625,255

RPC read-back: api.testnet.solana.com · getAgGenesisCert

Devnet

Votor active
Current consensus
Alpenglow Votor
Activation epoch
1,167
Feature activation slot
504,144,000
Genesis-certificate slot
504,148,999

RPC read-back: api.devnet.solana.com · getAgGenesisCert

Mainnet Beta

Pending
Current consensus
TowerBFT
Activation epoch
Not announced
Feature activation slot
—
Genesis-certificate slot
—

RPC read-back: api.mainnet-beta.solana.com · getAgGenesisCert

SIMD-0326

Votor is not the entire Alpenglow rollout

The current activation covers Votor, the new consensus protocol defined in SIMD-0326. Rotor, the planned data-dissemination protocol, is not part of this activation and will be scheduled separately. This page therefore says “Alpenglow Votor” rather than calling the entire Alpenglow system live.

Primary sources

Status claims are derived only from official Solana, Anza, SIMD and on-chain sources.

  1. 01
    Alpenglow upgrade overview

    Solana Foundation

    Supports: upgrade overview · rollout context

  2. 02
    Alpenglow consensus documentation

    Anza

    Supports: protocol terminology · Votor documentation

  3. 03
    Agave feature-gate tracker

    Anza

    Supports: Testnet epoch 1042 · Devnet epoch 1167 · Mainnet Beta pending

  4. 04
    getAgGenesisCert RPC method

    Solana Documentation

    Supports: non-null certificate means the cluster has migrated · null means the cluster is still using TowerBFT

  5. 05
    Agave 4.3 release schedule

    Anza

    Supports: September 28 schedule clarification

  6. 06
    SIMD-0326: Alpenglow consensus protocol

    Solana Improvement Documents

    Supports: Votor scope · Rotor excluded from this proposal

  7. 07
    SIMD-0384: Alpenglow migration

    Solana Improvement Documents

    Supports: migration sequence · genesis-certificate semantics

Change record

This page is updated at the same URL when official status changes. A Mainnet date will only be added after Solana or Anza explicitly publishes it and the activation can be verified on-chain.

Established the first verified baseline: confirmed Testnet and Devnet, marked Mainnet as pending, and corrected the September 28 misinterpretation.

Frequently asked questions

Is Alpenglow live yet?

Alpenglow Votor is active on Solana Testnet and Devnet. Its Mainnet Beta activation is still pending, and Mainnet continues to use TowerBFT.

When will Alpenglow activate on Mainnet?

Solana and Anza have not announced a Mainnet activation date for SIMD-0326. Any date currently presented as confirmed would be speculative.

Is September 28 the Alpenglow Mainnet date?

No. The Agave 4.3 schedule lists September 28 only as a tentative resumption of general feature activations. It does not assign that date to Alpenglow.

What is the difference between Votor and Rotor?

Votor is Alpenglow’s consensus protocol and the subject of SIMD-0326. Rotor is the planned data-dissemination protocol and will be introduced separately later.