> For the complete documentation index, see [llms.txt](https://docs.escc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.escc.io/core-features-and-technical-aspects-of-escc/understanding-eos-evm-compatibility.md).

# Understanding EOS EVM Compatibility

EOS EVM Compatibility is a standout feature of ESCC, providing significant benefits:<br>

**Seamless Ethereum Integration:** Developers can easily migrate or create Ethereum-based applications on ESCC, thanks to its EOS EVM compatibility.

**Access to Ethereum's Development Tools:** This compatibility allows developers to use familiar Ethereum development tools and frameworks, reducing the learning curve and accelerating development.

**Broader Application Scope:** By bridging EOS and Ethereum ecosystems, ESCC expands the scope of potential applications, attracting a wider developer community and user base.

Interoperability with Ethereum Ecosystem: ESCC enables interoperability with a vast array of existing Ethereum-based assets and services, enhancing the utility and reach of the ESCC platform.

<br>


---

# 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.escc.io/core-features-and-technical-aspects-of-escc/understanding-eos-evm-compatibility.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.