Solana 1.0 Is a Label; Alpenglow Is the Upgrade That Matters

Solana 1.0 Is a Label; Alpenglow Is the Upgrade That Matters

Solana 1.0, announced on 16 November 2026, is a renaming and versioning change, not a feature release. The real maturity step is Alpenglow, live since 21 October, which changed finality and the validator cost model. Validator revenue is still overwhelmingly inflation-funded, and no post-Alpenglow profitability data exists yet.

Blockchain Academics ResearchNovember 17, 2026
17 min read
Share

Executive Summary

Solana 1.0, announced on 16 November 2026, is a naming and versioning change. The Solana Foundation retired the "mainnet beta" label and gave validator clients a shared protocol version. It does not by itself activate any network improvement, and balances, accounts and history are unchanged. The substantive maturity step is Alpenglow, the consensus switch that went live on 21 October 2026, 26 days earlier.

Alpenglow's Phase 1, Votor, replaced TowerBFT. It targets finality of about 150ms, against about 12.8 seconds before. It arrived alongside 200ms slots and removed vote transactions from blocks. It also introduced the Validator Admission Ticket (VAT), a flat 0.8 SOL per epoch that is burned. Execution is unchanged, and Phase 2 (Rotor) has no date. The migration also required Agave-based clients (Agave, Jito-Solana or Harmonic builds), which cut against the client diversity that a shared version number is meant to protect.

Validator economics are still mostly inflation-funded. In stakefish's pre-Alpenglow sample, about 88% of gross validator revenue was issuance, and the inflation rate was 3.59% on 20 October 2026, well above the terminal rate. Fees and MEV tips are small and volatile. Whether they can replace falling issuance is unproven, and no post-Alpenglow profitability dataset exists. There is no evidence of a rerating tied to either event: SOL traded at $72.58 on 17 November 2026 (CoinGecko via DefiLlama).

Market Context

SOL traded at $72.58 on 17 November 2026, with a market capitalization of about $43.0 billion (CoinGecko via DefiLlama, 10:03 UTC). ETH traded at about $1,809 with a market capitalization of about $221 billion (same source and time). Blockonomi headlined that SOL had slid to a four-month low as the label changed, and said ETF outflows persisted. Outflow amounts were not available.

TECHi noted that SOL did not rally when Alpenglow activated. Neither event produced a visible rerating. That is consistent with the Foundation's own description of 1.0, discussed below.

On DeFi activity, DefiLlama shows Solana TVL at $4.78 billion on 17 November 2026. That ranks third, behind Ethereum at $37.49 billion and the Ethereum L2 Base at $5.18 billion.

What Actually Changed on 16 November: A Label, Not a Fork

On 16 November 2026 the Solana Foundation retired the "mainnet beta" designation and introduced "Solana 1.0" as a protocol version shared across validator clients (The Block). The announcement came at Breakpoint 2026 in London. Mainnet launched in March 2020, so the beta label lasted roughly 6 years 8 months.

Agave and Firedancer keep their own software version numbers. Users need take no action, and balances, accounts and history are unchanged. The Foundation said Solana 1.0 "recognizes the progress on network performance, resilience, and developer experience" and called the move a "simplification of nomenclature."

The Foundation was explicit about the limits. Assigning a protocol version does not automatically activate every associated network improvement. Validators and developers must keep following each client's own release guidance. In effect, 1.0 is a nomenclature and versioning change, not a feature release.

Decrypt adds that the announcement does not describe a new voting system or a change in who governs Solana. The SIMD process for proposals remains separate. A reader looking for a governance reform will not find one here.

The rename is also not fully propagated. Solana Compass reports that the Foundation's cluster page lists the production cluster as "Mainnet" (api.mainnet.solana.com). As of 16 November, Anza's docs still say "Mainnet Beta" (api.mainnet-beta.solana.com). The announcement does not address RPC endpoint names, so builders should not change configurations on the strength of the rename alone.

The table below separates the rename from the upgrade that preceded it.

Item

Date

What it is

Relation to Solana 1.0

Solana 1.0

16 Nov 2026

Retired "mainnet beta" label; shared protocol version number

The announcement itself

Alpenglow Phase 1 (Votor)

21 Oct 2026

Consensus switch replacing TowerBFT, shipped in Agave 4.3

Independent; went live 26 days earlier

Source: Solana Foundation, The Block, as cited in the text.

The institutional pipeline is a separate matter. According to The Block, DTCC announced plans to connect its tokenization service to Solana in the second half of 2027. Formation Securities notified the SEC of a tokenized securities trading venue on Solana, targeting early 2027. Schroders launched a tokenized emerging-markets debt fund on Solana via Centrifuge in early November 2026.

These are real signals of institutional interest. None of them depends on the rename, and none is caused by it. Some commentators, including TechFlow and an X post, argue that dropping "beta" eases institutional compliance hurdles. The Foundation's own statement does not say this, so treat it as opinion.

Alpenglow: The Real Upgrade

Alpenglow activated on Solana mainnet in epoch 1064, which began on Wednesday 21 October 2026 at about 13:36 UTC. It replaced TowerBFT and targets finality of about 150ms, versus about 12.8 seconds before (Solana Foundation). The Foundation frames this as a target rather than a guaranteed figure.

The path to activation was not frictionless. BLS public-key registration, a prerequisite, reached mainnet on 8 July 2026 under SIMD-0387. Alpenglow activated on devnet on 25 September. An expected 28 September mainnet date passed without activation, with Anza saying there would be no "Alpenrush." The final date was 21 October.

What the finality number means

The move from 12.8 seconds to 150ms is a roughly 85x speedup, or a 98.8% reduction (TECHi). It is not the "85% reduction" that some social posts claim. The 150ms figure measures time to finality, not block time.

Block time was cut separately, from 400ms to 200ms slots, in four stages completed in October 2026. Under Alpenglow the "confirmed" and "finalized" commitment levels now describe the same state, and vote transactions no longer appear in blocks.

The early measurement is good but short of the target. FinanceFeeds reports that the Foundation's dashboard showed observed finality of about 202 milliseconds on day one, roughly 35% above the 150ms target, with sustained performance still to be established. By my arithmetic, that reading is still about 63 times faster than the old finality time. One day of data does not show whether the target is reachable under load.

What Alpenglow does not change

Only Phase 1 is live. Phase 2, Rotor, replaces Turbine block propagation. The Foundation describes it as "planned for a later release" and "not yet scheduled." Execution is unchanged: the SVM, user transactions, programs and user transaction fees work as before. Only vote fees and validator costs changed.

That last point matters for how the upgrade is discussed. It is a consensus and finality change, and its second half has no date.

The Client-Diversity Wrinkle

The 1.0 framing presents a protocol version shared across clients. Alpenglow's activation did something different. At the migration, mainnet validators had to run Agave v4.3.2, Jito-Solana v4.3.2-jito or Harmonic Salsa v4.3.2-harmonic. The Foundation's page says Firedancer and Frankendancer "were not supported for the migration."

This sits uneasily with the shared-protocol message. For the cutover, the network was effectively Agave-based. I found no confirmation of when Firedancer support was added, and I do not state it as fact.

The counter-argument is fair. According to The Block, Jump Crypto's Firedancer went live on mainnet in December 2025 as an independently developed alternative to Agave, with separate codebases and version numbers. A shared protocol version exists precisely to decouple the protocol from any one client. The tension may be temporary, but it is not yet shown to be.

How much stake was affected

Syndica's April 2026 deep dive put stake at 86% Agave, 11% Frankendancer and 3% Firedancer. FinanceFeeds says Frankendancer reached roughly a fifth of staked SOL by early 2026. Those figures conflict, and other sources give different splits. No post-activation client split is confirmed, so I do not state a current Firedancer share.

Block production tells a similar story. Syndica's April data showed Agave Jito as the largest scheduler at 36%, followed by JitoBAM (28%), Harmonic (18%), and Rakurai and Vanilla at 2% each. Software diversity existed at the scheduler layer, but the migration list names only the Agave, Jito-Solana and Harmonic builds.

On participation, Alpenglow's mainnet genesis block (slot 459,652,999) was certified with votes from 446 of the network's 654 validators. That also gives the validator-set size at activation. The sources I have do not explain why the remaining validators did not vote in that block, and I draw no conclusion about it.

Validator Economics: Still Mostly Inflation

The central economic fact is unchanged by either announcement. Validators are paid mostly in newly issued SOL. Alpenglow changed their cost structure, but no revenue replacement has appeared yet.

Where revenue came from before Alpenglow

stakefish's sample covers late September to 20 October 2026, before activation. It shows a heavily inflation-funded model.

Revenue source

SOL per day

Share of gross validator revenue

Inflation

57,580

88.2%

Block fees

5,806

8.9%

Jito tips

1,885

2.9%

Total

65,271

100%

Source: stakefish, sample of late September to 20 October 2026. These are stakefish's own derived figures.

Fees and tips together were about 11.8% of gross revenue. On 438.6 million SOL of active stake, stakefish says they add only about 0.64 percentage points of gross annual yield. Jito tips are a minor line, not the main revenue source.

MEV and tips are volatile

Jito tips swung widely over 12 months. The peak was 4,838 SOL per day at epoch 922 (starting 5 February 2026). The low was 809 SOL per day at epoch 1028 (starting 3 September 2026). The median epoch was 1,431 SOL per day. That is about a 6x swing tied to trading demand.

The MEV market is also changing shape. Jito's Block Assembly Marketplace (BAM) reached 378 validators and about 33% of stake by the end of Q2 2026. Jito generated about $1.28 million in Q2 2026 revenue, down 45% from the prior quarter (Analytics Insight). This can be read as a maturing market spreading across BAM, Harmonic and Rakurai, or as a shrinking one. The data here cannot separate the two.

The vote-fee swap and the VAT

Alpenglow rewrote a fixed cost. Under TowerBFT, voting cost about 1 SOL per epoch in vote transaction fees. Under Alpenglow, votes are not transactions, so those fees are gone.

Each voting validator instead pays a flat 0.8 SOL per epoch VAT (SIMD-0357), taken from the vote account and burned. The fee is paid one epoch ahead. A validator that cannot pay does not vote or produce blocks the following epoch.

On the Foundation's figures, the flat fee is about 0.2 SOL per epoch lower than the vote fees it replaced. The burn is a second effect: the VAT removes SOL from supply rather than paying it to another party. I have no data on how much it removes in aggregate, so I do not estimate the offset against issuance.

Epoch length matters here. The VAT is charged per epoch, and epochs have shortened as slots got faster. Average slot time fell from 397ms (epoch 881, November 2025) to 218ms (epoch 1062), and epoch length fell from about 48 hours to about 26 hours. At 26 hours, a year holds roughly 337 epochs, so the flat fee costs about 270 SOL a year. That is my arithmetic, and it moves with epoch length.

A fixed per-epoch charge is a larger share of revenue for smaller validators, though the VAT is lower than the vote fee it replaced. Solana Compass estimates that on late-October 2026 numbers a validator with 100,000 SOL staked at a 5% fee earns about 670 SOL a year before costs. Against that, a VAT of about 270 SOL (my arithmetic) is roughly 40% of the 670 SOL estimate, but it replaces roughly 337 SOL a year of vote fees at the same epoch length, so on these figures it lowers a fixed cost rather than adding one. I do not know whether the Compass estimate already nets out voting costs, so treat the comparison as an illustration of sensitivity, not a measured margin.

For scale at the other end, Compass reports Figment as the largest validator by stake, at about 17 million SOL and a 7% fee. A flat fee is trivial for an operator that size. This is my inference from the figures, not a finding from the sources.

SIMD-0525 doubled the protocol's slots-per-year setting so that annual issuance stays the same. Per-epoch comparisons over the past year are therefore misleading. stakefish says issuance per calendar day now runs about 8% below the headline rate, so analysis should use calendar time.

What we cannot measure yet

stakefish notes that its sample predates Alpenglow. Some block fees in the sample came from vote transactions, which no longer go on chain. It expects block fees to run lower post-Alpenglow and says it will rerun the numbers. I found no post-Alpenglow validator profitability dataset.

So the net effect of Alpenglow on validator margins is unmeasured. Lower vote fees help costs. Possibly lower block fees hurt revenue. A burned flat ticket replaces the per-epoch vote fee with a fixed charge about 0.2 SOL lower. Any claim that validators are better or worse off since 21 October is, at present, an assertion without data.

One more claim should be set aside. Social commentary suggests "execution certainty" or execution-service sales are a new validator revenue model after 1.0. I found no primary source for this, and I do not treat it as fact.

The Inflation Path and the SIMD-0411 Debate

The getInflationRate RPC returned a total inflation rate of 3.5937% on 20 October 2026, with total supply of 636,151,765 SOL (stakefish). The schedule on the node is an 8% initial rate tapering 15% a year toward a terminal rate of 1.5%. The rate is not near that floor today.

SIMD-0411, authored by Lostin and 0xIchigo of Helius, proposed doubling the disinflation rate from -15% to -30%. This would reach the terminal rate in about 3.1 years (early 2029) instead of around 2032. The proposal was first published around late November 2025.

The authors' analysis said validators would need at least 556,000 SOL to break even long-term at that floor. Unchained reported estimates that as many as 47 validators would turn unprofitable in year three. These are the proposal's projections, built on its own cost assumptions, which are not in my fact table.

I could not confirm the proposal's final status. stakefish's October 2026 RPC description still shows the 15% taper, which suggests it has not taken effect. The proposal also predates Alpenglow and the VAT, so its cost assumptions would need rerunning under the new fee model.

The structural point holds either way. On the current schedule, issuance declines slowly and the floor arrives years out. Revenue pressure on validators is therefore gradual unless the schedule changes. If it does change, or if the floor is reached, the question of whether fees and MEV can fill the gap becomes urgent. With fees and tips at a small share and tips swinging about 6x, the replacement is not visible in current data.

Competitive Positioning and the Market's Verdict

The fastest finality number on a chain does not by itself move capital. Ethereum holds roughly 8x Solana's DeFi TVL, and Base, an Ethereum L2, holds more than Solana as of 17 November 2026 (DefiLlama). The TVL data alone cannot show whether consensus speed is a factor in this gap.

The bull case for maturity reads the rename, Alpenglow's finality, a shared protocol version and the institutional pipeline together as production-grade readiness. That case is coherent. Its weakness is that the Foundation itself calls the rename a simplification of nomenclature, and the market response has been muted to negative.

The skeptic case rests on narrower, documented points. Finality is a target, and the first day's observed reading (about 202ms) was slower than it. Rotor is unscheduled. Execution is unchanged. The client-diversity picture at activation was Agave-based. None of these points says Alpenglow failed. They say the evidence for success is early.

Tokenization pipeline items from DTCC, Formation Securities and Schroders are scheduled for 2027 or just launched. They suggest institutional interest in Solana as settlement infrastructure. They do not yet translate into on-chain TVL or validator revenue that I can measure from the sources here.

What to Watch

  • Rotor timing. Phase 2 replaces Turbine block propagation and is not yet scheduled. A date would be the clearest sign that the Alpenglow program is on track.
  • Firedancer and Frankendancer support. I could not confirm whether or when these clients gained Alpenglow support after the migration. A confirmed post-activation client split would settle the diversity question.
  • Post-Alpenglow validator revenue. stakefish has said it will rerun its numbers. That is the first dataset that can show how block fees, tips and the VAT net out.
  • Sustained finality against the target. A single day's reading is not a trend. Weekly or monthly observed finality is the relevant series.
  • Inflation schedule governance. Watch for SIMD-0411 or a successor. Any acceleration of disinflation would put validator margins at the center of the debate.
  • Endpoint and documentation cleanup. The rename is incomplete across docs and RPC endpoint names. This is minor, but it affects builders directly.

Risks

Risk

Rating

Trigger

Client concentration around Alpenglow

High

Firedancer and Frankendancer support stays unconfirmed, so a bug in an Agave-based build could affect a large share of the network (the current stake split is unconfirmed)

Validator attrition among smaller operators

Medium

Post-Alpenglow data shows lower block fees, and disinflation is accelerated by a SIMD-0411-style change; the fixed VAT is a larger share of revenue at small stake, though lower than the old vote fees

Fee and MEV revenue fails to replace issuance

Medium

Tips stay near the low end of their historical range; Jito-like revenue keeps falling

Finality below target

Medium

Observed finality stays well above the target under load

Rotor delay

Medium

No schedule is published and Rotor remains undated well into 2027

Expectation gap from the 1.0 label

Medium

Investors or builders treat the rename as an upgrade and are disappointed when no feature arrives

Competitive TVL gap

Medium

Base and Ethereum continue to hold more DeFi TVL than Solana

Naming and endpoint confusion

Low

Tooling or docs keep mixed "Mainnet" and "Mainnet Beta" references and break integrations

The High rating on client concentration reflects uncertainty, not a known failure. Its status could change quickly if Firedancer support is confirmed. The Medium ratings on validator economics reflect missing data. Without post-Alpenglow figures, I cannot rate them higher or lower with confidence.

Outlook

The 3 to 6 month view runs from now to roughly February, May 2027. The probabilities below are my estimates. They reflect the evidence in this report: a real upgrade is live and its early data is promising but thin, and the economic questions will not resolve quickly.

Base case (about 55%)

Alpenglow's Votor phase keeps running without a major incident. Observed finality settles somewhere between the day-one reading and the target. Rotor remains unscheduled or is scheduled for later in 2027. stakefish or others publish a first post-Alpenglow revenue dataset showing lower block fees, offset partly by lower vote costs. The 1.0 label fades from the conversation, and price action follows broader market conditions rather than protocol news.

Upside case (about 20%)

Rotor gets a firm date and Firedancer support for Alpenglow is confirmed, reducing the client-diversity concern. Sustained finality lands close to the target. Post-Alpenglow data shows validator revenue holding up, with tips recovering from their lows. Institutional tokenization announcements start translating into measurable on-chain activity.

Downside case (about 25%)

Observed finality stays well above the target under load, or an Agave-based client bug causes an incident while diversity is thin. Post-Alpenglow data shows block fees falling and tips staying weak, pressuring smaller validators. The inflation schedule returns to governance debate in a way that accelerates disinflation. Muted market response persists, and TVL stays behind Base.

I weight the downside slightly above the upside because three things remain unmeasured (sustained finality, post-Alpenglow validator margins, client-diversity status) and the known data points lean against the targets: day-one finality of about 202ms against 150ms, and falling Jito revenue. The base case, not the downside, is the most likely outcome because I found no report of an incident in the Phase 1 rollout, though I did not systematically search for one.

Takeaways

Traders. Do not treat the 1.0 announcement as a catalyst. The Foundation says it is a nomenclature and versioning change, and the market has not rerated on it. Watch the dated items: Rotor scheduling, finality data and post-Alpenglow validator data. Burned VAT supply effects are not yet quantified, so avoid building a thesis on them.

Builders. The rename requires no action. Do not change RPC endpoints until the Foundation or Anza documentation confirms the new names. Update assumptions about commitment levels, since "confirmed" and "finalized" now describe the same state under Alpenglow. Treat 150ms as a finality target, not a block time. Execution behavior is unchanged.

Investors and validators. Underwrite validator economics on issuance, not on fees and MEV, until post-Alpenglow data exists. Small operators should model the flat VAT against their own revenue and watch epoch length, since the fee is charged per epoch. Inflation is still well above its terminal rate, so the squeeze comes with the schedule, not today. The question to track is whether fees can grow before issuance falls.

Sources

Discussion

Loading comments...