What cross-rollup sequencing actually is

Cross-rollup sequencing is the process of ordering transactions across multiple Layer-2 rollups simultaneously using shared infrastructure. Instead of each rollup relying on its own isolated sequencer, a shared sequencer acts as a common ordering layer. This approach replaces fragmented liquidity pools with a unified view of user intent, allowing transactions on different chains to be processed in a coordinated sequence.

This mechanism differs significantly from traditional cross-chain bridging. Standard bridges typically involve locking assets on one chain and minting wrapped versions on another, a process that is slow and prone to fragmentation. Cross-rollup sequencing, by contrast, handles the ordering logic directly. As noted by Espresso Systems, while cross-rollup bridging functions similarly to cross-chain bridging, the key distinction lies in the shared consensus or ordering protocol that allows rollups to interact without relying solely on asset transfers.

The primary driver for this architecture is the reduction of Maximal Extractable Value (MEV). When rollups operate in isolation, arbitrageurs can exploit price discrepancies between them, often at the expense of regular users. A recent study on Cross-Rollup MEV highlights how non-atomic arbitrage opportunities exist between L2 blockchains. By sequencing transactions together, shared sequencers can align prices and reduce these arbitrage windows, ensuring fairer execution for all participants.

A shared sequencer is essentially a decentralized network that handles transaction ordering for multiple rollups at once. It replaces the single-operator sequencers common in many deployed systems with a distributed validator set. This shift improves liveness and censorship resistance while enabling true composability across the ecosystem.

Mastering Cross-Rollup Sequencing in

Shared sequencers are decentralized networks that handle transaction ordering for multiple rollups simultaneously, replacing single-operator sequencers with distributed validator sets to improve liveness and enable cross-rollup composability.
— Shared Sequencer Definition

The impact of this technology extends beyond technical efficiency. It fundamentally changes how liquidity flows between rollups. Instead of assets being locked in bridges, value can move fluidly as transactions are ordered together. This creates a more cohesive ecosystem where the boundaries between different rollups become less rigid, allowing for more complex and efficient financial interactions.

Why isolated rollups create MEV headaches

When rollups operate as independent silos, they inherit a specific vulnerability: non-atomic arbitrage. In a single-chain environment, a sophisticated trader can bundle transactions to extract maximum value from price discrepancies. But when that same logic spans multiple, disconnected chains, the problem amplifies. This is cross-rollup MEV, often described as "the unsolved problem of shared sequencing" because each rollup orders its transactions in isolation, unaware of the broader market context.

Consider a scenario where a token is listed on both an Arbitrum-based DEX and a Base-based DEX. If these rollups do not share sequencing data, an arbitrageur can exploit the time lag between them. They might execute a buy on Base, wait for the price to update, and then sell on Arbitrum. Because each rollup’s sequencer only sees its own local order book, it cannot detect that this sequence of trades is part of a single, cross-chain strategy. The result is fragmented liquidity and value extraction that benefits the attacker, not the protocol or its users.

This fragmentation creates a "waterbed" effect. Price movements on one chain can be artificially inflated or deflated by cross-rollup bots that front-run or sandwich trades across the gap. Without a shared view of the transaction pool, each rollup’s sequencer is blind to these cross-chain pressures. This makes it difficult to maintain fair pricing and exposes retail users to higher slippage and worse execution prices.

The core issue is that independent sequencers prioritize local efficiency over global consistency. They optimize for the fastest confirmation within their own chain, not for the integrity of the broader multi-chain ecosystem. As the number of rollups grows, this siloed approach becomes increasingly unsustainable, leading to the very MEV headaches that shared sequencing aims to resolve.

Traditional Sequencers vs. Shared Networks

The architecture of a rollup depends entirely on who controls the transaction order. In the current landscape, most Layer 2 networks rely on a traditional sequencer model. This approach treats sequencing as a centralized service, where a single operator or a tightly controlled node cluster receives transactions, decides their execution order, and provides fast confirmations to users. While this delivers low latency, it creates a single point of failure and concentrates significant power over MEV (Maximal Extractable Value) in one entity.

Shared sequencer networks represent a structural shift toward decentralization. Instead of each rollup running its own isolated ordering engine, these networks provide a shared infrastructure where multiple rollups submit transactions to a distributed validator set. This model replaces the single-operator bottleneck with a consensus mechanism that handles ordering across chains simultaneously. The result is improved liveness and censorship resistance, as no single operator can unilaterally reorder or drop transactions.

The technical implications extend beyond simple decentralization. Traditional sequencers often fragment liquidity because they cannot natively coordinate order flow between different rollups. Shared sequencers enable cross-rollup atomic composability, allowing transactions to be ordered together across chains. Although this feature is still maturing in production environments, it promises to eliminate the liquidity silos that currently plague the multi-chain ecosystem.

FeatureTraditional SequencerShared Sequencer
Operator StructureSingle operator or tightly controlled clusterDistributed validator set
Cross-Rollup ComposabilityNot supported; isolated order flowNative atomic ordering across chains
Censorship ResistanceLow; single point of controlHigh; consensus-based validation
Liquidity FragmentationHigh; siloed per rollupReduced; shared order book potential

How based rollups and L1 sequencing fit in

Shared sequencers are not the only path to cross-rollup composability. An alternative architecture relies on "based rollups," where the ordering authority shifts from a dedicated sequencer to the base layer itself. In this model, the Layer 1 proposer includes rollup blocks directly in the L1 block, effectively treating the rollup as an extension of the consensus layer rather than a separate sequencing silo.

This approach changes the economics of transaction ordering. Instead of a centralized operator deciding which transactions make it into the rollup block, L1 searchers and builders compete to include rollup data alongside L1 transactions. This permissionless inclusion allows for more efficient MEV extraction across the entire stack, as builders can optimize bundles that span both L1 and the rollup. It reduces the reliance on a single point of failure for ordering, aligning the rollup's security and liveness more closely with the base layer.

However, this tight coupling introduces complexity for cross-rollup interactions. If multiple rollups are "based" on the same L1, their blocks are ordered by the same L1 proposers. This can lead to contention or ordering conflicts if two based rollups attempt to process related state changes in the same L1 slot. The system must ensure that the L1 sequencing layer can handle the increased data throughput and that the ordering logic remains consistent across different rollup implementations.

Community views on shared sequencing in 2026

The industry is moving from theoretical papers to live testnets, and the conversation has shifted toward the practical mechanics of cross-rollup sequencing. Developers are no longer debating whether shared sequencers can exist, but how they will handle the complex reality of Multi-Party Computation (MPC) and transaction ordering.

Early discussions highlight the trade-offs between latency and decentralization. While a centralized sequencer offers speed, a shared, decentralized network introduces computational overhead. The community is closely monitoring how protocols like Cube and others manage this balance as they prepare for mainnet deployment.

"Shared sequencers are decentralized networks that handle transaction ordering for multiple rollups simultaneously. The idea is to replace each rollup's single-operator sequencer with a distributed validator set."

The focus is now on MEV mitigation. By making transaction ordering transparent and shared across rollups, developers aim to reduce the fragmented liquidity issues that plague isolated chains. This shift is expected to lower the barrier for cross-chain DeFi applications.

Common questions about rollup sequencers