Shared Sequencing
Shared sequencing separates the tasks of sequencing transactions and executing them. During the process, the shared sequencer only sequences transactions and builds blocks for rollups. This simplifies the operations of rollups and allows them to focus on their core functionality: execution.
Once the sequencing layer has provided the block, the rollup (or the execution layer) executes the transactions in the order they were provided. The transactions are then submitted to the data availability layer for storing data and/or the settlement layer for finalization.
Shared sequencing offers several benefits that help rollups scale more effectively:
- Reduced time and cost for bootstrapping validator set: Shared sequencing significantly reduces the time and cost required to bootstrap and operate a validator set, which can be a bottleneck in launching a rollup.
- Reduced rollup complexity: Shared sequencing reduces the overall complexity of the rollup, making it easier to maintain and upgrade the rollup over time. Implementing the sequencing layer is a simple process of plugging in and swapping out necessary components.
- Enhanced cross-rollup interoperability: Cross-rollup bridging and transaction verifications can be complex when rollups use different sequencers. Shared sequencing improves interoperability and enables atomic composability by using the same sequencer for cross-rollup communications. This not only makes bridging between rollups more efficient but also improves the user experience and mitigates the risk of attacks and latency associated with cross-rollup bridging.
Last modified 24d ago