> 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/architectural-overview/core-infrastructure.md).

# Core Infrastructure

Eclipse’s modular infrastructure provides execution scalability, verifiability, and user sovereignty. The system is structured around three foundational components:

* **Eclipse Canonical Bridge**: Provides secure withdrawal finality and settlement on Ethereum.
* **Eclipse L1 Gateway**: Ethereum L1 smart contract that stores batches posted by the L2 that contain pointers to Celestia blobs and state commitments.
* **Eclipse Celestia Publisher**: Ensures scalable data availability by batching and posting Eclipse block data to Celestia.

Together, these components uphold Eclipse’s rollup guarantees while offering flexibility for future upgrades.

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.eclipse.xyz/architecture/eclipse-architecture/architectural-overview/core-infrastructure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
