Solana Alpenglow Activation: What Stakers Should Check Before September 28

TL;DR. Anza's Agave v4.3 Release Schedule now puts Mainnet-beta general adoption on September 21 and begin v4.3 feature activation on September 28 (tentative). The Solana Foundation Alpenglow page (updated September 2026) ties mainnet activation to that schedule and ~150ms Votor finality. This is an update to our earlier Alpenglow explainers, not a republish. Exchange / unstaked: usually nothing. Self-custody delegated: check your validator's Agave 4.3 client after Sept 21. BLS / VAT are already live. Alpenglow ≠ APY cut; disinflation still waits on the SIMD-0607 yield gate.

Solana's consensus upgrade finally has a dated mainnet runway.

Our plain-English Alpenglow explainer and July countdown still hold on the mechanics. What changed is the calendar language: Anza published a tentative v4.3 schedule, and the Foundation's September update points stakers and operators at that same line. Here is what to check before the late-September window, without inventing tallies or live yields.

---

The dates that matter (and what they actually mean)

Anza labels the whole wiki page as a tentative schedule for informational purposes. Dates can move. Wait for Discord and client announcements before treating any day as locked.

Begin feature activation is the precise phrase on the schedule. September 28 is the target to start turning on v4.3 features on mainnet-beta, not a promise that every stake account wakes up to a finished migration at midnight. Feature gates and epoch boundaries do the rest.

Primary sources:

• Anza Agave wiki: v4.3 Release Schedule
• Solana.com upgrades: Alpenglow (Foundation page, updated September 2026)

---

What Alpenglow changes (quick refresh)

Alpenglow replaces how validators agree on the next block and when that block is final. It does not rewrite the SVM, transaction formats, or fee mechanics.

Phase 1: Votor (ships in Agave 4.3)

• Validators vote directly to each other instead of stuffing vote transactions into blocks
• Votes aggregate into certificates
• Target finality: roughly 150ms, versus ~12.8 seconds under TowerBFT

Phase 2: Rotor

• Later replacement for Turbine-style propagation
• Not yet scheduled for this September window

If you only send transactions and read account state, the Foundation's user checklist is blunt: no action needed for signing and approving. The staker-relevant work sits with validator operators and with anyone who streams or indexes blocks.

For the longer design story, see Alpenglow in plain English. For the July prep status (BLS registration opening), see the mainnet countdown.

---

Staker checklist

1. Exchange custody or unstaked SOL

Usually nothing. You are not choosing a vote-account client version. Watch wallet and app UX for confirmation-speed changes after the cluster migrates; you do not need a special September 28 ritual.

2. Self-custody, native delegation

This is the row that matters.

1. After September 21, confirm your validator has moved to the Agave 4.3 line recommended for general adoption (or an equivalent ready client path your operator documents).
2. Confirm the operator already completed earlier prerequisites: BLS pubkey on the vote account and VAT readiness. Those gates activated in July 2026 per the Foundation page. Do not invent participation tallies; just verify your operator is in the admitted set.
3. Prefer operators who publish upgrade notes. A validator that lags on client versions cannot keep earning for you if it drops out of consensus.

3. Liquid staking (including raSOL)

You hold a token that represents pooled stake. You do not manually re-delegate for Alpenglow day. You still want the underlying operators shipping upgrades. Soft path: stake natively or via raSOL with an operator that treats client readiness as part of the product, not a surprise.

Hubra has run a Solana validator since 2020 and documents native staking and liquid staking / raSOL paths without live APY claims in this article.

---

Already live vs still ahead

BLS and VAT are not the same event as Alpenglow consensus turning on. They were admission plumbing. Votor is the consensus switch that rides the Agave 4.3 feature-activation window.

---

Alpenglow is not your yield cut

Keep the two stories apart.

If a headline implies staking yields already stepped down because consensus is changing, that is a category error. Read our SIMD-0607 yield-gate piece for the disinflation activation chain. Alpenglow is about finality and validator voting, not an inflation schedule change.

---

How to track the flip without guessing

1. Follow Anza's schedule updates and Discord upgrade calls.
2. After operators are on 4.3, use cluster queries (getAgGenesisCert or solana alpenglow-genesis-info) rather than assuming September 28 finished the job.
3. Expect the practical effect to land across later epoch boundaries, potentially into October, even if begin-activation targets the 28th.

Infrastructure teams (indexers, Geyser consumers) have a longer migration list on the Foundation page. Ordinary stakers do not need that checklist. Validator readiness is the stake-weighted hinge.

---

Soft next step

If you self-custody:

• Keep SOL staked natively or as raSOL with an operator that ships upgrades on the Agave schedule.
• Re-check your validator's client version after September 21.
• Treat September 28 as begin activation, then watch epoch boundaries and cluster state.

Proof over calendar theater. The wiki is tentative. The Foundation page is the product-facing map. Your job is simple: pick operators who keep the vote account ready while Votor turns on.

---

Sources: Anza Agave v4.3 Release Schedule; Solana Alpenglow upgrade page. Prior Hubra context: Alpenglow consensus, mainnet countdown, SIMD-0607 yield gate.