Multi-Rollup

Overview

Meaning and scope

A multi-rollup environment contains several rollups that share, coordinate, or connect execution while retaining distinct state, sequencing, and settlement domains. Transactions between rollups are cross-domain operations, not ordinary local calls. They can require source finality, message proving, relay, destination execution, and liquidity. Shared infrastructure may improve composability but can create correlated upgrade, sequencer, or proof-system risk.

Mechanism and operation

Multi-rollup architectures use multiple rollup instances for applications, regions, execution environments, or throughput. Rollups may share a settlement layer, proof system, sequencer network, bridge framework, or interoperability standard while maintaining separate chain identities. Developers should define canonical asset routes, message ordering, replay protection, and recovery from delayed domains. Payment systems should track each leg separately and avoid assuming that two rollups settling on the same Layer 1 provide instant atomic transfers. Users should have a documented route to recover or exit when the preferred sequencer, prover, or interface is unavailable. Production support needs monitoring for sequencer outages, delayed batches, proof failures, forced-inclusion paths, contract pauses, and upgrade events.

Practical payment example

A SaaS platform serves customers on two rollups. Its billing backend maintains separate chain IDs, token contracts and withdrawal rules, even when both networks ultimately publish data to Ethereum.

Operational checks

Multi-Rollup should be described through its execution, sequencing, data-publication, proof or challenge, bridge, and settlement stages. The security model for Multi-Rollup includes sequencer control, proof or fault-resolution rules, data availability, bridge contracts, upgrade keys, and the base-layer verifier. Payment applications using Multi-Rollup should maintain separate states for local acceptance, batch publication, proof verification or challenge completion, bridge execution, and base-layer finality.

Distinctions and limits

A transaction accepted by a sequencer has not necessarily been published, proven, finalized on the base layer, or made withdrawable. A cryptographic proof can reduce execution trust while leaving censorship, data, governance, and contract risks.

Related reading

Related definitions: rollup.