A sequencer is the part of a rollup that receives user transactions, decides the order they’ll be processed in, and packages them into batches to post back to L1. It’s the component users’ transactions actually hit first when they interact with a rollup — the equivalent of a block producer, but for an L2 rather than for Ethereum itself.
On most live rollups today, the sequencer is run by a single operator, usually the team behind the rollup. That’s a deliberate, acknowledged tradeoff for speed and simplicity in a still-maturing technology, not an oversight — but it is real centralization.
Why it matters
A centralized sequencer is a single point of failure in two specific ways: it can go down, halting new transactions on the L2 until it recovers, and it can, in principle, reorder, delay, or censor specific transactions before they’re posted. Canonical bridge exits and fraud proof or validity proof mechanisms are what still let users leave even if a sequencer misbehaves — but the day-to-day experience of using the rollup depends on that one operator staying up and honest. Decentralized sequencing — multiple parties sharing or rotating the role — is an active area of work across the ecosystem, not yet the default.
Example
If a rollup’s sequencer goes offline, users typically can’t submit new L2 transactions until service resumes, even though their existing balances and the rollup’s state on L1 remain intact.
Related · Rollups
Not financial advice.