Sequencer

What is a Sequencer, and how does it differ from the common assumption that "a Rollup is inherently decentralized"?

Many people hear that a rollup inherits main-chain security and intuitively conclude the rollup as a whole is decentralized — but this reasoning overlooks a key distinction: a rollup's security (whether transaction execution results are correct) and a rollup's liveness and censorship-resistance (whether transactions can be included promptly and fairly) are two different things, and the sequencer is responsible for the latter.

Even if a rollup's proof system (fraud proofs or validity proofs) is fully decentralized and independently verifiable by anyone, as long as the sequencer itself is controlled by a single entity, that entity still holds meaningful real-world power — it can decide the order in which transactions are included (thereby affecting how MEV gets distributed), selectively delay or even refuse to include specific transactions, and potentially cause the entire chain to temporarily halt due to its own infrastructure failures. Understanding that "proof system decentralization" and "sequencer decentralization" are two separate progress tracks is key to correctly assessing a rollup's actual degree of decentralization.

Why has Sequencer operation become centralized — is this a design flaw or a staged choice?

Having a single entity operate the sequencer was a relatively pragmatic architectural choice in rollups' early development: the sequencer needs extremely high performance and stability to deliver the instant soft-confirmation experience users expect, and designing a truly decentralized sequencing mechanism that can maintain that performance level is a complex distributed-systems engineering problem — requiring solutions to a series of challenges, including how nodes reach consensus on transaction ordering, how to prevent Sybil attacks among sequencers, and how to design fair incentive mechanisms, all of which take time to refine.

This also means sequencer centralization is, for most teams, positioned as a staged engineering tradeoff rather than a deliberately chosen permanent architecture — several major rollups have already published public roadmaps toward decentralized sequencing, though the transition has taken longer than initially expected. Industry consensus generally estimates that major rollups won't see genuine large-scale production adoption of decentralized sequencing mechanisms until late 2026 to 2027.

What can a Sequencer actually do and not do? What real incidents have occurred?

A sequencer's power is mainly concentrated in two things: transaction ordering and inclusion. It can decide the order in which multiple transactions in the same Block get executed (directly affecting how MEV revenue like Arbitrage opportunities gets distributed), it can selectively censor by refusing to include transactions from specific addresses or of specific types, and it can cause the entire chain's liveness to temporarily stall due to operational problems. But a sequencer cannot steal user assets — regardless of whether the Rollup uses fraud proofs or validity proofs, its proof system independently verifies whether state transitions are correct, meaning a misbehaving sequencer can at most delay or censor transactions, not get an invalid state transition to pass verification.

Real incidents include: Arbitrum's sequencer stalled in December 2023 due to a surge in traffic, causing a multi-hour service outage; Linea suffered an outage incident in June 2024; Base also experienced a service disruption in February 2025. What these incidents share is that they caused delayed or temporarily unavailable transactions for users, but none resulted in stolen user assets or incorrectly altered state — confirming the technical distinction that "sequencer failure affects liveness, not asset security." Current leading decentralized sequencing approaches include shared sequencer networks (such as Espresso Systems' Mainnet 0, which uses a Byzantine Fault Tolerant consensus protocol called HotShot, letting multiple rollups share the same decentralized sequencing infrastructure), and some rollups planning to adopt a "based rollup" model, letting Ethereum mainnet's own validators handle ordering directly.

What does a Sequencer mean for me, and what should I watch for?

If you're using a Rollup for routine operations, sequencer centralization usually doesn't directly affect you in practice — but if your use case involves needing censorship resistance (say, your region could be denied service by a particular sequencer due to regulatory factors), or requires transactions to be handled fairly and promptly during high-traffic periods, understanding who currently operates that rollup's sequencer (whether it's team-run or has already adopted some form of decentralized mechanism) becomes important.

For larger transactions, or institutional-grade applications built on a rollup (involving real-world asset Tokenization or Stablecoin reserve management, for instance), the liveness risk that sequencer centralization introduces is, in a sense, equivalent to trusting a single operator not to go down or censor. If this kind of risk exceeds what you're willing to accept, it's worth prioritizing rollups that have already adopted shared sequencing or decentralized ordering mechanisms, or at least confirming whether the rollup has a public, verifiable decentralization roadmap and timeline.