Sequencers

What are Sequencers?

Sequencers are the entities responsible for ordering transactions and producing blocks on Layer 2 networks, particularly rollups. When users submit transactions to a rollup, they don’t go directly to the base layer blockchain. Instead, the sequencer receives these transactions, determines their order, executes them to update the rollup state, and eventually submits the results to the underlying chain. This role makes sequencers the heartbeat of rollup operation, controlling the rhythm at which transactions flow through the system.

The sequencer’s ordering power is fundamental to how rollups function. Unlike Layer 1 blockchains where transaction ordering emerges from decentralized consensus among many validators, rollup sequencers typically have unilateral control over which transactions appear in which order. This centralization enables dramatically faster transaction confirmations - users can receive “soft confirmations” from the sequencer in milliseconds rather than waiting for base layer finality. However, this speed comes with trust assumptions that distinguish rollups from the fully decentralized systems they inherit security from.

Transaction ordering directly impacts user experience and economics. The sequencer determines not just when transactions confirm but their relative position, which affects execution prices on decentralized exchanges and opportunities for MEV extraction. A sequencer could theoretically front-run user transactions, censor specific addresses, or manipulate ordering for profit. Understanding sequencers is essential for anyone using rollups because the trust model differs fundamentally from interacting with base layer blockchains.

How Sequencers Work

The sequencer’s workflow begins when users submit transactions, either directly to the sequencer’s endpoint or through RPC providers that relay to it. The sequencer maintains a queue of pending transactions, selecting which to include in the next batch based on criteria like gas prices, account nonce ordering, and any protocol-specific rules. After selecting transactions, the sequencer executes them sequentially, updating the rollup’s state with each operation - modifying account balances, smart contract storage, and all other state changes that result from execution.

Batching and compression represent crucial aspects of sequencer operation that directly affect rollup economics. Rather than posting each transaction individually to the base layer, sequencers aggregate many transactions into batches that get submitted together. These batches undergo compression to minimize the data footprint since base layer data costs typically dominate rollup operational expenses. Advanced compression techniques can reduce transaction data by 80% or more, spreading fixed posting costs across more transactions and lowering per-transaction fees for users.

The final step involves submitting batch data and state commitments to the base layer. For optimistic rollups, the sequencer posts compressed transaction data along with a new state root representing the rollup state after batch execution. For ZK rollups, this submission also includes or references validity proofs demonstrating correct execution. Once data reaches the base layer, it becomes available for anyone to verify, and the security guarantees of the underlying chain protect users. The gap between soft confirmation from the sequencer and hard finality on the base layer creates different levels of transaction assurance that applications must navigate.

Centralized Sequencers

Today’s major rollups operate with centralized sequencers controlled by their development teams. Arbitrum’s sequencer is run by Offchain Labs, Optimism’s by the Optimism Foundation, and similar arrangements exist across most production rollups. This centralization emerged pragmatically - building a working rollup is complex enough without simultaneously solving decentralized sequencing, and centralized operation allowed teams to ship functional systems faster. The responsible operators have committed to fair ordering policies and have not engaged in malicious behavior, but the trust requirement remains.

The trust assumptions of centralized sequencing merit careful consideration. Users must trust that the sequencer will include their transactions in a reasonable timeframe without censorship. They must trust that the sequencer won’t exploit its ordering power to extract MEV at their expense. They must trust the sequencer’s infrastructure remains available, as downtime means users cannot transact. These trust assumptions differ qualitatively from using Ethereum or other decentralized base layers, where no single party can unilaterally censor or reorder transactions.

However, centralized sequencing doesn’t compromise the fundamental security guarantees that make rollups valuable. Even if a sequencer acts maliciously, users can always force-include transactions through the base layer after a delay period, ensuring censorship resistance as an escape hatch. The sequencer cannot steal funds or post invalid state transitions because these would be caught by fraud proofs or validity proofs depending on the rollup type. Centralization affects liveness and MEV exposure but not the core security property that users can eventually recover their assets through the base layer regardless of sequencer behavior.

Decentralizing Sequencers

Shared sequencing networks represent one approach to reducing sequencer centralization while enabling new capabilities. Rather than each rollup operating its own sequencer, multiple rollups could delegate ordering to a common decentralized network. Projects like Espresso, Astria, and Radius are building these shared sequencer layers, where a set of validators reaches consensus on transaction ordering across multiple participating rollups. This provides censorship resistance through decentralization while potentially enabling atomic transactions spanning multiple rollups that share the same sequencer.

Based rollups take a more radical approach by eliminating dedicated sequencers entirely. In a based rollup design, the base layer’s own proposers handle transaction ordering. Layer 1 validators directly include rollup transactions, inheriting all the decentralization and censorship resistance properties of the underlying chain. This approach has compelling simplicity and security properties but involves trade-offs around latency and MEV dynamics. Because ordering happens at Layer 1 block times rather than through a dedicated fast sequencer, based rollups may offer slower soft confirmations than centralized alternatives.

The path toward sequencer decentralization involves navigating complex trade-offs between performance, security, and complexity. Centralized sequencers offer sub-second confirmations and simpler operation but require trust. Shared sequencers distribute trust while enabling cross-rollup composability but introduce coordination overhead and new infrastructure dependencies. Based sequencing maximizes decentralization but potentially sacrifices speed. Different rollups may choose different approaches based on their priorities, and the optimal design may continue evolving as the ecosystem matures and new technical solutions emerge.

Sequencer Economics

Sequencer revenue derives primarily from transaction fees paid by users, similar to how validators earn on base layer blockchains. Users pay gas fees for their transactions, and the sequencer collects these fees as compensation for providing ordering and execution services. In rollup ecosystems with native tokens, sequencers may also earn token rewards as additional incentive. The fee levels that sequencers charge must balance user affordability against operational sustainability - too high and users migrate to competitors, too low and the sequencer cannot cover costs.

Operational costs for sequencers center on base layer data publication, which often represents the dominant expense. Every batch of transactions must be posted to the underlying chain, incurring data costs that scale with the volume of transaction data. Ethereum’s EIP-4844 upgrade introduced blob transactions specifically to reduce these costs for rollups, and further data availability improvements promise additional savings. Sequencers also bear infrastructure costs for running execution environments, maintaining RPC endpoints, and ensuring high availability. The margin between fee revenue and these costs determines sequencer profitability.

MEV considerations add complexity to sequencer economics. The entity controlling transaction ordering can potentially extract value through strategies like frontrunning or sandwich attacks, similar to how block builders operate on Layer 1. Current centralized sequencers have generally committed not to extract MEV, but the temptation exists and verification is difficult. As sequencing decentralizes, MEV dynamics will evolve - shared sequencers and based rollups introduce different MEV exposure profiles. Some proposals aim to return MEV to users or the protocol rather than sequencers, while others focus on encrypted mempools that prevent ordering exploitation entirely. The long-term economic model for sequencers will likely involve some combination of transaction fees, potential MEV, and protocol incentives balanced against operational costs.