Alt-L1s: Why Smaller Chains Are Moving to Ethereum
See why Zilliqa, Gnosis and Ronin are moving toward Ethereum, what L1 economics have to do with it, and why independent chains still have a case.

Are Alt-L1s Becoming Ethereum L2s? The Economics Behind the Shift
An independent Layer 1 lets a project control its consensus rules, validators, and technical roadmap. That freedom can matter a lot. But it also comes with a very unglamorous job: you have to attract enough users and economic activity to keep the chain secure and running. For smaller networks, that bill can be hard to justify.
So it's not surprising that Zilliqa, Gnosis, and Ronin have all moved closer to Ethereum. Zilliqa has announced plans to become an Ethereum Layer 2 (L2), Gnosis is working on a transition that uses Ethereum settlement, and Ronin completed its move to Ethereum as an L2 in May. The common thread isn't just "Ethereum is popular" - it's that operating a chain gets expensive fast, and tying into a bigger ecosystem can be the difference between surviving and stalling.
That said, this isn't proof that independent L1s are doomed. Ethereum can help with shared security and liquidity access, but an L1 can still make sense when a project needs specific rules, tighter control, or a dedicated environment. The real question isn't which model sounds better on paper. It's which one can support the users it needs, without taking on risks the team can't actually manage.
This article looks at the economics behind the shift, what Ethereum integration can add beyond lower operating costs, and why the L1-versus-L2 debate is still very much alive.
Why are smaller L1s moving toward Ethereum?
Running an independent L1 is more than processing transactions. You also need a consensus mechanism, validators, incentives that keep those validators participating, and enough users and applications to sustain demand over time. On top of that, the project has to maintain the software and infrastructure that keep the network reliable.
Autonomy isn't free, either. A team can be capable and the community can be real - and still struggle to generate enough fees, liquidity, or funding to pay for security. That's the gap many smaller chains run into: building is hard, but keeping the whole machine funded is harder.
Zilliqa's announcement nailed that tension. After years of running its own L1, it said standalone usage hadn't grown to the point where the model worked. It also cited weaker funding and liquidity for independent L1s, along with the security burden that's become more obvious after recent hacks. In other words, the decision to move toward an Ethereum-based L2 is basically a recognition that the architecture has to match the economics.
Gnosis and Ronin point to different ways of getting closer to Ethereum. Gnosis has described an Ethereum Economic Zone initiative meant to let participating networks use shared Ethereum settlement and interact synchronously. Ronin - focused on gaming - finished its transition to Ethereum as an L2 in May. Their approaches aren't the same, but both reflect a choice to rely on Ethereum more directly instead of operating every part of a separate L1 stack.
This shouldn't get reduced to "Ethereum is safer" or "L2s are cheaper." Those claims skip the important part. The real issue is whether the costs and responsibilities a project gives up are worth the security, settlement, and ecosystem access it gains. That depends on what users want, how the chain earns revenue, and how much control the team really needs.
When teams evaluate a move, a common trigger is mismatch. The security and operating costs may be sized for an ecosystem that hasn't fully arrived yet. Changing architecture can help close that gap. But it won't magically create demand or fix weak economics by itself.
What does an independent L1 really cost?
A standalone chain has to provide (or arrange) execution, consensus, data availability, and settlement. It also needs a credible way to pay for network security - often through staking incentives. Those aren't one-time setup items. They're ongoing obligations that require people, capital, and dependable operations.
Max Shannon, a senior research analyst at Bitwise, frames this in terms of profitability. In his analysis, a small set of leading chains brings in meaningful fee income, while activity drops off sharply after the top tier. The numbers he cites show that uneven distribution: Coinbase's and Robinhood's L2 networks generated tens of millions of dollars in fees over the preceding 365 days, while the next eight largest chains each generated more than $1 million annually. From 11th place onward, the combined annual fees for the chains he lists were under $1 million.
That's a useful warning, not a full picture of any one network's finances. Fees aren't profit. Costs can include incentives, ecosystem grants, and other commitments, and fee levels can swing with activity. Still, the broader point stands: technical ambition alone doesn't guarantee the recurring revenue needed to keep the infrastructure running.
An L2 can reduce how many functions a project has to operate on its own. Shannon notes that L2s mainly need to maintain execution and may not need a separate token for security. That can improve the operating and financing equation - but it doesn't automatically make the business profitable. He points to Optimism, Katana, and Linea as examples where expenses have outweighed fee revenue, and he notes that Blast shut down.
A realistic comparison has to cover more than validator costs or transaction fees. Teams should think about:
- Security funding: What incentives make attacks expensive?
- Operating overhead: What systems and teams does the project still have to run?
- Revenue quality: Are fees recurring and broad-based, or tied to temporary activity?
- Migration costs: What does it take to move users, apps, assets, and developer tooling?
- Control and risk: Which decisions become dependent on another network, and what happens if that dependency breaks?
The decision isn't "L1 costs more, so choose an L2." It's whether the extra control of an L1 produces enough user or business value to cover the full cost of providing it. If not, the project may end up paying for sovereignty it doesn't really need.
What does Ethereum add beyond lower costs?
Ethereum integration isn't only about outsourcing parts of security or reducing operational burden. It's also about connecting to an existing base of developers, applications, and liquidity. For smaller or newer networks, that can reduce the friction users face when trying to find assets, tools, and counterparties - things you simply can't fabricate quickly from scratch.
Ethereum's settlement role can also change how responsibility is divided. Alex Gluchowski, co-founder and CEO of Matter Labs, argues that an independent L1 has to maintain security while also building something people will use. Sharing Ethereum's security, in his view, gives teams more room to focus on users. That framing is hard to argue with: infrastructure only matters if it supports a product people actually need.
Gnosis's Ethereum Economic Zone plans aim at another problem: how separate networks feel from each other. Its RollupX test network is designed to show how participating chains could share Ethereum settlement and support synchronous composability. The practical goal is straightforward: a smart contract on one network could call a contract on another and use the result in the same transaction, instead of relying on slower bridge-and-wait workflows.
If that works as intended, separate networks could feel less isolated while keeping some distinct features. Ethereum supporters often talk about a stronger liquidity hub - participating chains benefiting from a wider pool of assets and activity. Still, it's worth treating that as a design target, not a guaranteed outcome. Cross-network composability is difficult to implement safely, and shared settlement doesn't eliminate every dependency or failure mode.
There's also a difference between integrating and giving up control. Gluchowski's argument is that sovereignty and Ethereum integration don't have to be opposites. A project may keep control over its rules and operations while using Ethereum for shared settlement. The exact degree of control depends on the architecture and governance choices, so teams shouldn't assume that every Ethereum-based chain works the same way.
Private applications add another layer. Some products need to protect transaction data or operate in a restricted environment while still tapping into public liquidity. Shared settlement doesn't automatically mean every transaction detail goes public, but privacy requirements do add complexity. As Gluchowski points out, connecting private environments while preserving useful interoperability is a hard problem - not something that simply follows from moving to Ethereum.
Does every chain need Ethereum?
No. Moving to Ethereum can be a sensible trade when a project values shared security, ecosystem access, and less operational responsibility more than it values full independence. But it isn't a universal upgrade. Some products need a purpose-built execution environment, specific governance rules, control over transaction ordering, or operational requirements that are harder to satisfy on a shared network.
The market also doesn't point to one winner. While Coinbase and Robinhood have launched L2s, other major projects have continued with independent L1 designs. Examples cited include Circle's Arc, Stripe's Tempo, and Hyperliquid's purpose-specific perpetual futures chain. The takeaway is simple: teams still see reasons to build outside Ethereum's L2 ecosystem.
A specialized chain can work when its design solves a concrete problem a general-purpose network doesn't handle well. In practical terms, the team has to explain that value in operational language - what users can do, what gets better, and why that improvement is worth the cost of running the network. "We want sovereignty" doesn't hold up if there isn't a durable user need underneath it.
The reverse is also true. An Ethereum L2 isn't automatically a sustainable business. Lower infrastructure responsibility can make the cost structure lighter, but the network still needs users, useful applications, reliable operations, and a way to cover its expenses. Moving into a larger ecosystem may make adoption easier, but it can't manufacture product-market fit.
Interoperability is another unresolved trade-off. Today, many L2s still aren't truly integrated with each other or fully with Ethereum in a way that feels seamless to users. Bridges and cross-network workflows can add delay, complexity, and new security concerns. As more applications combine private activity with public liquidity, interoperability stops being "nice to have" and starts affecting what the product can actually offer.
A practical way to start is with four questions:
- What does the user actually require? Start with the need behind the architecture, not the chain's preferred pitch.
- Can the project fund security and operations through a market cycle? Model recurring costs against conservative revenue, not peak conditions.
- Which responsibilities must stay under the team's control? Separate real product requirements from assumptions baked into the original design.
- What new dependencies does the move introduce? Compare the risks of independence with reliance on another network, including settlement and interoperability constraints.
If the team can't explain why independent consensus is necessary, Ethereum may be the more defensible choice. If it can point to a specific user need that truly demands a separate chain, independence is still a valid option. Either way, don't treat the architecture like an identity - it can change as the product grows and requirements shift.
Key takeaways
- Running an L1 is bigger than transaction execution: security, consensus, infrastructure, and ongoing operations all matter.
- Ethereum integration can reduce some responsibilities and connect a project to existing developers, applications, and liquidity, but it doesn't guarantee profitability.
- L2s still face revenue, interoperability, and operating challenges. They aren't interchangeable, and their costs vary.
- Independent L1s remain viable when their control or specialization matches a clear, funded user need.
- Treat migration as a business and security decision, not a branding change. Compare full costs, benefits, and dependencies on both sides.
Conclusion
Zilliqa, Gnosis, and Ronin's moves toward Ethereum look like a practical reset: running a standalone L1 only works if the network can generate enough revenue, users, and security capacity to fund the infrastructure it's operating. For some teams, Ethereum integration offers a more sustainable path while still allowing selected forms of control.
But that doesn't make L2s the default answer. They still need working economics, a solid user experience, and interoperability that doesn't make life harder than it needs to be. Independent L1s stay relevant when autonomy serves a specific, funded user need. The best decision is the boring one: compare what each architecture costs, what it enables, and which risks it shifts - then pick the option the project can realistically sustain.