sol2go.lol Before Solana gets 150ms finality, two gates had to open
Alpenglow is the largest change to how Solana agrees with itself since the chain launched, and the headline number is the one everyone repeats. The number underneath it is the one that explains why this has taken a year.
The numbers
The Foundation states the target plainly: “roughly 150ms finality, compared with Solana's current roughly 400ms pre-confirmation latency and 12.8-second TowerBFT finality.” The 400ms figure is the one applications already feel. The 12.8 seconds is the one that matters to anything settling value, and it is the one Alpenglow is aimed at.
More broadly, Alpenglow “makes changes to how Solana thinks about blockspace, finality, voting, and rewards” — four things at once, which is why it does not ship as a single switch.
What already happened
BLS Pubkey Management in Vote Account (SIMD-0387) activated on mainnet on 8 July 2026. The Validator Admission Ticket (SIMD-0357) activated on mainnet on 22 July 2026. Neither turns Alpenglow on. They are the plumbing it needs to exist before the consensus change can be switched at all.
What has not happened yet
Devnet activation is listed against Agave 4.3, and expected mainnet activation against Q3 2026 — a quarter that ends this month. Read those two lines together and the honest summary is that the schedule is tight and the page has not been updated to say otherwise.
What to do about it
If you run a validator, the July gates are already behind you and 4.3 is the release to be reading. If you build applications, nothing in your code changes on activation day — but a finality budget you wrote around 12.8 seconds is a design assumption worth revisiting rather than inheriting.
The interesting thing about a two-stage rollout like this is what it tells you about the risk model. Both July gates are additive: a BLS public key in a vote account and an admission ticket are new fields and new checks, and neither changes what the network agrees is true. The consensus switch is not additive, and it is the only part that can split the network if it goes wrong — so it is deliberately last, deliberately on devnet first, and deliberately separated from the plumbing by three months. Anyone reading the July activations as “Alpenglow is live” has read the changelog and not the design.
Source: Solana Foundation checked against the source
