Purpose and High-Level Flow

Purpose and High-Level Flow

When the Eclipse L2 generates a new block (or “batch”), it posts a commitment to the Gateway. This references the previous commit to maintain continuity. The Gateway enforces the correct parent-child relationship and logs each commit to an internal registry to prevent duplicates.

• Initialization: The contract starts uninitialized. The first submitBatch with a zero parent hash becomes the genesis batch.

• Normal Operation: As the aggregator or sequencer produces new L2 blocks, they call submitBatch, extending the chain tip.

• Forking: If a dispute or bug arises, an authorized user (an entity with FORKER_ROLE) can create a new fork from a specific commit (by calling forkChain) , potentially replacing the current chain.

• Canonicality: By default, the chain with the highest fork ID is considered the tip. However, older forks remain in storage (and can be restored if needed).

• Access Control: OpenZeppelin’s AccessControlEnumerable checks every critical function (e.g., only PAUSER_ROLE can pause).

• Pausible: While paused, no commits or forks can happen, protecting the contract from malicious or unintended updates.

Below, we dive into each concept, show test code to illustrate usage, and then present the detailed sequence diagrams and state transition diagrams that map out the system’s execution in a visual format.