# Rollup sequencers: who puts transactions in order? A rollup sequencer selects and orders transactions into the rollup’s execution history. Its quick acknowledgment can arrive before data or proofs reach Ethereum. Sequencing, verification and settlement are separate roles, and outage or censorship protections depend on the deployed rollup. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) Canonical: https://degreesofsatoshi.com/encyclopedia/rollup-sequencers/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T15:10:23.134Z AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Primary role:** Choose and order rollup transactions ([Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md)) - **Early acknowledgment:** Can precede Ethereum publication and settlement ([Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md)) - **Escape path:** Forced inclusion and exit mechanisms vary by implementation ([Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md)) ## The sequencer decides what executes next Transaction order matters because each operation sees the state left by earlier operations. Rollups use a sequencing process to assemble this ordered history. Some deployments place that role in one operator’s hands, while others design additional operators or different selection mechanisms. The sequencer is not automatically the same component as a prover, challenger or Ethereum validator. One organization may operate several components, but their responsibilities differ. Ordering produces a proposed history; the settlement rules determine how it is accepted. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) ## Example: two buyers and one remaining ticket Imagine a contract has one ticket remaining and two valid purchase requests arrive. If the sequencer places Maya’s transaction first, her purchase can consume the ticket and Leo’s later attempt may revert. Reverse the order and the result can reverse too. Both ordered executions could follow the contract’s rules. That is why a proof of valid execution does not establish that ordering was fair. A sequencer’s ability to delay, omit or reorder transactions is a separate question from its ability to invent invalid balances. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) ## A fast response is useful, but ask what it commits to A wallet may show the result shortly after a sequencer accepts a transaction. The relevant data may be published to Ethereum later, and a validity proof or dispute process can introduce further stages. These events should not all be compressed into one undefined word: confirmed. For a concrete transaction, identify the stage the interface reports and the assumptions behind it. An acknowledgment from one operator is different evidence from a state update accepted by the settlement contract and included in finalized Ethereum history. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md); [Data availability](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/data-availability/index.md) ## Outages test the paths around the operator A single sequencer can be a point of failure for prompt service even when it cannot make the settlement contract accept an invalid state. If it stops, users need to know whether another operator can continue, whether they can force inclusion through Ethereum, and how they obtain the data required to act. These protections are deployment-specific. A design document’s proposed escape mechanism does not prove that a particular production system exposes it today or that it is inexpensive. Check the actual contracts, permissions and documented conditions before relying on an emergency route. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) ## Questions ### Can a sequencer choose transaction order? Yes, ordering is its core role in the designs described here. The deployed protocol determines any constraints, competing operators or alternative inclusion paths. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) ### Does a centralized sequencer make every balance untrustworthy? That does not follow. State validity can be enforced separately by proofs or challenges. Centralization still affects ordering, censorship and availability of prompt service. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) ### Can I always bypass a failed sequencer? Do not assume so. The route, waiting conditions, permissions and data requirements depend on the actual deployment. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) ## Claims and scope ### rollup-sequencers-quick-answer A rollup sequencer selects and orders transactions into the rollup’s execution history. Its quick acknowledgment can arrive before data or proofs reach Ethereum. Sequencing, verification and settlement are separate roles, and outage or censorship protections depend on the deployed rollup. Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### rollup-sequencers-fact-primary-role Primary role: Choose and order rollup transactions Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### rollup-sequencers-fact-early-acknowledgment Early acknowledgment: Can precede Ethereum publication and settlement Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### rollup-sequencers-fact-escape-path Escape path: Forced inclusion and exit mechanisms vary by implementation Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ## Sources - [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md) — ethereum.org contributors. Supports challenge periods, dispute verification, sequencer ordering and withdrawal distinctions; concrete timings depend on the implementation. Locator: Fraud proving; censorship resistance; exiting the rollup. Retrieved: 2026-10-02T14:35:47.579696+00:00. - [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) — ethereum.org contributors. Supports validity proofs and public rollup data; no claim that every withdrawal is instant or that every ZK system is private. Locator: Data availability; validity proofs; withdrawals; EVM compatibility. Retrieved: 2026-10-02T14:35:47.579728+00:00. - [Data availability](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/data-availability/index.md) — ethereum.org contributors. Supports why a hash is not sufficient to reconstruct data and why availability differs from permanent historical storage. Locator: Data availability problem; rollups; availability versus retrievability. Retrieved: 2026-10-02T14:35:47.112785+00:00. ## Revision history - 2026-10-02: First publication after primary-source research and independent automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Rollup sequencers: who puts transactions in order?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/rollup-sequencers/