In this article6 sections
Solana’s Alpenglow consensus migration took effect on Oct. 21, 2026, with epoch 1064 as the trigger, and blocks no longer carry validator vote transactions, according to Crypto.news reporting by Lawrence Mondal. Co-founder Anatoly Yakovenko questioned how the upgrade was built, saying in an Oct. 21 post on X that the project could have shipped in half the time if the team had simply moved the vote program to an “ag state machine.”
Crypto.news reported that Yakovenko made the comment while replying to a post celebrating the removal of on-chain votes and mocking a familiar criticism: that most of Solana’s transactions per second were validators voting. Anza, the development shop behind the client software, documented a replacement for TowerBFT, the mechanism validators used to agree on blocks, built on direct voting and compact certificates.
Also readDecrypt Money Accounts Go Live on Solana for Earn, Perps and Swaps
Key facts
- The Solana Foundation identified epoch 1064 as the migration trigger and estimated it would start around 13:20 UTC.
- The consensus handoff came 5,000 slots after feature activation, a window in which blocks temporarily contained only votes.
- Validators now pay a flat 0.8 SOL admission charge per epoch, drawn from the vote account, with the full amount burned.
- Before the transition, operators needed version 4.3.2 of Agave, Jito-Solana or Harmonic Salsa; Firedancer and Frankendancer were not supported during the handoff.
- Cryptobriefing reported that non-vote transactions on Solana reached 8.92 billion in the third quarter of 2026, a 104% increase over the final quarter of 2025.
Headline counts fall as votes leave blocks
The Foundation instructed explorers and analytics providers to reset transaction-count and TPS baselines, because vote transactions will no longer appear on-chain. A total that included votes will decline even if payments, trades and other activity hold steady. Services that track validator participation are told to read certificate data in block footers instead of Vote program instructions.
Yakovenko’s remark pointed at a lopsided metric rather than a drop in activity. Cryptobriefing reported separately that non-vote transaction volume reached 8.92 billion in Q3 2026, up 104% from Q4 2025, though that data does not break out how much came from organic users. Cryptobriefing framed the figure as evidence of network demand and noted that Alpenglow’s mainnet activation was among the technical developments market participants were watching.
Also readMoneyGram Joins Solana as Validator, Adopts SDP's One-API for Stablecoin Issuance
Fees move to a per-epoch charge
With votes no longer submitted as transactions, the fees paid on each individual vote disappear. Validators instead face a single admission charge of 0.8 SOL per epoch, paid one epoch ahead: the charge at the start of epoch 1064 covers participation in epoch 1065, and an operator that cannot pay forfeits the right to vote or produce blocks in that later epoch. Operators must keep the balance above the vote account’s rent-exempt minimum, the Foundation’s guidance said.
Two parallel voting paths replace TowerBFT under Anza’s design. One finalizes a block in a single round once 80% of stake responds; the other needs two rounds at 60% thresholds. Votes are signed directly with BLS cryptography so multiple signatures collapse into one compact certificate. Under the SIMD-0326 proposal, the admitted validator set is capped at 2,000, prioritizing the highest-staked operators so certificates stay small enough for a single UDP message. Governance cleared the change in September 2025, when the proposal passed with 98.27% support among votes cast and participating stake equal to 52% of the total.
Finality signals can trail consensus
Anza’s operator documentation qualifies the roughly 150-millisecond finality target: nodes outside the admitted validator set may learn of finality later, because the default path reads certificates from a subsequent block. That can add up to one produced-block interval, and longer when blocks are skipped or delayed. An admitted validator can push consensus messages straight to a partner node, but if every configured partner is unreachable, the recipient falls back to block footers.
Agave 4.3 provides an optional block-footer notification that services must enable and implement, and the chain clock keeps its existing format with whole-second precision, still treated as approximate during execution.
Why it matters
The change rewrites how Solana is measured. Dashboards that counted votes will show lower throughput while user-facing activity is unchanged, so cross-epoch comparisons require a reset. Validators face a predictable, burned epoch charge in place of variable vote fees, and the vote account becomes the funding source. Anyone running analytics, explorers or reward accounting on top of Solana has to adopt the certificate-based view to track participation accurately.
What to watch
The first 0.8 SOL admission payment, taken at the start of epoch 1064, covers eligibility for epoch 1065, so any validator that cannot cover the cost will drop out of voting there. Adoption of block-footer and certificate data by explorers, RPC providers and analytics services will determine how quickly public transaction counts and participation metrics settle into the new baseline.
Price references to SOL in the source reporting are not a forecast, and nothing here is financial advice; crypto markets are volatile and uncertain.
Sources: crypto.news, Cryptobriefing
