What Are Shared Sequencers? Cross-Rollup Coordination Explained

A shared sequencer is a network that orders transactions across multiple rollups at once, instead of each rollup having its own isolated sequencer that only orders transactions for itself. The goal is to let actions on different rollups be coordinated, or even executed atomically together, as if they happened on one chain.

The problem shared sequencing tries to solve

Most rollups today run their own sequencer — a node or small set of nodes responsible for ordering and batching user transactions before they're posted to the settlement layer. This works fine for a single chain, but it creates two problems as the number of rollups grows.

First, cross-rollup transactions become slow and clunky. If you want to swap on rollup A and immediately use the proceeds on rollup B, you generally need to wait for a bridge to finalize between the two independent sequencing processes — there's no way to guarantee both actions happen together or not at all.

Second, MEV opportunities that span multiple chains become harder to police. A searcher who can see pending transactions on several rollups at once may extract value across them in ways that are invisible to, and unaddressed by, any single rollup's own MEV mitigations.

How shared sequencing works in practice

A shared sequencer network sits above individual rollups and takes on the job of ordering transactions destined for any participating chain. Projects like Espresso Systems and Astria have built networks along these lines. The mechanics generally involve:

• Rollups opting in to have their transaction ordering handled by the shared network instead of their own sequencer.
• The shared sequencer producing an ordered stream of transactions that gets split back out to each rollup for execution.
• Some designs allowing "atomic" cross-rollup transaction bundles, where a set of transactions across multiple chains either all execute or none do.

This is conceptually related to but distinct from preconfirmations, which are about giving users fast inclusion guarantees rather than specifically about cross-chain ordering.

Why this matters for MEV and composability

Rollup interoperability today is largely handled through bridges, which are slow relative to native, same-chain transactions and don't offer atomicity — see our explainer on rollup interoperability for more on why cross-L2 communication is hard. Shared sequencing is one of several approaches attempting to close that gap, alongside shared proving and messaging standards.

On the MEV side, centralizing ordering into a shared network doesn't eliminate MEV — it changes who can extract it and how. A shared sequencer that can see order flow across many chains has more information and power than any single-chain sequencer, which raises its own centralization and fairness concerns that the space is still actively debating solutions for (encrypted mempools, fair ordering rules, and decentralized sequencer sets among them).

Shared sequencing vs. independent sequencing

Aspect	Independent per-chain sequencer	Shared sequencer network
Cross-chain atomicity	Not possible natively	Possible for participating chains
Cross-chain MEV visibility	Limited to that chain	Broader, spanning multiple chains
Maturity	Standard today, widely deployed	Early-stage, few production deployments
Decentralization	Varies per chain, often centralized	New trust model, still being tested

What this means for users today

For most users, shared sequencing is not yet something you interact with directly — it's largely infrastructure-stage technology being built and piloted by specific rollup projects. The practical takeaway is that cross-chain actions today still mostly rely on bridging, and users should treat any bridge or cross-chain swap as carrying its own timing and smart contract risk, regardless of how sequencing evolves underneath it. Checking a chain's TVL and activity on chains data pages remains a better day-to-day signal of a rollup's health than its sequencing architecture.

Encrypted mempools and fair ordering research

A big part of the shared sequencer conversation overlaps with broader research into fairer transaction ordering generally. One proposed mitigation is encrypting transactions until after their order is committed, so that whoever is doing the ordering (shared sequencer or otherwise) can't see the contents of a transaction well enough to front-run or sandwich it before deciding where it goes in the sequence. Other proposals focus on strict first-come-first-served ordering rules enforced by the sequencing network's own protocol, removing discretion from the operator entirely rather than merely making that discretion transparent.

None of these approaches is a complete solution on its own, and most shared sequencer projects are experimenting with some combination of these ideas rather than having settled on one dominant design. This is very much an active research area, and the specific guarantees offered by any given shared sequencer network should be evaluated on their own technical merits rather than assumed from the general concept.

Adoption status and what to watch

As of now, shared sequencing remains mostly at the pilot or early-mainnet stage rather than something the majority of rollup transaction volume runs through. A handful of rollups have integrated with early shared sequencer networks, but most major L2s by TVL and activity still run their own independent sequencer. Watching adoption numbers, audited security reviews, and whether these networks maintain uptime and fair ordering guarantees under real usage over an extended period will tell you more about their viability than the underlying concept alone.

Bottom line

Shared sequencers aim to solve two real problems in the rollup landscape: slow cross-chain transactions and fragmented, hard-to-police MEV. They're a promising but early-stage piece of infrastructure, with a handful of live networks and no dominant standard yet. Users should keep relying on careful, verified bridging for cross-chain moves today, while developers evaluating rollups should watch this space as one of several efforts to solve rollup interoperability.