← Articles

Solana Alpenglow Is Live: What Faster Finality Changes and How to Market It

Solana Alpenglow went live on 21 October 2026 and cut the time it takes for a transaction to become final from about 12.8 seconds to a target of about 150 milliseconds. Here is what that means in plain terms, what it changes for apps and users, and how teams can turn it into a story people care about.

By Sparx, Growth research team··8 min read

Key takeaways

  • Solana Alpenglow replaced the network's original consensus system on 21 October 2026. Its first phase, called Votor, cuts finality, the point at which a transaction can no longer be reversed, from about 12.8 seconds to a target of about 150 milliseconds.

  • Wallets, programs and transaction formats are unchanged, and users need to do nothing. Developers should still review timeouts, commitment levels and any dashboard that counts transactions, because vote transactions no longer sit in blocks.

  • Faster finality helps exchanges, payments, trading and bridges most. It becomes a marketing story only when a team turns it into something users can feel, such as instant deposits or a checkout with no waiting screen.

Solana Alpenglow is the largest change to how Solana agrees on its own history since the network launched, and it is now live. On 21 October 2026 validators switched off TowerBFT, the consensus system Solana had used since day one. The time for a transaction to become final dropped from about 12.8 seconds to a target of about 150 milliseconds, according to Anza, the developer firm that built it. Anza chief executive Brennan Watt called it "the largest, most ambitious blockchain upgrade since 'The Merge'", referring to Ethereum's 2022 switch to proof of stake.

For a founder building on Solana, the useful question is not how the protocol works inside. It is what changes for your users and whether you can turn that into a reason to choose your product. At AnkhLabs we spend a lot of time helping teams translate technical upgrades into words users understand. This piece covers both halves: the plain-English version of Alpenglow and the product and marketing work that follows it.

What is Solana Alpenglow?

Every blockchain needs a way for its validators, the computers that check and record transactions, to agree on which blocks are valid. That agreement process is called consensus. Alpenglow is Solana's new consensus protocol. Anza researchers Quentin Kniep, Kobi Sliwinski and Roger Wattenhofer published the design in May 2025 and described it at the time as "the biggest change to Solana's core protocol since, well, ever."

Alpenglow has two parts. Votor, the part that went live, changes how validators vote. Under TowerBFT each vote was written to the chain as its own transaction. Under Votor, validators send votes directly to each other and bundle them into compact certificates. A block can be finalised in one round if validators holding 80% of staked SOL agree, or in two rounds at a 60% threshold, according to the Solana Foundation's Alpenglow page. Rotor, the second part, will change how block data spreads across the network. It needs its own governance proposal and has no date yet, Bankless reported.

The key word is finality. A transaction is final when it cannot be reversed. Before finality, an exchange or a merchant receiving funds is taking a small risk that the payment disappears. After finality, the money is settled. On Solana that wait used to be about 12.8 seconds. For comparison, an Ethereum block takes about 15 minutes to finalise, according to ethereum.org.

How fast is Alpenglow in practice?

The 150 millisecond figure is a target, not a guarantee. The Solana Foundation says performance will depend on network conditions. Memeburn reported on 25 October 2026 that the Foundation's dashboard showed a latest observed finality of 202 milliseconds in the first days after the switch. Solana's own chart showed the slowest 5% of finality times falling from close to 10 seconds to well under one second.

The headline "85 times faster" also needs a footnote. Solana separately cut its block time from 400 milliseconds to 200 milliseconds in October 2026, before Alpenglow went live. Memeburn estimates that, measured against those faster blocks, the real gain is closer to 40 times. That is still a very large improvement, but it is the kind of detail a sceptical reader will check before they repeat your claim.

The switch itself was smooth. According to the Solana Foundation, Alpenglow consensus began at slot 459,653,000 at the start of epoch 1064 (Solana counts time in short slots, grouped into longer epochs). The genesis block for the new system was certified with votes from 446 of 654 validators. The handoff from the old system took about 900 milliseconds.

What does Alpenglow change for apps and users?

For users, nothing to do. The Solana Foundation says that for most people "transactions settle almost immediately, and wallets and apps work as they did before." Programs, fees and transaction formats stay the same.

For developers, a short review is worth doing. The Foundation's guidance for app teams includes these points.

  • Commitment levels. Solana apps choose how sure they want to be about a transaction before acting on it. The "confirmed" and "finalized" levels now describe the same state, and "confirmed" will be removed in a later release, so new code should use "finalized".

  • Timeouts and retries. Any waiting screen, retry loop or delay tuned around 12.8 seconds is now far too slow and should be shortened.

  • Data pipelines. Indexers and exchanges reading block streams should not assume one block per slot, and should reconcile data using the blockhash.

  • Timestamps. The on-chain clock now comes from the block leader, so logic that relied on the old method of averaging should be checked.

There is one change that matters for marketing more than engineering. Validator votes used to be counted in Solana's reported transactions. They are no longer in blocks, so raw transactions per second will drop. Bankless suggests non-vote transactions as the fair comparison. Any team that quotes Solana's throughput in a deck, or shows a transaction count on its own dashboard, should re-baseline before someone posts a chart claiming activity collapsed.

Which products benefit most from faster finality?

Anza named two groups in its launch announcement: exchanges crediting deposits and merchants processing payments. Both have the same problem. They want to release money or goods as soon as possible, and they have to wait until the transaction cannot be reversed.

Infrastructure provider Tatum adds bridges, on-chain order books and lending markets to that list. Bridges can release assets on the other chain sooner. Market makers on order books carry less risk from trades that might be rolled back. Lending protocols can act on liquidations faster, which also means oracles (services that bring prices on-chain) and bots built around the old timing need to be checked.

Games and consumer apps benefit less directly. An app that already acted on transactions before they were final to keep things snappy will see a smaller difference. The biggest wins sit wherever a business was waiting for certainty before it moved money.

How can teams turn Solana Alpenglow into a product story?

A consensus upgrade is a story about the network, and every Solana app gets it at the same moment. A team that just reposts "150ms finality" says nothing that the Solana Foundation has not already said. The story only becomes yours when you change something users can see.

  • Ship a visible change, then announce it. If you run an exchange, cut your Solana deposit confirmation time and show it on the deposit screen. If you run a payment product, remove the "processing" spinner. The announcement is the change, not the upgrade.

  • Measure your own end-to-end time. Users feel the whole journey, from tapping a button to seeing a balance update, and that includes your wallet, your RPC provider (the service that connects your app to the chain) and your interface. Publish your number, not the network's target.

  • Be precise about the claim. Say "a target of about 150 milliseconds" and link to the source. The 85x versus 40x debate shows how quickly a loose number gets picked apart.

  • Rewrite the copy around waiting. Words like "pending", "confirming" and "please wait" were written for slower settlement. Replacing them is cheap and users notice. For Zoop we rewrote the onboarding copy to remove crypto terminology at the wallet step, and the programme reached 2M+ user signups with a 25% signup-to-wallet conversion rate.

  • Pre-empt the dashboard story. Explain the drop in reported transactions to your community before a critic does. A short thread with the non-vote numbers is enough.

We wrote more about turning technical features into user benefits in our guide to web3 product marketing, and about talking to builders in web3 developer marketing.

What Solana Alpenglow does not fix

Speed is not demand. Memeburn put it well: "Alpenglow removes an excuse rather than creating demand." In the days around the switch, Solana's decentralised finance activity barely moved. DefiLlama data cited by Memeburn put the value locked in Solana DeFi at $5.87 billion and seven-day volume on decentralised exchanges at $12.21 billion on 22 October 2026. The same data put Solana's perpetual futures open interest at about 3.6% of Hyperliquid's.

That last number is a useful reminder. Hyperliquid won traders with a product they used every day, not with a consensus paper, as we described in our piece on Hyperliquid's growth strategy. Faster settlement makes Solana a better place to build that kind of product. Someone still has to build it and bring users to it.

There are also loose ends. Rotor has no date. Jump's Firedancer client did not support the migration, so its operators had to run Anza's Agave client temporarily, Bankless reported. Validators now pay a flat 0.8 SOL fee each epoch that is burned in full. None of this affects users directly, but it is part of the story if your audience is technical. For teams still choosing a chain, our comparison of the best blockchain to build on puts finality alongside the other factors that matter.

What we'd tell a founder building on Solana

First, do the engineering review before the marketing. Check your commitment levels, timeouts and transaction counts against the Solana Foundation's list. A launch post about speed that sits next to a stuck loading screen does more harm than no post at all.

Second, find the one moment in your product where users used to wait, and make it instant. That is your Alpenglow story. Write it in the user's words, show it in a short video, and give it a number you measured yourself. Our product marketing work usually starts with exactly this kind of moment.

Third, take the infrastructure story to the right audience. Developers and validators care about Votor, certificates and fault tolerance. Users care that their deposit arrived. Infrastructure can still build an audience of its own. For the blockchain infrastructure project Rayls, our campaign acquired 20K+ followers and delivered 500K+ campaign reach. You can find more examples in our case studies.

If you are planning to ship something on the back of Alpenglow and want a second opinion on how to tell it, talk to AnkhLabs.

The bottom line

Solana Alpenglow made transactions final in a fraction of a second, which matters most to exchanges, payments, trading venues and bridges. Users do not need to do anything, and developers need only a short review. The upgrade belongs to the whole network, though, so the teams that benefit most will be the ones that turn it into a change users can feel and describe it honestly, with their own numbers.

This article is for information only and is not investment advice. Figures are as of 26 October 2026.

← Articles

Solana Alpenglow Is Live: What Faster Finality Changes and How to Market It

Solana Alpenglow went live on 21 October 2026 and cut the time it takes for a transaction to become final from about 12.8 seconds to a target of about 150 milliseconds. Here is what that means in plain terms, what it changes for apps and users, and how teams can turn it into a story people care about.

By Sparx, Growth research team··8 min read

Key takeaways

  • Solana Alpenglow replaced the network's original consensus system on 21 October 2026. Its first phase, called Votor, cuts finality, the point at which a transaction can no longer be reversed, from about 12.8 seconds to a target of about 150 milliseconds.

  • Wallets, programs and transaction formats are unchanged, and users need to do nothing. Developers should still review timeouts, commitment levels and any dashboard that counts transactions, because vote transactions no longer sit in blocks.

  • Faster finality helps exchanges, payments, trading and bridges most. It becomes a marketing story only when a team turns it into something users can feel, such as instant deposits or a checkout with no waiting screen.

Solana Alpenglow is the largest change to how Solana agrees on its own history since the network launched, and it is now live. On 21 October 2026 validators switched off TowerBFT, the consensus system Solana had used since day one. The time for a transaction to become final dropped from about 12.8 seconds to a target of about 150 milliseconds, according to Anza, the developer firm that built it. Anza chief executive Brennan Watt called it "the largest, most ambitious blockchain upgrade since 'The Merge'", referring to Ethereum's 2022 switch to proof of stake.

For a founder building on Solana, the useful question is not how the protocol works inside. It is what changes for your users and whether you can turn that into a reason to choose your product. At AnkhLabs we spend a lot of time helping teams translate technical upgrades into words users understand. This piece covers both halves: the plain-English version of Alpenglow and the product and marketing work that follows it.

What is Solana Alpenglow?

Every blockchain needs a way for its validators, the computers that check and record transactions, to agree on which blocks are valid. That agreement process is called consensus. Alpenglow is Solana's new consensus protocol. Anza researchers Quentin Kniep, Kobi Sliwinski and Roger Wattenhofer published the design in May 2025 and described it at the time as "the biggest change to Solana's core protocol since, well, ever."

Alpenglow has two parts. Votor, the part that went live, changes how validators vote. Under TowerBFT each vote was written to the chain as its own transaction. Under Votor, validators send votes directly to each other and bundle them into compact certificates. A block can be finalised in one round if validators holding 80% of staked SOL agree, or in two rounds at a 60% threshold, according to the Solana Foundation's Alpenglow page. Rotor, the second part, will change how block data spreads across the network. It needs its own governance proposal and has no date yet, Bankless reported.

The key word is finality. A transaction is final when it cannot be reversed. Before finality, an exchange or a merchant receiving funds is taking a small risk that the payment disappears. After finality, the money is settled. On Solana that wait used to be about 12.8 seconds. For comparison, an Ethereum block takes about 15 minutes to finalise, according to ethereum.org.

How fast is Alpenglow in practice?

The 150 millisecond figure is a target, not a guarantee. The Solana Foundation says performance will depend on network conditions. Memeburn reported on 25 October 2026 that the Foundation's dashboard showed a latest observed finality of 202 milliseconds in the first days after the switch. Solana's own chart showed the slowest 5% of finality times falling from close to 10 seconds to well under one second.

The headline "85 times faster" also needs a footnote. Solana separately cut its block time from 400 milliseconds to 200 milliseconds in October 2026, before Alpenglow went live. Memeburn estimates that, measured against those faster blocks, the real gain is closer to 40 times. That is still a very large improvement, but it is the kind of detail a sceptical reader will check before they repeat your claim.

The switch itself was smooth. According to the Solana Foundation, Alpenglow consensus began at slot 459,653,000 at the start of epoch 1064 (Solana counts time in short slots, grouped into longer epochs). The genesis block for the new system was certified with votes from 446 of 654 validators. The handoff from the old system took about 900 milliseconds.

What does Alpenglow change for apps and users?

For users, nothing to do. The Solana Foundation says that for most people "transactions settle almost immediately, and wallets and apps work as they did before." Programs, fees and transaction formats stay the same.

For developers, a short review is worth doing. The Foundation's guidance for app teams includes these points.

  • Commitment levels. Solana apps choose how sure they want to be about a transaction before acting on it. The "confirmed" and "finalized" levels now describe the same state, and "confirmed" will be removed in a later release, so new code should use "finalized".

  • Timeouts and retries. Any waiting screen, retry loop or delay tuned around 12.8 seconds is now far too slow and should be shortened.

  • Data pipelines. Indexers and exchanges reading block streams should not assume one block per slot, and should reconcile data using the blockhash.

  • Timestamps. The on-chain clock now comes from the block leader, so logic that relied on the old method of averaging should be checked.

There is one change that matters for marketing more than engineering. Validator votes used to be counted in Solana's reported transactions. They are no longer in blocks, so raw transactions per second will drop. Bankless suggests non-vote transactions as the fair comparison. Any team that quotes Solana's throughput in a deck, or shows a transaction count on its own dashboard, should re-baseline before someone posts a chart claiming activity collapsed.

Which products benefit most from faster finality?

Anza named two groups in its launch announcement: exchanges crediting deposits and merchants processing payments. Both have the same problem. They want to release money or goods as soon as possible, and they have to wait until the transaction cannot be reversed.

Infrastructure provider Tatum adds bridges, on-chain order books and lending markets to that list. Bridges can release assets on the other chain sooner. Market makers on order books carry less risk from trades that might be rolled back. Lending protocols can act on liquidations faster, which also means oracles (services that bring prices on-chain) and bots built around the old timing need to be checked.

Games and consumer apps benefit less directly. An app that already acted on transactions before they were final to keep things snappy will see a smaller difference. The biggest wins sit wherever a business was waiting for certainty before it moved money.

How can teams turn Solana Alpenglow into a product story?

A consensus upgrade is a story about the network, and every Solana app gets it at the same moment. A team that just reposts "150ms finality" says nothing that the Solana Foundation has not already said. The story only becomes yours when you change something users can see.

  • Ship a visible change, then announce it. If you run an exchange, cut your Solana deposit confirmation time and show it on the deposit screen. If you run a payment product, remove the "processing" spinner. The announcement is the change, not the upgrade.

  • Measure your own end-to-end time. Users feel the whole journey, from tapping a button to seeing a balance update, and that includes your wallet, your RPC provider (the service that connects your app to the chain) and your interface. Publish your number, not the network's target.

  • Be precise about the claim. Say "a target of about 150 milliseconds" and link to the source. The 85x versus 40x debate shows how quickly a loose number gets picked apart.

  • Rewrite the copy around waiting. Words like "pending", "confirming" and "please wait" were written for slower settlement. Replacing them is cheap and users notice. For Zoop we rewrote the onboarding copy to remove crypto terminology at the wallet step, and the programme reached 2M+ user signups with a 25% signup-to-wallet conversion rate.

  • Pre-empt the dashboard story. Explain the drop in reported transactions to your community before a critic does. A short thread with the non-vote numbers is enough.

We wrote more about turning technical features into user benefits in our guide to web3 product marketing, and about talking to builders in web3 developer marketing.

What Solana Alpenglow does not fix

Speed is not demand. Memeburn put it well: "Alpenglow removes an excuse rather than creating demand." In the days around the switch, Solana's decentralised finance activity barely moved. DefiLlama data cited by Memeburn put the value locked in Solana DeFi at $5.87 billion and seven-day volume on decentralised exchanges at $12.21 billion on 22 October 2026. The same data put Solana's perpetual futures open interest at about 3.6% of Hyperliquid's.

That last number is a useful reminder. Hyperliquid won traders with a product they used every day, not with a consensus paper, as we described in our piece on Hyperliquid's growth strategy. Faster settlement makes Solana a better place to build that kind of product. Someone still has to build it and bring users to it.

There are also loose ends. Rotor has no date. Jump's Firedancer client did not support the migration, so its operators had to run Anza's Agave client temporarily, Bankless reported. Validators now pay a flat 0.8 SOL fee each epoch that is burned in full. None of this affects users directly, but it is part of the story if your audience is technical. For teams still choosing a chain, our comparison of the best blockchain to build on puts finality alongside the other factors that matter.

What we'd tell a founder building on Solana

First, do the engineering review before the marketing. Check your commitment levels, timeouts and transaction counts against the Solana Foundation's list. A launch post about speed that sits next to a stuck loading screen does more harm than no post at all.

Second, find the one moment in your product where users used to wait, and make it instant. That is your Alpenglow story. Write it in the user's words, show it in a short video, and give it a number you measured yourself. Our product marketing work usually starts with exactly this kind of moment.

Third, take the infrastructure story to the right audience. Developers and validators care about Votor, certificates and fault tolerance. Users care that their deposit arrived. Infrastructure can still build an audience of its own. For the blockchain infrastructure project Rayls, our campaign acquired 20K+ followers and delivered 500K+ campaign reach. You can find more examples in our case studies.

If you are planning to ship something on the back of Alpenglow and want a second opinion on how to tell it, talk to AnkhLabs.

The bottom line

Solana Alpenglow made transactions final in a fraction of a second, which matters most to exchanges, payments, trading venues and bridges. Users do not need to do anything, and developers need only a short review. The upgrade belongs to the whole network, though, so the teams that benefit most will be the ones that turn it into a change users can feel and describe it honestly, with their own numbers.

This article is for information only and is not investment advice. Figures are as of 26 October 2026.