> For the complete documentation index, see [llms.txt](https://docs.eclipse.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eclipse.xyz/architecture/eclipse-architecture/eclipse-l1-gateway.md).

# Eclipse L1 Gateway

## Introduction and Motivation

The **Syzygy L1 Gateway** is a smart contract system that anchors the state of the Eclipse Layer 2 (L2) blockchain onto an Ethereum-based Layer 1. By storing sequential commitments (hashes of L2 blocks), along with an ability to **fork** when necessary, the Gateway ensures an auditable, on-chain record of L2 state progression. Fork management, role-based access control, and pausable safety mechanisms all come together to form a robust design for real-world rollup usage.

In particular, the Gateway addresses these key challenges:

1. **Immutable Commitment Chain**: Recording L2 blocks so that anyone can verify their sequential integrity.
2. **Fork Support**: Allowing the L2 system to reorganize or branch off from a previous commit.
3. **Access Control**: Ensuring only designated roles can submit batches or create forks.
4. **Emergency Pausing**: A failsafe to halt state changes during high-severity incidents.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eclipse.xyz/architecture/eclipse-architecture/eclipse-l1-gateway.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.