> For the complete documentation index, see [llms.txt](https://solar-studios.gitbook.io/solar-studios/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solar-studios.gitbook.io/solar-studios/solar-dex/supported-networks.md).

# Supported Networks

Solar DEX is built natively on the Eclipse Network, leveraging its high-speed execution and scalable architecture to deliver seamless and efficient trading. Designed with expansion in mind, Solar DEX plans to integrate with additional networks, providing broader accessibility and interoperability.

Current and Planned Networks:

* Eclipse Network (Native): Core infrastructure with secure, fast, and low-cost transactions.
* Quai (Planned): A decentralized layer that offers unique scalability solutions.
* Soneium (Planned): Optimized for DeFi and GameFi applications, enhancing cross-chain liquidity.

As Solar DEX grows, future integrations with other leading networks will further expand cross-chain opportunities, ensuring users have access to a diverse and dynamic decentralized exchange environment


---

# 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://solar-studios.gitbook.io/solar-studios/solar-dex/supported-networks.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.
