Decentralized Sequencing
Web3 / layer2 solutions
An approach to Layer 2 transaction ordering that distributes the role of sequencing among multiple parties rather than concentrating it in a single centralized operator. Most rollups in their early production stages rely on a single sequencer, typically controlled by the development team, which collects user transactions, orders them into batches, and submits them to the base layer. This centralized structure creates single points of failure, enables transaction censorship, and gives the sequencer opportunities to extract value by reordering transactions ahead of users (a form of MEV). Decentralized sequencing distributes this function through mechanisms including sequencer auctions, rotating leadership among a permissioned set, full permissionless participation, or by delegating sequencing entirely to the parent chain's validators. The latter approach, used by based rollups, results in the most censorship-resistant sequencing but trades off some throughput and latency advantages that a dedicated sequencer provides. Example: Taiko implemented a based rollup architecture when it launched its mainnet in May 2024, making it one of the first production rollups to use Ethereum validators directly as its sequencers. This means Taiko inherits Ethereum's censorship resistance at the sequencing layer by design, without a separate sequencer committee or auction mechanism. Why it matters for Web3: Centralized sequencers are arguably the most significant remaining centralization point in today's rollup ecosystem. Arbitrum, Optimism, Base, and most major L2s have acknowledged this and published roadmaps to decentralize sequencing, but execution has been slow due to complexity and performance tradeoffs. Decentralized sequencing is widely viewed as a prerequisite for rollups to achieve meaningful decentralization beyond their cryptographic proving mechanisms.
Explore the full Web3 Glossary — 2,000+ expert-curated definitions. Need guidance? Talk to our consultants.