> 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/readme.md).

# Getting Started

## For New Eclipse Users Starting Out:

### [Set Up Your Eclipse Wallet](/readme/set-up-your-eclipse-wallet.md)

The first step is to create and configure your Eclipse wallet, your gateway to everything Eclipse.

### [Bridge Assets for Gas and Transactions](/readme/bridge-assets-for-gas-and-transactions.md)

Depending on your current blockchain experience, there are two main pathways (Ethereum or Solana) for bridging assets to Eclipse for gas.

### [Explore the Eclipse Ecosystem](/readme/explore-the-eclipse-ecosystem.md)

Once your wallet is set up and funded, you’re ready to explore! Browse and engage with various public Dapps built on Eclipse.

### [Engage with the Community on Discord](/readme/engage-with-the-community-on-discord.md)

Join the Eclipse community on Discord to connect with other Eclipse users, stay in the loop on new developments, events, exclusive opportunities, and discussions that shape the Eclipse ecosystem.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eclipse.xyz/readme.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 `build a script that syncs our docs to a CMS` 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.