> For the complete documentation index, see [llms.txt](https://egochain1.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://egochain1.gitbook.io/doc/develop/get-started.md).

# Get Started

#### Building a dApp on Egochain

Are you looking to build a decentralized application (dApp) on Egochain? Our comprehensive documentation and academy provide the resources you need to learn how and become a part of the rich Egochain ecosystem. Whether you're creating new use cases on Egochain or porting an existing dApp from another blockchain, you'll find valuable information in the following sections:

* **Building and Deploying EVM Smart Contracts**
* **Integrating Wallets (e.g., Keplr and MetaMask) into Your Frontend**
* **Available Developer Tools**

Once you have tested your dApp on Testnet and deployed it on Mainnet, you can start earning income from transaction fees through interactions with your dApp or register your tokens for cross-chain use.

#### Why Develop dApps on Egochain?

The Egochain Core Development Team is dedicated to providing the essential tools for building the cross-chain applications of the future. Egochain liberates developers from the limitations of today’s siloed blockchains by focusing on cross-chain innovation. This allows developers to create entirely new dApp experiences for their users.

Deploying smart contracts on Egochain is straightforward, as the blockchain is fully compatible with Ethereum and its extensive ecosystem of robust tools, wallets, explorers, numerous assets, and intelligent end-users. Additionally, Egochain enables developers to build scalable EVM dApp chains using the upcoming Egochain SDK. It also boasts one of the most active community governance systems, promoting fairness among all key participants (users, builders, and validators).


---

# 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://egochain1.gitbook.io/doc/develop/get-started.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.