Lab: free tools · size first · stock scanner · crypto scanner · journal

Layer 2

Sequencer

A sequencer is a centralised or semi-centralised component in Layer 2 rollup systems that receives, orders and batches user transactions before submitting them to the Layer 1 blockchain. It allows high throughput and low latency at the cost of a centralised ordering point that could, in theory, censor or front-run transactions.

A sequencer is the component of a rollup that receives transactions, decides their order and publishes them in batches. It provides fast confirmations, often within a second, before data reaches Ethereum. Because most sequencers are run by a single operator today, they can censor or go offline. Rollups usually offer a slower path to force transactions through Ethereum if that happens.

What the sequencer does

Users send rollup transactions to the sequencer, which orders them, executes them and returns a near-instant confirmation that they are included. That confirmation is the operator's promise, often called a soft confirmation. The stronger guarantee comes when the sequencer posts the batch to Ethereum, and on optimistic rollups withdrawals to Ethereum also wait out a challenge period.

Why centralization matters

Most large rollups launched with a single sequencer run by the team or its foundation. That is simple and fast, and it creates three problems:

  • Downtime: if the sequencer stops, the rollup stops producing blocks. Users cannot trade or move collateral, which matters most in volatile markets. Several major rollups have had sequencer outages.
  • Censorship: a single operator could refuse to include certain transactions.
  • Ordering power: whoever orders transactions controls MEV on the rollup. Most sequencers today use first-come-first-served ordering or priority fees, and users have to trust that policy.

Escape hatches

Well-designed rollups let users submit transactions directly to a contract on Ethereum and force the rollup to include them after a delay, often hours. That protects against lasting censorship, not against short outages. Check whether the rollup you use has this path and whether it is enabled. Risk trackers such as L2BEAT rate rollups on exactly these points.

Decentralizing the sequencer

Several approaches are under way: decentralized sequencer sets that rotate the role, shared sequencers that serve several rollups at once, and based sequencing, where Ethereum's own block proposers order rollup transactions. Preconfirmations aim to keep fast confirmations once ordering is spread out. Each design gives up some speed or simplicity for less trust.

For traders the practical points are short: know whether your rollup has a forced-inclusion path, do not park collateral where an outage could trap it during a crash, and treat an instant confirmation as strong but not final.