Showing posts with label Solana transaction count. Show all posts
Showing posts with label Solana transaction count. Show all posts

Solana Targets October 21 for Alpenglow - Why Transaction Counts Could Fall as Settlement Speeds Up

Violet and green network paths converge into a glowing crystal beneath an alpine dawn

Solana's next speed upgrade could make its transaction charts look worse, even when nothing is wrong.

Alpenglow is scheduled for October 21, according to the Solana Foundation's updated rollout guide. It targets roughly 150-millisecond finality, the point when a transaction becomes irreversible. The mainnet switch is still ahead, rather than an improvement traders can already measure in production. One less obvious change deserves attention before the countdown ends: validator votes will disappear from blocks.

Those votes currently contribute to transaction totals on dashboards that include them. Removing them can produce a sharp numerical drop without customers sending fewer payments or making fewer trades. Anyone comparing activity before and after the upgrade needs to check what the chart counts. A headline number can change because its ingredients changed. For SOL holders trying to judge demand, confusing that accounting change with an exodus would be an expensive reading mistake.

What 150 milliseconds actually means

The target concerns settlement certainty, rather than a promise that every wallet screen will refresh within 150 milliseconds. Anza's documentation says the target applies under normal network conditions. Its new voting system, Votor, replaces the voting and finality logic of Tower BFT. The network's computers exchange consensus messages, and certificates communicate the result. That is a change to how agreement is reached, with practical consequences for services waiting to treat a payment as final.

Different connections can still deliver that result at different speeds. Anza explains that a node outside the admitted validator set can learn finality from a certificate carried in a later block. That route can add a produced-block interval, and skipped or delayed blocks can extend the wait. Direct connections to an admitted validator provide another route, with their own network latency. So a faster consensus target does not make every provider, connection and application equally fast.

A rollout date, then a real-world test

The Foundation places activation in epoch 1064, expected to begin around 15:00 UTC on October 21. Epoch timing can drift, so the clock time is approximate. Its guide also describes a transition window before the new consensus takes over. Ordinary wallet users are not being asked to migrate their assets. The preparation falls mainly on the operators and developers responsible for keeping the network and its data services running.

Validators have a concrete funding requirement alongside the software work. Anza's vote-account guide sets the new admission ticket at 0.8 SOL per epoch, held above the vote account's rent-exempt minimum. An insufficient balance excludes the validator from voting and producing blocks in the following epoch. For readers, the useful checks after activation are whether settlement improves in the apps they use and whether activity comparisons exclude validator votes consistently. A successful upgrade should earn its reputation through those results, not through a countdown or a misleading chart.

---------------

Author: Rowan Marrow
Seattle Newsroom
Breaking Crypto News