A Sequencer is a component of many Layer 2 blockchain systems that receives user transactions, determines their order, executes or coordinates their processing, and groups them into batches that can later be submitted to a settlement or data availability layer. In most rollups, the sequencer provides the fast transaction experience users see before the corresponding Layer 2 activity is ultimately anchored to Layer 1.
Sequencers exist because rollups separate transaction execution from the base blockchain. Instead of sending every user transaction directly through Ethereum’s Layer 1 mempool and asking Ethereum validators to order it, users can submit transactions to Layer 2 infrastructure. The sequencer can process them much faster and at lower cost, while the rollup later publishes the required commitments, proofs, and data according to its design.
This makes sequencing one of the most important operational functions in a rollup. Transaction ordering determines which transaction is processed first when several users interact with the same application, which can influence arbitrage opportunities, liquidations, token trades, and other time-sensitive actions.
Many production rollups historically launched with centralised sequencers because this architecture provides high performance and simplifies development. The longer-term challenge is to preserve these performance advantages while reducing censorship, downtime, and transaction-ordering risks.
Where the Sequencer Sits in a Rollup
A rollup can process transactions outside Ethereum while using Ethereum for functions such as settlement and data availability. The sequencer sits close to the beginning of this pipeline.
When a user sends a Layer 2 transaction, it is generally not immediately included in an Ethereum block. It first reaches the rollup’s transaction-processing infrastructure. The sequencer determines its position relative to other transactions and can provide an early confirmation that the transaction has been accepted into the Layer 2 ordering.
The process can be simplified into the following sequence:
- A user signs and submits a Layer 2 transaction.
- The transaction reaches the rollup sequencer.
- The sequencer validates basic transaction requirements and determines an ordering.
- Ordered transactions are processed according to the Layer 2 execution rules.
- Transactions are grouped into batches or blocks.
- Required data and state commitments are submitted through the rollup’s Layer 1 and data availability mechanisms.
- The rollup reaches stronger settlement or finality guarantees according to its proof system and underlying blockchain.
The sequencer is therefore not the ultimate source of Ethereum finality. A fast response from a sequencer and final settlement on Ethereum represent different stages of transaction confirmation.
This distinction matters for applications handling large values. A transaction may appear almost immediately in a Layer 2 interface while its corresponding batch has not yet received the strongest guarantees available from the settlement layer.
Ordering Is the Sequencer’s Core Power
Sequencers are sometimes described simply as servers that bundle transactions, but transaction ordering is the more economically important function.
Suppose two traders attempt to buy the same token immediately after a price change. The transaction processed first may receive a better execution price. Similar ordering effects occur with liquidations, NFT purchases, arbitrage, collateral adjustments, and many other on-chain actions.
On Ethereum Layer 1, transaction ordering emerges through the block-building and block-proposal process. In a rollup with a centralised sequencer, much of the immediate ordering authority is concentrated in the sequencer.
This creates opportunities related to Maximal Extractable Value, or MEV. An entity with control over ordering may be able to identify profitable transaction sequences, place transactions before or after user transactions, or auction ordering rights to other participants.
Not all sequencing policies are based simply on the order in which transactions arrive. A system may incorporate fees, auctions, priority rules, encrypted transaction mechanisms, or other policies.
The sequencing design therefore influences more than speed. It can affect market fairness, MEV distribution, censorship resistance, and the economics of applications operating on the Layer 2.
Sequencer, Proposer, Validator and Batcher
Several blockchain roles can appear similar because they all interact with blocks or transaction batches. Their responsibilities, however, are different.
| Role | Main Function | Where It Commonly Operates | Controls Transaction Ordering? | Provides Final Settlement? |
| Sequencer | Receives and orders L2 transactions | Layer 2 | Usually yes | No |
| Ethereum block proposer | Proposes an L1 block | Ethereum Layer 1 | Participates in L1 block production | Through Ethereum consensus |
| Rollup batcher | Publishes L2 transaction data or batches | Between L2 and L1 | Not necessarily | No |
| Validator / verifier | Checks protocol rules, proofs, or state transitions | Depends on architecture | Usually not its primary role | Depends on system |
| Prover | Generates validity proofs | ZK-rollup infrastructure | No | No |
Implementations can combine several of these functions in one piece of infrastructure. For example, the entity operating a rollup sequencer may also operate batching infrastructure. That does not make the underlying concepts identical.
A prover in a ZK-rollup has a particularly different responsibility. It generates cryptographic evidence that a state transition followed the relevant rules. It does not inherently determine the original transaction order.
Separating these concepts is important when evaluating decentralisation. A rollup may decentralise proving while retaining a centralised sequencer, or decentralise sequencing while other operational components remain controlled by a smaller group.
Why Many Rollups Use Centralised Sequencers
Centralised sequencers became common because they solve several practical engineering problems.
A single sequencer can establish an ordering quickly without running a separate distributed consensus protocol among many sequencing nodes. This can produce low latency and predictable block production, both of which are valuable for applications that need responsive transaction execution.
The architecture can also simplify rollup development. Teams can initially focus on execution, proving, bridges, data publication, and compatibility rather than simultaneously building a decentralised sequencer network.
Centralised sequencing does not necessarily mean that the operator can arbitrarily steal all assets in a properly designed rollup. The ultimate security properties depend on the rollup’s smart contracts, proof system, data availability, withdrawal mechanisms, and upgrade controls. A sequencer generally cannot make an invalid state transition valid simply by ordering transactions.
However, centralised control can still create significant risks.
A sequencer can potentially censor transactions by refusing to include them. It can experience an outage that temporarily interrupts normal Layer 2 processing. It may also have privileged visibility into incoming transactions and control their order.
For this reason, the distinction between safety and liveness is useful. A rollup can remain safe in the sense that invalid state transitions cannot be finalised while still experiencing a liveness failure because users cannot get transactions processed normally.
Censorship Resistance and Forced Transactions
One of the most important protections in a rollup architecture is the ability to operate when the normal sequencer is unavailable or refuses to process a user’s transaction.
Some rollups provide mechanisms through which users can submit transactions or messages through Layer 1 contracts. The exact implementation varies, but the general purpose is to prevent the sequencer from having permanent censorship power.
If a centralised sequencer ignores a transaction, an escape mechanism can allow the user to rely on Ethereum or another underlying blockchain to force progress under defined conditions.
This is an important difference between a centralised exchange and a rollup with meaningful Layer 1 escape mechanisms. A centralised exchange operator can control its internal database entirely. A rollup can be designed so users retain a route to the underlying settlement system even if the normal Layer 2 operator fails.
Relevant protections can include:
- forced transaction inclusion through Layer 1;
- independent withdrawal mechanisms;
- limits on how long the sequencer can delay transactions;
- publicly verifiable Layer 2 state commitments;
- accessible transaction data needed for state reconstruction;
- alternative processing modes during sequencer outages.
These mechanisms can be slower and more expensive than ordinary Layer 2 transactions because they interact with Layer 1. Their purpose is not to replace normal sequencing but to provide a fallback.
The strength of such mechanisms differs substantially between rollups. Evaluating a sequencer therefore requires examining what users can actually do if it disappears or becomes hostile.
Sequencers and MEV
MEV is one of the most important economic questions surrounding sequencing.
A sequencer sees a flow of transactions and determines their order. In financial applications, ordering can have measurable monetary value. Arbitrageurs may compete to correct price differences, liquidators may compete for positions eligible for liquidation, and traders may care about whether another transaction is inserted before theirs.
A poorly designed sequencing system can allow the operator or sophisticated searchers to capture value at users’ expense. Front-running and sandwich-style strategies are examples of ordering-related problems familiar from decentralised exchange trading.
Layer 2 systems can also experiment with sequencing designs that are difficult to introduce at the base layer. Possible approaches include encrypted mempools, transaction auctions, fair-ordering mechanisms, MEV redistribution, and specialised block-building markets.
There is no universally accepted solution. A strict first-come-first-served policy sounds simple but becomes difficult in geographically distributed networks because different nodes observe transactions at different times. Auctions can allocate ordering efficiently but may favour sophisticated participants. Encryption can reduce information leakage but adds cryptographic and operational complexity.
Sequencer decentralisation therefore involves more than replacing one server with several servers. The system needs rules determining how multiple participants agree on ordering and how economically valuable ordering rights are distributed.
Decentralised and Shared Sequencing
The centralisation of production rollup sequencers has encouraged development of decentralised sequencing systems.
One approach is to create a network of sequencers that reaches consensus over transaction ordering. Instead of trusting one operator for liveness and ordering, the rollup relies on a distributed protocol.
Another approach is shared sequencing. A common sequencer network can order transactions for multiple rollups rather than requiring every Layer 2 to operate an independent sequencing system.
Shared sequencing can provide an additional benefit for cross-rollup transactions. If the same sequencing infrastructure coordinates several rollups, it may become easier to provide atomic or tightly coordinated execution across them.
Based rollups take a different direction. Instead of establishing an independent sequencer network, they use Ethereum’s Layer 1 block production infrastructure for sequencing. This can inherit important decentralisation and liveness properties from Ethereum, although it introduces different latency, design, and economic considerations.
These models represent different answers to the same question: who should have the right to determine the next Layer 2 transaction order?
Sequencer Revenue and Layer 2 Economics
Sequencing can be economically valuable even without malicious MEV extraction.
Users pay Layer 2 transaction fees. Part of this revenue is needed to cover execution infrastructure and the cost of publishing data to the DA layer. If the total fees collected from users exceed these costs, the difference can contribute to the rollup operator’s revenue.
Batching creates economies of scale. Thousands of Layer 2 transactions can share the cost of publishing compressed data or commitments rather than each user paying for an independent Layer 1 transaction.
The sequencer can therefore occupy an important position in a rollup’s business model. This has implications for decentralisation because transferring sequencing to an external or distributed network can also redistribute revenue that previously went to the rollup operator.
MEV introduces another source of potential value. Depending on the design, this value might be captured by the sequencer, distributed among network participants, auctioned to block builders, returned partly to users, or handled through other mechanisms.
Sequencer design is consequently both a technical and economic decision.
Why Sequencers Matter for Layer 2 Decentralisation
Rollups can inherit important security properties from Ethereum while still operating centralised infrastructure at other layers. Sequencers are one of the clearest examples.
A centralised sequencer can provide an excellent user experience, with rapid confirmations and low transaction costs, while simultaneously creating a single point of failure for normal transaction processing. This does not make the rollup equivalent to a centralised database, but it does mean that its decentralisation cannot be evaluated solely by asking where settlement occurs.
The practical questions are more specific: who operates the sequencer, who can replace it, whether users can bypass it, how transactions are ordered, how outages are handled, and who receives sequencing revenue and MEV.
As Layer 2 networks mature, sequencing is increasingly becoming its own area of blockchain infrastructure. Decentralised sequencers, shared sequencing networks, based sequencing, preconfirmation systems, and new MEV mechanisms are all attempts to redesign this part of the rollup stack.
The sequencer ultimately determines the immediate ordering experience of a Layer 2 blockchain. Ethereum or another base layer may provide final settlement, but before transactions reach that stage, the sequencing mechanism decides how users’ actions are organised into the Layer 2 history. That makes it one of the most influential components in the performance, economics, and decentralisation of modern rollups.