Sequencer

What Is a Sequencer?

A sequencer is the node (or set of nodes) in a rollup responsible for receiving user transactions, deciding the order in which they execute, and submitting the results to Layer 1 for verification and settlement. Think of it as the traffic controller for a rollup: every transaction passes through the sequencer before it becomes part of the chain's history.

The term "sequencer" emphasizes the ordering role. Because transaction order determines execution outcomes (who gets the trade, who gets liquidated, which state transitions are valid), the entity controlling that order wields significant power. This makes sequencer design one of the most consequential architectural decisions in any rollup.

Sequencers exist in both optimistic rollups (like Arbitrum and Optimism) and ZK rollups (like zkSync and Scroll). The core function is the same across both types: order transactions, execute them, and post data to L1. What differs is how the L1 verifies correctness: fraud proofs for optimistic rollups, validity proofs for ZK rollups.

How It Works

A sequencer's lifecycle follows a pipeline of distinct stages, from receiving raw transactions to achieving finality on the base layer.

Transaction Intake

Users submit transactions to the sequencer via RPC endpoints. These enter the sequencer's mempool, a holding area for pending transactions. Unlike Ethereum L1's public mempool, most rollup sequencer mempools are private: only the sequencer operator can see pending transactions.

Ordering and Execution

The sequencer determines execution order using a policy chosen by the rollup team. Common approaches include:

• First-come-first-served (FCFS): transactions are ordered by arrival time. Arbitrum historically used this model.
• Priority fee: users bid for ordering priority, similar to Ethereum L1's fee market. Optimism and Base use this approach.
• Auction-based: Arbitrum introduced Timeboost in 2025, where bidders pay for 60-second windows of priority access via an express lane.

After ordering, the sequencer executes transactions against the current L2 state and issues soft confirmations to users. These are near-instant acknowledgments (typically under 250 milliseconds on Arbitrum, around 2 seconds on Optimism) that the transaction will be included. Soft confirmations are fast because a single operator can commit to an ordering without coordinating with other parties.

Batching and Posting

The sequencer groups multiple L2 blocks into compressed batches and submits them to L1. Since Ethereum's Dencun upgrade in March 2024, rollups post batch data via EIP-4844 blobs, which are significantly cheaper than calldata. Batches are posted based on size thresholds or time intervals: Arbitrum typically posts every 1 to 10 minutes depending on load, while OP Stack chains target intervals of 1 to 6 hours.

Once the batch is accepted by the rollup's L1 settlement contract (after a 7-day challenge window for optimistic rollups, or upon validity proof verification for ZK rollups), the transactions achieve L1-level finality and can no longer be reversed by the sequencer.

Simplified Transaction Flow

User submits tx → Sequencer mempool → Ordering + execution
  → Soft confirmation (~250ms) → User sees "confirmed"

Background: Sequencer batches multiple blocks
  → Compresses data → Posts to L1 via blobs
  → L1 verification (fraud proof or validity proof)
  → Final settlement on base layer

The Centralization Problem

As of 2026, every major Ethereum rollup runs a single sequencer operated by the rollup's core team: Offchain Labs for Arbitrum, the Optimism Foundation for OP Mainnet, Coinbase for Base, Matter Labs for zkSync Era, and Consensys for Linea. This centralization creates three categories of risk.

Single Point of Failure

If the sequencer goes down, the rollup stops producing blocks. Real incidents include Arbitrum's roughly 3-hour outage in December 2023 (triggered by inscription volume overwhelming the sequencer) and Base's multiple outages in 2024, including back-to-back disruptions spanning over two hours. These events halted all user activity on the affected rollups.

Censorship Risk

A single operator can exclude specific transactions or addresses without any protocol-level check. While no major rollup has been caught arbitrarily censoring ordinary user transactions, the capability exists. Rollups mitigate this with forced inclusion mechanisms: users can submit transactions directly to the rollup's L1 inbox contract, bypassing the sequencer. Arbitrum enforces inclusion within roughly 24 hours; Optimism within roughly 12 hours. However, these delays make the escape hatch impractical for time-sensitive operations like DeFi trading or liquidations.

MEV Extraction

Because the sequencer controls transaction ordering and has a private mempool, it is uniquely positioned to extract MEV: inserting its own transactions ahead of users (front-running), sandwiching trades, or back-running profitable operations. The private mempool prevents external searchers from extracting MEV, but shifts all extraction capability to the sequencer operator itself.

Arbitrum's Timeboost auction was designed to internalize MEV revenue for the Arbitrum DAO. However, empirical analysis of over 11.5 million express lane transactions (April to July 2025) found that two entities won more than 90% of auctions, concentrating control rather than distributing it.

Decentralized Sequencer Proposals

The industry is pursuing several approaches to remove or distribute the sequencer's centralized power. For a comprehensive analysis, see the L2 sequencer decentralization research.

Shared Sequencers

A shared sequencer is an external network that provides ordering services to multiple rollups simultaneously. Rather than each rollup running its own sequencer, they delegate ordering to a decentralized sequencing layer.

• Espresso Systems launched its first mainnet in April 2025, using the HotShot BFT consensus protocol to provide permissionless sequencing confirmations in roughly 8 seconds across 20+ partner chains.
• Astria built a shared sequencer using Celestia for data availability but shut down in December 2025, illustrating the economic challenges of bootstrapping a shared sequencing network.
• Radius uses zero-knowledge encryption (Practical Verifiable Delay Encryption) to encrypt transactions until after ordering is finalized, preventing the sequencer from viewing transaction contents and extracting MEV.

Based Rollups

Based rollups eliminate the dedicated sequencer entirely by delegating transaction ordering to Ethereum L1 validators. This approach, proposed by Ethereum researcher Justin Drake in 2023, inherits the full decentralization and censorship resistance of Ethereum's validator set without introducing a new token or consensus protocol.

Taiko is the leading based rollup implementation, launching preconfirmations on Ethereum mainnet in August 2025 to achieve roughly 2-second confirmation times. The tradeoff: without preconfirmation infrastructure, based rollups are limited to Ethereum's 12-second block time, and sequencer revenue flows to L1 validators rather than the rollup team.

Self-Decentralization

Some rollups plan to decentralize their own sequencer sets through multi-party sequencing with shared revenue. This approach preserves the rollup's sovereignty over ordering policy while distributing trust across multiple operators.

Sequencers vs. Other L2 Approaches

Not every Layer 2 design requires a sequencer. The need arises specifically from rollups' architecture: they maintain a shared global state for arbitrary smart contract execution, so someone must determine the canonical order of all state transitions.

Spark, for example, uses a statechain-based model that avoids the need for a sequencer entirely. Instead of routing all transactions through a centralized ordering entity, Spark facilitates direct transfers of virtual UTXOs between participants. This eliminates the MEV and censorship concerns inherent to sequencer architectures while preserving self-custody guarantees. For a deeper comparison, see the rollup vs. state channel scaling tradeoffs research.

Use Cases

Sequencers are essential infrastructure for any rollup-based application. Their role enables several categories of use case that depend on fast, ordered execution.

• DeFi protocols on rollups: decentralized exchanges, lending platforms, and derivatives markets rely on the sequencer to process trades and liquidations in a deterministic order within milliseconds.
• High-throughput applications: gaming, social networks, and NFT marketplaces use rollups to achieve transaction throughput far beyond L1 capacity, with the sequencer providing the responsiveness users expect.
• Cross-rollup composability: shared sequencers enable atomic transactions across multiple rollups by ensuring coordinated ordering, unlocking interoperability between isolated L2 ecosystems.
• MEV mitigation: encrypted mempools and fair ordering protocols at the sequencer level can protect users from front-running and sandwich attacks that plague L1 trading.

Risks and Considerations

Trust Assumptions

Users of a centralized sequencer trust that the operator is honestly ordering transactions, not extracting MEV, and will remain operational. This is a social and legal trust assumption, not a cryptographic one. The forced inclusion mechanism provides a censorship backstop but with delays measured in hours, not seconds. For a broader analysis of trust models across Bitcoin L2s, see the L2 trust model comparison.

Liveness Dependency

A rollup's liveness depends on its sequencer. If the sequencer stops producing blocks, users cannot transact on the L2 until either the sequencer recovers or they use the forced inclusion path through L1 (which requires paying L1 gas fees and waiting for the inclusion window).

Decentralization Tradeoffs

Decentralizing the sequencer introduces its own challenges. Multi-party consensus adds latency (reducing the speed advantage over L1), complicates MEV policy, and requires economic incentives to attract operators. Based rollups trade sequencer revenue for decentralization. Shared sequencers introduce a new dependency and potential failure point. No approach has yet achieved the combination of speed, decentralization, and economic sustainability that the ecosystem is seeking.

Regulatory Uncertainty

A centralized sequencer operator that controls transaction ordering and can censor users may face regulatory scrutiny as a financial intermediary in some jurisdictions. The legal classification of sequencer operators remains an open question as regulators develop frameworks for Layer 2 infrastructure.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.