Alpenglow Is Pending Activation on Solana Mainnet, With TowerBFT Set to Retire at Slot 459,653,000

Anza says Alpenglow is now pending activation on Solana SOL$105.94+1.7% mainnet-beta. In a post at 12:25 UTC on 20 October 2026, Anza named the migration boundary as slot 459,653,000 and said the new consensus "goes live tomorrow, Wednesday, Oct 21 at ~14:00 UTC." Its summary of the handoff: "One slot, and TowerBFT retires."

That turns the Alpenglow mainnet activation from a date on a calendar, which Anza first set for about 14:50 UTC on 13 October, into a fixed block height. The clock time is a projection. It depends on how fast slots arrive between now and then, which is why Anza wrote "~".

Why the Alpenglow switch time reads 13:20 UTC in some places and 14:00 UTC in others

Two different moments are being timed. The Solana Foundation's upgrade page says Alpenglow activates in epoch 1064, "which starts on October 21, 2026, at approximately 13:20 UTC," and Triton One used the same 13:20 UTC figure in its migration explainer. The epoch start is not the switch. Triton describes a countdown of 5,000 slots, about 17 minutes, after the epoch begins, during which "the chain runs exactly as it does today." Slot 459,653,000 sits at the end of that countdown.

Solana Compass epoch records put both moments a little later than 13:20 UTC. Epoch 1063 began at 11:37 UTC on 20 October, and the last full epoch, 1062, ran 26.1 hours at an average of 217.7 ms per slot. At that pace, epoch 1064 starts around 13:44 UTC on 21 October and slot 459,653,000 arrives around 14:02 UTC, in line with Anza's estimate. That is our arithmetic, and with roughly 375,000 slots still to go, each millisecond of drift in the average slot time moves the boundary by about six minutes. Triton's advice covers it: "Don't hard-code a date." The new getAgGenesisCert RPC method returns null while TowerBFT runs and a certificate once Alpenglow is live, so an RPC node gives the real answer.

What happens on Solana at slot 459,653,000

Triton expects the handoff itself to be brief. For about two slots, roughly 400 ms, blocks carry only validator votes and user transactions do not land. Then transactions land again and blocks finalize in about 150 ms, down from 12.8 seconds under TowerBFT, per Triton. "There's no going back to the old consensus afterwards," Triton wrote.

Galaxy Digital's Solana engineers, who have run validators on the Alpenglow community test cluster since 18 June 2026, describe 150 ms finality as a design target in a write-up published on 20 October. Galaxy's engineers also set out the new fault model: the share of malicious stake the network tolerates falls from 33% to 20%, but it can now keep running with a further 20% of stake offline. Slashing for double voting "is well defined but deliberately not enabled in the first iteration," they wrote, and Proof of History retires once the migration completes. The mechanics behind the faster finality are in our explainer on what Alpenglow changes for validator costs and finality.

Alpenglow readiness: 20.3% of Solana stake flagged unprepared on 20 October

On the morning of 20 October, SolanaFloor reported that 151 validators holding 20.3% of stake remained unprepared, citing data from Pumpkin's Pool's Alpenglow tracker. That snapshot, posted at 10:59 UTC, compares with the 45% of stake the same tracker flagged as not ready on 19 October. Most of the 19 October figure was validators on Agave 4.3.0 and 4.3.1, and SolanaFloor's post does not say how the tracker now counts them, so it is not clear how much of the drop comes from upgrades. The number keeps moving as operators update.

The Solana Foundation lists three requirements. Validators must run Agave, Jito JTO$0.472+7.5%-Solana or Harmonic Salsa at version 4.3.2, the release Anza named as recommended on 16 October. They need a registered BLS key, and they must hold at least 0.8 SOL in the vote account above its rent-exempt minimum to pay the per-epoch Validator Admission Ticket. The Foundation says validators without a BLS key are excluded from the admitted set, stop voting and stop earning inflation rewards, and a validator that does not pay the ticket fee does not vote or produce blocks in the next epoch. Stake delegated to a validator that is not voting earns no inflation rewards either, so delegators may want to look up their validator's status before Wednesday.

Firedancer operators are a separate case. "Operators on Firedancer can fail over to Agave beforehand and return afterwards, since Firedancer's 26.10 release supports Alpenglow," Galaxy's engineers wrote, adding that Frankendancer will not be supported once Alpenglow is active. Firedancer's developers have also opened a bug bounty with higher payouts for Alpenglow findings.

What Alpenglow changes for RPC, gRPC streaming and indexing users

Triton One's post on X put it in capitals: "If you stream, index, or measure the chain, action is REQUIRED!" Applications that only send transactions and read accounts have nothing to do. For everyone else, Triton's guide to updating before mainnet lists the changes:

• Vote transactions leave blocks, so transaction counts will "fall sharply," with no real activity lost.
• Transaction and account updates should be grouped by (slot, bank_id), not by slot alone.
• Ticks are gone, so code that reads time from ticks stops working.
• Code that waits for confirmed commitment should move to finalized, but only once Alpenglow is live on mainnet. Switching early means waiting the old 12.8 seconds.
• Triton's gRPC customers need yellowstone-grpc-client v15.0.0 for Rust or @triton-one/yellowstone-grpc v9.0.0 for TypeScript.

Triton also says its preconfirmation streams will be unavailable during the switch and subscribers will not be billed.

The vote change will show up on every Solana transaction chart. Votes made up about 62% of all transactions on Solana between 13 and 19 October, according to Solana Compass network data: roughly 264 million vote transactions a day, against 145 million to 173 million non-vote transactions. When votes leave the blocks, headline TPS figures that count them will drop by about that share, while the non-vote activity stays where it is.

What to watch on 21 October

Anza says a 24-hour countdown starts soon, but the switch itself is defined by a slot, not a clock. The markers are epoch 1064 starting on 21 October, the 5,000-slot countdown that follows, slot 459,653,000, and the first non-null answer from getAgGenesisCert. The other number to watch is the unprepared share of stake when epoch 1064 begins, since validators that miss the Foundation's requirements stop voting under its rules.

Alpenglow replaces the TowerBFT voting Solana has used since launch, which Galaxy's engineers call the largest change to the core protocol since the network went live. Testnet and devnet each made the same switch in September, and devnet's handoff at slot 504148999 is the closest rehearsal for what mainnet attempts on Wednesday.