Most Rollups execute transactions away from Ethereum and periodically publish transaction data or proofs back to Ethereum. This allows them to process transactions more efficiently while still using Ethereum as part of their security and settlement infrastructure. However, many Rollups rely on their own sequencers to determine transaction ordering, creating an additional component between users and Ethereum.
Based Rollups take a different approach. Instead of introducing a dedicated sequencing layer, they allow Ethereum block proposers to incorporate Rollup transactions into Ethereum blocks. This can make the sequencing process more closely integrated with Ethereum’s consensus and block-production mechanism.
The idea has attracted attention because it could improve decentralization and composability while reducing reliance on centralized Layer 2 operators. At the same time, Based Rollups involve trade-offs around revenue, transaction latency, sequencing flexibility and MEV management.
To understand Based Rollups, it helps to first separate the different jobs performed by a blockchain.
A Rollup generally needs to handle at least three major functions:
Traditional Rollups often perform execution offchain while using Ethereum for settlement and data availability.
The sequencing process, however, can remain separate.
For example, a Rollup may operate a centralized sequencer that receives user transactions, determines their order, executes them, and later submits the resulting data or commitments to Ethereum.
A Based Rollup changes this arrangement by making Ethereum’s block production process responsible for sequencing.
Ethereum researcher Justin Drake introduced the concept of Based Rollups in 2023, describing them as Rollups whose sequencing is “driven by the L1.” In this architecture, Ethereum’s validators can include Rollup transactions in Ethereum blocks without requiring a separate Rollup sequencer.
The important point is that a Based Rollup does not mean that all Rollup execution happens directly on Ethereum.
Instead, the key change concerns who determines transaction ordering.
Layer 2 networks process transactions outside Ethereum to improve scalability.
If every transaction had to be executed directly by every Ethereum validator, Ethereum would have limited capacity. Rollups solve part of this problem by processing many transactions offchain and then posting compressed data, commitments or proofs to Ethereum.
But someone still needs to decide the order of those transactions.
Suppose Alice submits transaction A and Bob submits transaction B.
The Rollup needs to determine whether the sequence is:
A → B
or:
B → A
Transaction ordering can affect balances, smart-contract interactions, liquidations, arbitrage opportunities and other outcomes.
A centralized Rollup sequencer can perform this task quickly and efficiently. It can provide users with rapid transaction confirmations and organize transactions before eventually submitting them to Ethereum.
However, this architecture introduces another trusted or operational component.
If a sequencer experiences downtime, users may temporarily be unable to transact normally. Depending on the Rollup’s design, a centralized sequencer can also have significant control over transaction ordering and potentially extract MEV.
Based Rollups attempt to address part of this issue by relying on Ethereum’s existing block-production infrastructure.
The basic idea can be simplified into several steps.
First, users submit transactions intended for the Rollup.
Instead of sending all of them to a dedicated Rollup sequencer, the transactions can be made available to Ethereum block proposers.
Ethereum’s proposer then constructs an Ethereum block that includes the relevant Rollup transactions.
The Rollup derives its transaction ordering from the Ethereum block.
Afterward, Rollup nodes can execute those transactions and update the Layer 2 state. The resulting state data or commitments can then be processed according to the Rollup’s settlement mechanism.
This creates a close relationship between Ethereum block production and Rollup sequencing.
A simplified architecture looks like this:
Users → Ethereum block builders/proposers → Ethereum blocks → Based Rollup sequencing → Rollup execution
This is different from a conventional architecture:
Users → Rollup sequencer → Rollup execution → Ethereum settlement
The distinction is subtle but important.
In the traditional model, Ethereum provides the base layer while the Rollup maintains a separate sequencing mechanism.
In a Based Rollup, Ethereum becomes part of the sequencing mechanism itself.
The two architectures have different design trade-offs.
| Feature | Centralized Rollup Sequencer | Based Rollup |
|---|---|---|
| Sequencing | Rollup operator | Ethereum block proposers |
| Sequencer decentralization | Depends on operator design | Inherits Ethereum’s proposer set |
| Transaction latency | Can be very low | Constrained by Ethereum block production |
| Ethereum integration | Settlement-focused | Sequencing + settlement |
| MEV management | Rollup-specific | Closely connected to Ethereum’s MEV ecosystem |
| Sequencer revenue | Usually captured by Rollup operator | Can shift toward Ethereum ecosystem |
| Infrastructure | Dedicated sequencer required | Uses Ethereum block-production infrastructure |
This comparison does not mean that one model is universally superior.
Centralized sequencers can offer fast confirmations and greater control over transaction ordering. They can also make it easier for developers to implement specialized sequencing policies.
Based Rollups sacrifice some of that flexibility in exchange for closer integration with Ethereum.
The appropriate architecture depends on the requirements of the Rollup.
One of the most obvious benefits is that the Rollup does not need to rely on a single sequencing operator.
Ethereum already has a large validator ecosystem responsible for proposing blocks. By using Ethereum’s block-production process, a Based Rollup can inherit part of that decentralized infrastructure.
This can reduce the operational dependence on a separate centralized sequencer.
However, “inheriting Ethereum’s security” should not be interpreted as meaning that every aspect of the Rollup automatically has identical security properties to Ethereum. The Rollup still has its own execution, proof and smart-contract assumptions.
Based Rollups can also improve composability between Ethereum and Layer 2 transactions.
Because Rollup sequencing is tied closely to Ethereum blocks, transactions on Ethereum and the Rollup can potentially be coordinated within the same block-production environment.
This is particularly interesting for applications that depend on interactions between L1 and L2.
For example, imagine a decentralized exchange on Ethereum and another application on a Based Rollup. If their transaction ordering can be coordinated more closely, certain cross-layer interactions may become easier to design.
This could become increasingly important as Ethereum develops a larger ecosystem of specialized Rollups.
Operating a centralized sequencer requires infrastructure, monitoring, failover mechanisms and operational management.
A Based Rollup can potentially reduce some of this burden by using Ethereum’s existing block-production process.
This does not eliminate all infrastructure requirements, but it changes where sequencing responsibility resides.
Based Rollups are closely connected to Ethereum’s consensus and block-building ecosystem.
This can create stronger alignment between the interests of the Rollup and the underlying Layer 1.
In particular, Ethereum’s proposer-builder separation and MEV infrastructure can become relevant to Rollup sequencing.
This creates an opportunity for Rollup transaction ordering to become part of a broader Ethereum block-building market rather than operating as an isolated sequencing system.
Based Rollups also introduce meaningful trade-offs.
A centralized sequencer can provide rapid soft confirmations to users.
Based sequencing depends more closely on Ethereum’s block-production process, which can make it harder to provide the same type of instant confirmation experience.
For applications where users expect extremely fast execution, this can be an important consideration.
A centralized sequencer gives the Rollup operator considerable control over transaction ordering.
That can be useful for implementing application-specific policies or specialized execution environments.
Based Rollups reduce this flexibility because sequencing is integrated with Ethereum’s block-production mechanism.
MEV is another major issue.
Transaction ordering can create opportunities for arbitrage, liquidations and other forms of value extraction.
With a centralized sequencer, the Rollup operator may capture much of this value.
With Based Rollups, some of the MEV associated with Rollup transactions can instead flow through Ethereum’s block-building ecosystem.
This raises an important economic question: who captures the value generated by Layer 2 transaction ordering?
A Based Rollup may provide stronger decentralization while potentially changing the revenue relationship between Ethereum and the Rollup.
Sequencer revenue is an important source of income for many Rollup ecosystems.
If sequencing is delegated to Ethereum’s validators, Rollups may give up some of that revenue.
That means Based Rollups need to consider how the ecosystem itself captures value.
A technically decentralized architecture still needs an economically sustainable model for developers, infrastructure providers and applications.
Ethereum’s scaling strategy has increasingly focused on Layer 2 networks.
Instead of trying to execute every transaction directly on the Ethereum mainnet, Ethereum can serve as a settlement and data layer for a broader ecosystem of Rollups.
This creates another challenge: how should dozens or hundreds of Rollups coordinate with Ethereum?
If every Rollup maintains its own centralized sequencer, the Ethereum ecosystem could become fragmented across multiple sequencing environments.
Each Rollup might have different transaction ordering, different MEV markets and different operational assumptions.
Based Rollups offer one possible alternative.
By making Ethereum the sequencing layer, multiple Rollups could potentially share a common block-production environment.
This could strengthen interoperability between Rollups while making Ethereum more central to the architecture of Layer 2 scaling.
However, Based Rollups are not the only possible solution.
Other approaches include decentralized sequencer networks, shared sequencing systems and application-specific sequencing mechanisms.
The broader trend is therefore not simply about replacing centralized sequencers. It is about exploring different ways to balance scalability, decentralization, latency, MEV and economic incentives.
Based Rollups represent one particular point in that design space.
A Based Rollup is a Layer 2 Rollup whose transaction sequencing is driven by Ethereum’s block-production process rather than by an independent centralized Rollup sequencer.
Not necessarily. The main distinction is sequencing. Rollup transactions can still be executed offchain, while Ethereum’s block-production process determines their ordering.
They can reduce reliance on a separate centralized sequencer by using Ethereum’s proposer set. However, the overall decentralization and security of a Rollup also depend on its execution, proof system, smart contracts and other infrastructure.
Many Rollups use their own sequencer to order transactions. A Based Rollup instead derives sequencing from Ethereum’s Layer 1 block production.
No. MEV does not disappear. Instead, the way MEV is generated, managed and distributed can change because Rollup sequencing becomes more closely integrated with Ethereum’s block-building ecosystem.
They offer a way to integrate Layer 2 sequencing more closely with Ethereum. This could potentially improve sequencing decentralization and cross-layer composability while reducing the need for independent sequencing infrastructure.
* The information is not intended to be and does not constitute financial advice or any other recommendation of any sort offered or endorsed by Gate.
* This article may not be reproduced, transmitted or copied without referencing Gate. Contravention is an infringement of Copyright Act and may be subject to legal action.





