Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
A network extension explained, minus the Solana hype.
A network extension is a modular add-on that plugs into a blockchain’s base layer to add specialized execution, storage, or coordination without spinning up a separate chain.
The phrase started showing up in mid-2025 and has not stopped since. It is mostly a Solana term, pushed by the Solana Foundation as an answer to Ethereum’s Layer 2 rollups. If you hit it in a roadmap thread or a “is this just an L2 rebrand?” argument, that is the context.
This guide gives you the plain definition first, then the mechanism, then an honest verdict on the rebrand debate. You will also get the real projects that count today and where all this sits in Solana’s 2026 plans.
A network extension is a modular add-on that attaches to a blockchain’s base layer to give it a new, specialized job. That job might be faster order scheduling, EVM compatibility, or heavy off-chain compute. The key part is that it extends the existing chain rather than becoming a new one.
You will almost always see this term next to Solana. The Solana Foundation coined the modern usage, so most search results, roadmap posts, and debates trace back to that one network. If a piece talks about network extensions without mentioning Solana, treat it with suspicion.
Two quick misconceptions to clear up. This has nothing to do with browser network extensions or VPN features, despite the shared words. And it is not crypto slang like “printer on” or “cooking.” It is a technical scaling concept with a real definition.
The one-line version is simple. A network extension adds power to a chain from the inside, so activity stays close to the base layer instead of moving out to a bridged environment. That single design choice is what the rest of this guide unpacks.
A network extension works by adding a custom execution environment beside Solana’s mainnet while still settling to the same validators and base layer. Transactions get their specialized processing, then finalize where every other Solana transaction finalizes. The chain does not fork. It gains a new lane.
Picture Solana’s base layer as a highway. A network extension widens that same highway or adds a purpose-built service lane on it. A Layer 2, by contrast, builds a separate bypass road and bridges cars back to the highway later. That contrast is the whole pitch in one image.
The Solana Foundation’s Austin Federa has framed extensions as coordination and execution layers that plug in without competing for base-layer blockspace in a fragmenting way. Strip out the framing and the mechanical claim is concrete. Because settlement stays on Solana, assets and state do not get stranded on a side network.
This matters for how blockspace and data get handled. Ethereum’s rollups post data into dedicated space and settle proofs back to mainnet, a model worth understanding through how blobspace works. Network extensions aim to avoid that separate-data step by keeping execution attached to the base layer.
So an extension is closer to a specialized module than a new chain. It borrows Solana’s security and finality, adds its own logic, and returns results to the same ledger. When it works as described, users never feel a boundary at all.
A Layer 2 is a separate network that processes transactions off the main chain, then settles the results back to a base layer like Ethereum. Rollups are the common form. They batch transactions, often use zero-knowledge or fraud proofs, and post data to the main chain to stay verifiable.
The core Solana complaint about L2s is liquidity fragmentation. When activity spreads across dozens of rollups, the same asset gets split into many pools on many networks. Users bridge, wait, and juggle balances. A network extension tries to keep liquidity unified on one base layer instead.
Here is how the two models compare on the points users actually feel.
| Network Extension | Layer 2 Rollup |
|---|---|
| Settles directly to the base-layer validators | Settles to L1 after off-chain processing |
| Aims to keep liquidity unified on one chain | Can fragment liquidity across many rollups |
| No bridge step for the user in the default design | Usually needs a bridge in and out |
| Newer, less battle-tested | Proven and widely deployed on Ethereum |
| Attaches to Solana specifically | A general Ethereum-scaling pattern |
The comparison is not a clean win for either side. L2s are the more mature technology, with billions in value secured and years of live use. Many settle to Ethereum using zero-knowledge proofs, a hardened cryptographic method. Network extensions are the newer bet with less on-chain history.
There is also overlap with other “specialized chain” ideas, like dedicated appchains, which give one application its own environment. Extensions sit near that family but insist on staying inside the base layer rather than spinning off. The design intent is the real difference, not the marketing.
This is the debate that sent most people searching. On Crypto Twitter it reads as a Solana-versus-Ethereum fight, and both camps have a real argument. The honest answer is that they share goals but make genuinely different design choices.
The Solana camp, including Federa and co-founder Anatoly Yakovenko, argues the function differs. Extensions settle directly to the base layer, aim to keep liquidity unified, and avoid the bridge friction that rollups impose. In their telling, calling it an L2 misses what the design is trying to avoid.
The Ethereum-adjacent view pushes back. L2s are symbiotic with their base layer too, the underlying stack overlaps heavily, and a specialized execution environment settling to an L1 sounds a lot like a rollup with new vocabulary. From that angle, some of the distinction reads as branding.
The rebrand suspicion gets sharper when you look at how rollups are built, which is worth grounding through hybrid rollup designs that mix proof systems. If an extension borrows those same building blocks, the line between the two blurs fast. That is a fair thing to notice.
Culturally, this fight is very online, and the tribal edge is part of the story. So here is the non-cheerleading takeaway. Extensions and L2s want the same thing: more capacity without breaking a base layer. They chase it with different tradeoffs on settlement and liquidity. Which one wins is a question of results, not slogans, and the results are not in yet.
The category is easier to trust once you see real projects behind it. Several are already building as network extensions on Solana, each targeting a specific need rather than a general-purpose chain. The roster is young and will shift, so treat any list as a snapshot.
The clearest way to see the spread is by what each project actually does.
| Project | What It Does |
|---|---|
| Raiku | High-frequency trading and transaction scheduling, aimed at pro market activity |
| Neon EVM | Brings Ethereum Virtual Machine compatibility so EVM apps can run on Solana |
| Termina | Specialized high-frequency processing for demanding workloads |
| Lollipop | Compute verification, checking heavy off-chain work against the chain |
Map these back to real problems and the logic holds. Raiku targets traders who need tight scheduling. Neon EVM targets builders who want Ethereum tooling without leaving Solana. Termina and Lollipop target apps that need heavy compute or proof of that compute.
Notice what these projects are not. They are not each launching a rival chain and asking users to bridge over. The design goal is to keep everything anchored to Solana’s base layer, which is exactly the anti-fragmentation pitch that motivates the omnichain liquidity conversation more broadly.
One caveat before you get attached to any name. This category is early, so projects will appear, merge, pivot, or fade. A label like “network extension” is not a quality guarantee. It describes an architecture, not an audit result or a track record.
Network extensions do not sit alone. They are one piece of Solana’s broader mid-2026 direction, which pairs new execution options with core consensus work and a push toward regulated and institutional use. The headline consensus upgrade in this window is Alpenglow, aimed at faster finality and a rebuilt consensus path.
Alpenglow was approved by Solana validators in a network vote in 2025 and is designed to cut finality times sharply, as CoinDesk reported. That base-layer speed matters for extensions, since anything attaching to the base layer inherits its finality. A faster core makes the extension pitch stronger.
Maturity is where honesty counts. Some extensions are shipping and processing real activity. The category as a whole is still early, and “on the roadmap” is not the same as “battle-tested in production.” Both things are true at once.
So the fair read on timing is this. Network extensions are live in parts, not vaporware, but not a finished, proven layer either. If you are tracking Solana in 2026, watch the extensions alongside consensus upgrades rather than treating either as the whole story.
For everyday users, the promised upside is quiet but real. If extensions work as designed, you get smoother apps, unified liquidity, and new specialized products, all without learning a new bridge or juggling balances across side networks. The best-case outcome is that you never notice the plumbing.
For SOL holders, the framing is about base-layer value. Extensions are meant to route more activity through Solana’s validators rather than off to separate chains, which keeps fees, settlement, and liquidity on the network you already hold. That is the theory. Whether it plays out depends on adoption.
What does not change is worth stating plainly. In the default design you do not bridge to use an extension, and there is no automatic new token for every extension. If a project pushes a token hard, that is a choice by that project, not a rule of the category.
Before you trust any single extension, run a few quick checks.
One concrete thing to do this week: pick one named extension from the list above and read its own documentation on how it settles. That single habit separates informed users from headline followers.
A network extension in crypto is a modular add-on that attaches to a blockchain’s base layer to add specialized execution, storage, or coordination without launching a separate chain. It is mainly a Solana term for scaling.
Not exactly. Network extensions and Layer 2s share the goal of adding capacity, but extensions settle directly to Solana’s base layer and aim to keep liquidity unified, while L2s run off-chain and often bridge back. The design choices differ even where the goals overlap.
Network extensions stay attached to the base layer and try to avoid bridges and fragmented liquidity. Ethereum Layer 2s process transactions off-chain, post data back to the main chain, and usually require bridging. Extensions are also newer and less battle-tested than proven L2 rollups.
Partly. Some network extensions are shipping and processing real activity, while the category overall is still early. Being on Solana’s 2026 roadmap does not mean every extension is fully proven, so check each project individually.
The stated goal of network extensions is to avoid liquidity fragmentation by keeping activity on one base layer instead of spreading it across many separate networks. Whether they fully succeed depends on adoption and how each extension is actually built.
You do not need to buy anything to get up to speed. The best first move is to understand the model well enough to judge the next headline for yourself.
Start by following one named extension’s progress. Pick Raiku, Neon EVM, Termina, or Lollipop and read how it settles and what it actually does, not just its pitch.
From there, a few practical steps make the picture stick:
Treat the category as promising but unproven. The users who do well here are the ones who track the mechanics quietly and let results, not tribal arguments, decide the winners.