Rollup Sequencers

What the Sequencer Actually Does

You send a transaction to the rollup's endpoint. The sequencer picks an order, gives you a near instant confirmation, then compresses the batch and posts it to a layer one contract. That posting is the moment the ordering becomes canonical, because the contract on the main chain, not the sequencer, is what defines the chain.

Holding both jobs gives one operator two powers. It can stop producing batches, which is a liveness failure, and it can decline to include a particular user, which is censorship. For an industry that talks a great deal about decentralisation, this is a slightly awkward single computer.

The Second Door

Rollups answer both problems the same way: a permissionless path to the same contract that does not need the sequencer's cooperation or goodwill.

On the OP Stack a user submits directly to the portal contract on layer one, and the documentation describes a rolling twelve hour sequencing window within which that transaction must be derived into the layer two chain. Arbitrum asks for two steps instead of one: the message goes into a delayed inbox on layer one, and after the delay you send a second transaction calling force inclusion yourself.

Inclusion Is Not Withdrawal

Here is where cheerful summaries go astray. Getting a transaction included is not the same as getting your money out. A withdrawal still needs a state root proposed and the challenge period served, which is measured in days rather than hours.

L2BEAT's stage framework tracks exactly these properties, including whether anyone besides the operator can propose state roots and how long an exit window must stay open. It is the practical place to check what a chain actually guarantees, as opposed to what its launch announcement implied.

What a Sequencer Cannot Do

The common fear is that a centralised sequencer could run off with the funds or lock users out forever. It cannot. The worst it can impose on a determined user is delay, plus the gas to walk around it.

What it can do freely is reorder transactions and trade ahead of them, and it can make the escape route expensive at precisely the wrong moment, since forced inclusion matters most during a crisis and that is exactly when main chain fees are at their least charming.

The practical rule: before parking a large balance on a rollup, find out whether it supports forced inclusion, how long the window is, and whether anyone other than the operator can propose state roots. Those three answers describe your real exit, and they vary a lot more between chains than the marketing does.