Solana Alpenglow Mainnet Activation: What Changes on October 21, 2026

Solana Alpenglow activates on mainnet on Wednesday, October 21, 2026, when epoch 1064 begins, per the Solana Foundation. It replaces Tower BFT, the consensus Solana has run since launch, with a new voting protocol called Votor. The Foundation's target is finality, the point where a transaction can no longer be undone, in roughly 150 milliseconds instead of about 12.8 seconds.

This guide covers the activation itself: when it happens, how the handover works, how to check that it is live, and what changes for holders, stakers, apps, and anyone who pays with SOL. For how Alpenglow works under the hood (Votor, the "20+20" resilience model, and the August 12 near miss), see our Alpenglow explainer.

Alpenglow is tied to an epoch, not a clock time. The Solana Foundation says epoch 1064 starts on October 21 "at approximately 13:20 UTC" and calls that an estimate because epoch timing drifts. Reports citing Anza give about 14:50 UTC, per TechTimes, or around 15:00 UTC, per CryptoSlate. Plan for early-to-mid afternoon UTC. The exact minute depends on when the slots get there.

The switch happens in two steps, per the Solana Foundation:

1. Epoch 1064 starts and the feature gate turns on. The cluster "keeps running TowerBFT for the first 5,000 slots of the epoch," which the Foundation puts at roughly 18 minutes.
2. Alpenglow takes over at slot 459,653,000. From that slot on, Votor finalizes blocks. The first block under the new consensus is covered by a "genesis certificate."

CryptoSlate adds two details the Foundation page does not state: the handover needs validators holding at least 82% of staked SOL to sign that genesis certificate, and "user transactions will briefly stop being included in blocks" while it happens. Neither source says how long that pause lasts.

The earlier September 28 date came from Anza's Agave v4.3 release schedule, which marks every date tentative and still lists mainnet feature activation as pending. Devnet went first, and mainnet follows about four weeks later.

Don't trust a date or a headline. The Foundation says to "gate feature detection on that call rather than on a date or a version string," meaning the RPC method getAgGenesisCert:

curl https://api.mainnet-beta.solana.com -s -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"getAgGenesisCert"}'

• null: the cluster is still on Tower BFT.
• A certificate object: Alpenglow is live. Its block.slot is the slot where Alpenglow consensus began.
• Method not found (-32601): the RPC node runs a client older than 4.3. That tells you about the node, not the network. Try another endpoint.

The method "reads from the finalized bank," per the Solana Foundation, so it only flips once the handover is final.

The Solana Foundation says finality "takes about 12.8 seconds" today and that "Alpenglow targets roughly 150 milliseconds." Two caveats from the same page: the number is "an expectation, not a constant," and it measures finality, "not how often blocks are produced." Nobody has measured it on mainnet yet. Give it a few weeks of real data before treating 150 ms as settled.

Today a Solana app picks between a fast "confirmed" signal and a slower "finalized" one. Under Alpenglow, "confirmed and finalized become the same thing," per the Foundation, and confirmed "will be deprecated and removed in a later release." Nothing breaks on activation day, since all three commitment levels keep working. The Foundation warns builders not to switch early, though: on Tower BFT, "finalized still means waiting 12.8 seconds."

Under Tower BFT, validators vote by sending transactions, and those votes make up a large share of everything Solana processes. Under Alpenglow, "votes are no longer transactions, so they no longer appear in blocks," per the Solana Foundation, so "transaction counts and TPS drop sharply." The Foundation calls it "an accounting change, not a throughput regression," and warns that outdated dashboards "will report the change as a collapse in network activity."

If you see a "Solana activity collapses" chart on Thursday, this is why. For what the throughput numbers mean, see our Solana transactions per second breakdown.

"Wallets and applications keep working exactly as they do today," per the Foundation, and "sending transactions and running onchain programs are not affected." Alpenglow is a consensus change. Transaction fees come from Solana's separate fee market, and you sign the same transactions as before.

• Rotor. The new block-propagation layer "is planned for a later release once Votor is adopted, and is not yet scheduled," per the Solana Foundation. October 21 is Votor only.
• Slot time. Blocks still come every few hundred milliseconds, after the SIMD-0525 cuts in August, per Solana's upgrade tracker. Alpenglow shortens the wait for finality, not the block interval.
• Your SOL. Balances, token accounts, and stake accounts are untouched. There is no token swap, migration, or claim.

Nothing to do. You don't need to update your wallet, move funds, or sign anything. Expect scammers to use the news: SolanaFloor tells holders to "ignore any messages from impersonators encouraging you to sign any transactions." No legitimate Alpenglow step needs your signature.

Your stake account needs nothing either, but your validator does. A validator that doesn't pay the per-epoch admission fee "does not vote or produce blocks in the next epoch," per the Solana Foundation, and a validator that isn't voting isn't earning rewards for its delegators. If you delegate to a smaller operator, check that it has announced its Agave 4.3 upgrade. Firedancer and Frankendancer operators in particular have to switch clients before activation.

• Client: v4.3.2 of Agave, Jito-Solana, or Harmonic Salsa. "Firedancer and Frankendancer are not supported during the migration."
• BLS key: validators without a BLS public key registered on-chain are excluded from the admitted validator set.
• Admission fee: a flat 0.8 SOL per epoch, taken from the vote account and burned, on top of the rent-exempt minimum. The first charge comes at the start of epoch 1064 and pays for epoch 1065.

• Commitment: keep current settings until activation, then move new code to finalized and migrate off confirmed.
• Timeouts: the Foundation recommends re-checking timeouts and retry logic tuned to 12.8-second finality.
• Indexers: Geyser and gRPC events now carry a bank_id. The Foundation says to "buffer per (slot, bank_id), never per slot." JSON-RPC and WebSocket are unchanged.
• Analytics: update anything that counts or filters vote transactions. "Vote filtering becomes a no-op."

For merchants, the big change is that "confirmed" and "final" in a Solana Pay checkout collapse into one fast signal.

Solana carries most of our deposits. Over the 90 days to mid-September 2026, about 66% of SolCard deposits came in over Solana: 43.8% in SOL, 12.9% in USDC, and 9.0% in USDT. Our August 2026 crypto payments report shows the same pattern.

Alpenglow touches one part of that flow: the on-chain leg, when you send SOL or a Solana stablecoin to top up a card. A deposit only becomes irreversible at finality, so faster finality removes a wait from the network side. Paying at checkout is separate. Once your balance is loaded on a SolCard, card payments run on Visa and Mastercard rails and don't wait for a Solana transaction, so the handover itself doesn't touch a purchase at checkout. Alpenglow doesn't change your top-up fees, your card fees, or your limits.

On Wednesday itself, the practical advice is to top up before or after the handover rather than during it. If user transactions briefly pause while the genesis certificate is signed, a deposit sent in that window may simply land later. For more on using Solana to pay day to day, see our Solana payments guide.

In epoch 1064, which the Solana Foundation expects to start on Wednesday, October 21, 2026, at roughly 13:20 UTC. Reports citing Anza say about 14:50-15:00 UTC. Tower BFT runs for the first 5,000 slots of the epoch, about 18 minutes, and Alpenglow takes over at slot 459,653,000.

Check, don't guess. Call the RPC method getAgGenesisCert on a node running client version 4.3 or later. It returns null while Solana is still on Tower BFT and a certificate once Alpenglow has taken over.

No. Per the Solana Foundation, wallets and applications keep working as they do today and nothing breaks on activation day. Ignore anyone asking you to sign a transaction "for the upgrade."

No. Alpenglow changes consensus, meaning how validators agree that a block is final. Fees come from Solana's separate fee market, and the Foundation says the fee model is unchanged.

Votes stop being transactions. Under Tower BFT, validator votes are recorded on-chain and counted in TPS. Under Alpenglow they move off the ledger, so reported transaction counts fall sharply. The Solana Foundation calls this "an accounting change, not a throughput regression."

No. The Solana Foundation calls 150 ms "an expectation, not a constant." It is the design target, and mainnet numbers will only exist after activation.

No. October 21 activates Votor only. The Solana Foundation says Rotor is planned for a later release and is not yet scheduled.

On Wednesday, Solana hands consensus from Tower BFT to Alpenglow's Votor. The feature turns on at the start of epoch 1064, Tower BFT runs for about 18 more minutes, and Alpenglow takes over at slot 459,653,000. The headline is finality dropping from about 12.8 seconds toward 150 ms. Two things are worth remembering: the 150 ms number is a target until mainnet proves it, and the falling TPS chart is bookkeeping, not a slowdown.

For holders, there is nothing to do except ignore anyone asking you to sign something. If you fund a card with SOL, the payoff is a shorter wait on the network side of a top-up. The card itself works the same at checkout, before and after.

• Solana Foundation -- Alpenglow upgrade page
• Anza -- Alpenglow: A New Consensus for Solana
• Solana Status -- SIMD-0326 governance result
• Anza -- Agave v4.3 Release Schedule
• Solana Foundation -- Reduced Slot Times (SIMD-0525)
• CryptoSlate -- Solana sets October 21 for Alpenglow upgrade
• SolanaFloor -- Alpenglow mainnet activation set for October 21
• TechTimes -- Solana Alpenglow Goes Live Oct 21