A Shared Sequencer is a blockchain sequencing system that receives and orders transactions for multiple Layer 2 networks instead of serving only one rollup. It provides common transaction-ordering infrastructure that different rollups can use while keeping their own execution environments, applications, and settlement logic.
In a conventional Layer 2 architecture, each rollup can operate its own sequencer. That sequencer determines the order of transactions before they are processed and eventually anchored to a settlement layer such as Ethereum. This approach can provide low latency, but it fragments sequencing across independent systems.
Shared Sequencers attempt to make sequencing a reusable service. Multiple rollups connect to the same sequencing network, which establishes transaction ordering on their behalf. The model can reduce reliance on individual centralised sequencers and, importantly, create coordination between rollups that would otherwise operate independently.
This cross-rollup coordination is one of the main reasons Shared Sequencers are more than simply outsourced sequencers. A common ordering layer can potentially support atomic transactions, shared MEV mechanisms, and more predictable interoperability between Layer 2 networks.
Why Share Sequencing Across Rollups?
The growth of Layer 2 ecosystems creates fragmentation. Two rollups may settle to Ethereum while maintaining completely separate transaction ordering systems. From Ethereum’s perspective they belong to the same broader ecosystem, but their immediate transaction histories are produced independently.
This creates problems for applications that need to interact across rollups. A transaction on Rollup A may depend on an action on Rollup B, but independent sequencers cannot automatically guarantee how the two actions will be ordered relative to each other.
A Shared Sequencer creates a common coordination point. Instead of each rollup independently deciding its next transaction order, several networks can receive ordering from the same decentralised sequencing system.
The concept also addresses some operational problems associated with centralised rollup sequencers. A single sequencer can become a liveness bottleneck if it goes offline. It can also potentially censor transactions or exercise significant control over ordering and MEV.
A distributed Shared Sequencer can spread these responsibilities among multiple participants while allowing several rollups to share the cost and complexity of maintaining sequencing infrastructure.
How a Shared Sequencer Works
The exact architecture varies between projects, but a Shared Sequencer generally operates between users and the execution environments of participating rollups.
Instead of submitting transactions only to a rollup-controlled sequencer, transactions enter the shared sequencing system. Its nodes agree on ordering according to a consensus or coordination mechanism. The resulting ordered transactions are then delivered to the relevant rollups for execution.
A simplified workflow is:
- Users submit transactions intended for participating Layer 2 networks.
- The Shared Sequencer receives transactions from several rollups.
- Sequencer nodes establish an agreed ordering.
- Ordered transactions are delivered to the appropriate execution environments.
- Each rollup executes its transactions according to its own state-transition rules.
- The rollups publish the required data, commitments, or proofs through their normal settlement and data availability infrastructure.
The Shared Sequencer therefore does not necessarily execute transactions itself. Its primary responsibility is ordering.
Likewise, it does not replace the rollup’s proof system or settlement layer. An optimistic rollup still needs its relevant verification and challenge architecture, while a ZK-rollup still needs validity proofs. Ethereum can remain responsible for final settlement even when transaction ordering is provided elsewhere.
This modularity allows sequencing to become an independent blockchain service.
Shared Sequencer vs Individual Sequencer
The difference between the two models is primarily about who controls ordering and whether that ordering can span several rollups.
| Characteristic | Individual Sequencer | Shared Sequencer |
| Networks served | Usually one rollup | Multiple rollups |
| Ordering infrastructure | Rollup-specific | Shared across participating networks |
| Cross-rollup coordination | Limited | Native coordination may be possible |
| Failure domain | Primarily one rollup | Can affect multiple connected rollups |
| Sequencer decentralisation | Depends on rollup | Can use a distributed sequencer network |
| MEV market | Usually rollup-specific | Can potentially span several rollups |
| Atomic cross-rollup execution | Difficult | Potentially easier |
| Infrastructure management | Maintained per rollup | Shared among participating rollups |
Shared infrastructure does not automatically mean decentralised infrastructure. A Shared Sequencer controlled by one entity could still represent a central point of control. The security properties depend on how sequencer nodes are selected, how they reach agreement, and what happens if the sequencing network fails.
The model also creates a larger failure domain. An outage affecting an individual sequencer may disrupt one rollup, while a failure in shared infrastructure can potentially affect several networks simultaneously.
Cross-Rollup Composability
One of the most important potential benefits of Shared Sequencers is synchronous or atomic coordination between rollups.
Composability is straightforward when applications exist on the same blockchain because transactions share a common state and ordering system. Across separate rollups, coordination is harder. Messages may need to pass through bridges, settlement layers, or asynchronous communication protocols.
A Shared Sequencer can observe transactions across participating networks and establish a common ordering. This can potentially allow applications to create transactions whose components depend on one another across rollups.
For example, a user might want to sell an asset on one Layer 2 and use the proceeds in another operation on a different Layer 2. Independent sequencers cannot easily guarantee that both actions succeed together. Shared ordering can provide infrastructure for stronger execution guarantees, depending on how the participating rollups are designed.
Potential applications include:
- atomic transactions spanning multiple rollups;
- cross-rollup arbitrage with coordinated execution;
- liquidity movement between Layer 2 networks;
- applications whose state or actions depend on several rollups;
- common ordering guarantees for cross-chain messaging;
- shared transaction inclusion and confirmation mechanisms.
Shared sequencing does not automatically make every rollup composable with every other rollup. Execution environments, settlement rules, communication protocols, and state dependencies still need to support the interaction.
It does, however, address one important part of the problem: establishing a common order for transactions that occur across otherwise independent systems.
Shared Sequencers and MEV
Transaction ordering has economic value. A sequencer can influence arbitrage, liquidations, decentralised exchange trades, and other operations where execution order matters.
With independent sequencers, each rollup develops its own MEV environment. Searchers compete separately, and liquidity fragmentation can create price differences between networks.
A Shared Sequencer can create a broader ordering market covering several rollups. Searchers could identify opportunities involving applications on different Layer 2 networks, while the sequencing protocol could establish rules for allocating or redistributing the resulting MEV.
This creates both opportunities and risks. Cross-rollup MEV could improve market efficiency by reducing persistent price differences between networks. At the same time, a shared ordering system could become an economically powerful infrastructure layer if it controls valuable transaction flows across many rollups.
The design of auctions, ordering rules, encryption, and reward distribution therefore becomes important. A Shared Sequencer needs to decide not only how transactions are ordered technically, but also who benefits economically from the right to determine that order.
Projects Developing Shared Sequencing
Shared sequencing has become an active area of Layer 2 infrastructure development rather than a single standard.
Espresso has been one of the prominent projects developing a decentralised sequencing network intended to support multiple rollups. Its approach focuses on providing shared ordering and confirmations while allowing rollups to retain their own execution environments.
Other projects and research initiatives have explored similar concepts through decentralised sequencing, interoperability layers, and rollup coordination systems.
The implementations can differ substantially. Some focus primarily on decentralising the sequencer role, while others place greater emphasis on interoperability, preconfirmations, MEV, or atomic cross-rollup transactions.
This means the term Shared Sequencer should describe the architectural role rather than any particular protocol. The common characteristic is that transaction-ordering infrastructure is used by multiple Layer 2 systems.
Trade-Offs of Shared Sequencing
Shared Sequencers can remove duplicated infrastructure, but they introduce a new dependency into the rollup stack.
A rollup that previously controlled its own sequencer becomes dependent on an external sequencing network for normal transaction ordering. If that network fails, the rollup needs a fallback mechanism or users may experience reduced liveness.
The major trade-offs include:
- stronger cross-rollup coordination but increased dependency on common infrastructure;
- potential sequencer decentralisation but a larger shared failure domain;
- broader MEV markets but greater concentration of economically valuable order flow;
- simpler sequencing infrastructure for rollups but additional integration complexity;
- faster interoperability in some designs but new consensus and networking assumptions;
- common confirmations but potential differences between sequencing confirmation and final settlement.
Fallback mechanisms are therefore important. A rollup may still need a way to bypass the Shared Sequencer and interact with its underlying settlement system if shared infrastructure becomes unavailable or attempts censorship.
The precise security model depends on how much authority the rollup delegates to the sequencing network.
Shared Sequencing as Modular Infrastructure
Shared Sequencers fit into the broader movement towards modular blockchain architecture. Instead of requiring every rollup to develop execution, sequencing, data availability, proving, and settlement infrastructure independently, these functions can be provided by specialised systems.
In this model, sequencing becomes a service that several Layer 2 networks can consume.
The main advantage is not simply lower operational cost. A common sequencing layer can create coordination between rollups that otherwise behave like isolated blockchains. This can improve interoperability and potentially make a multi-rollup ecosystem behave more like a connected execution environment.
The trade-off is that shared infrastructure creates shared dependencies. A successful Shared Sequencer therefore needs strong liveness, censorship resistance, transparent ordering rules, and mechanisms that allow participating rollups to remain safe if the sequencing service fails.
Shared Sequencers are ultimately an attempt to solve two Layer 2 problems at once: decentralising transaction ordering and reducing fragmentation between rollups. Whether they become standard infrastructure will depend on whether those benefits outweigh the complexity and dependency introduced by adding another shared layer to the rollup stack.