Native Rollups: When Ethereum L1 Starts to Look Like a Rollup

Native Rollups: When Ethereum L1 Starts to Look Like a Rollup

The boundary between Ethereum L1 and L2 is starting to disappear, but in the opposite direction from what most people would expect. Rather than L2s becoming more like L1, Ethereum’s own execution layer will become a rollup.

Two directions currently being discussed in the Ethereum community are relevant here: native rollups and single-slot finality (SSF). Neither is new on its own, but combined they produce something that did not exist before.

Native Rollups: Moving L2 Verification Into L1

Native rollups allow Ethereum L1 to directly verify an L2’s state transitions.

Instead of maintaining its own proof system and validation contracts, an L2 can rely on Ethereum’s native execution and verification infrastructure.

There is a clear trade-off. The L2’s execution environment must remain fully aligned with L1. In return, subsequent L1 upgrades can be inherited automatically.

This changes where the trust boundary sits.

Rollups today already settle to Ethereum in principle, but what users actually trust is each rollup’s own validation contracts and the upgrade permissions behind them. Native rollups remove this layer of custom trust assumptions by bringing verification directly into Ethereum L1.

Single Slot Finality: The Other Half of the Delay

Single Slot Finality addresses a different constraint.

Today, Ethereum L1 finality takes roughly 15 minutes. SSF aims to compress this toward a single slot.

For an L2 transaction today, settlement latency can involve two separate waits:

1. Proof generation and batch submission on the L2
2. Finality on Ethereum L1

Native rollups address the first. By allowing verification to happen synchronously within an L1 block, they can eliminate the separate delay associated with L2 proof generation and batch submission.

SSF addresses the second by reducing the time required for L1 finality.

The distinction matters because solving only one of these bottlenecks still leaves L2 settlement constrained by the other. Native rollups and SSF are therefore complementary rather than interchangeable.

When L1 and L2 Blockspace Begin to Converge

If both mechanisms are in place, the distinction between L2 and L1 blockspace becomes significantly smaller.

Add a based sequencer, and the two converge almost completely.

But the trade-off is equally clear.

By giving up control over a customized execution environment, an L2 also gives up much of its ability to differentiate at that layer.

Its role shifts from “another chain” to “an extension of Ethereum L1.”

For leading L2s that have already built mature technology stacks, ecosystems, and differentiated execution environments, this represents a genuine architectural trade-off.

Greater alignment with Ethereum can reduce custom trust assumptions and simplify inheritance of L1 improvements, but it can also reduce the architectural independence that has allowed individual L2s to differentiate.

Who Actually Generates the Proof?

There is another important aspect of this architecture: what is being proven is L1, not each individual L2.

Under this model, block builders generate a proof for the entire L1 block, and nodes verify that proof.

Because the L2 execution itself occurs within the L1 block, it is naturally covered by the same proof. The L2 does not need to generate a separate proof of its own, nor does it need to adapt whenever L1 changes its proof system.

This turns proving from something each rollup has to maintain on its own into infrastructure shared at the Ethereum base layer.

Was the Rollup-Centric Roadmap a Detour?

After years of pursuing a rollup-centric roadmap and investing heavily in ZK and proof technologies, Ethereum’s renewed emphasis on L1 scaling can make those earlier efforts look, at first glance, like a detour.

The opposite may be true.

Native rollups depend on L1 becoming provable. And making L1 provable depends heavily on the same proof technologies that have been developed, tested, and refined through years of competition and experimentation across the L2 ecosystem.

In other words, Ethereum’s L1 scaling roadmap does not necessarily invalidate the rollup-centric era that preceded it. It may increasingly build on it.

The proof infrastructure developed through L2s can become infrastructure for L1. The knowledge accumulated through rollup development can inform Ethereum’s own execution and verification architecture.

Seen this way, the rollup-centric roadmap has not simply been abandoned. Its outputs are becoming inputs for Ethereum’s next phase.

And if native rollups, L1 provability, and faster finality ultimately converge, the distinction between “scaling Ethereum” and “scaling on top of Ethereum” may become increasingly difficult to draw.

If you have any questions, please visit our community channels for support and more information.

Discord | Twitter | Telegram | Website | Blog