> 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/stage-0-and-stage-1.md).

# Stage 0 & Stage 1

Eclipse is currently working on deploying the optimistic layer 2 protocol, with the following milestones (following the guidelines from [L2Beat](https://l2beat.com)):

* **Stage 0**
  * Deploy the Eclipse Gateway smart contract on Ethereum to post the state of the layer 2 chain periodically
  * Provide an open-source validator node software that can re-execute Eclipse blocks from the data stored on Celestia
  * Make availability of the data on Celestia verifiable from Ethereum (required for optimiums)
  * Deploy a fraud proof system compatible with the SVM execution logic
* **Stage 1**
  * Guarantee permissionless exit of funds from Eclipse
  * Implement a delay on smart contract updates to allow users to exit the rollup before an undesirable update
  * Implement a sufficiently decentralized security council for security-critical operations, such as emergency updates or in, some extreme cases, pausing the L1 smart contracts.

We plan to implement fraud proofs with RISC Zero’s [Kailua](https://github.com/risc0/kailua), an optimistic fraud proof system based on Zero Knowledge (ZK) proofs that guarantees resolution of challenges in a single step. Find more information in [our article](https://www.eclipselabs.io/blogs/fraud-proofs-the-eclipse-perspective) regarding Kailua and our plans regarding this key part of the protocol.

Similarly, we developed a ZK-based data availability challenge system based on Celestia’s Blobstream oracle that lets anyone prove that the sequencer lied about posting a specific piece of data on Celestia.


---

# 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/stage-0-and-stage-1.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.