> For the complete documentation index, see [llms.txt](https://docs.metaverse-ico.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metaverse-ico.net/whitepaper/smart-contract/smart-contract-compatibility.md).

# Smart Contract Compatibility

MetaChain offers smart contract support in accordance with EVM, with the vision of supporting distributed applications and software developers beyond just financial transactions and data storage. Thus, existing smart contracts on Ethereum and similar networks can be uploaded to MetaChain without the need for any modifications.

In addition, Metachain enables the creation of Advanced Smart Contracts (MASC / Metachain Advanced Smart Contract); ERC20, ERC721, ERC 1155 and other standardized protocols (See: <https://eips.ethereum.org/all> ) and all their associated functions with the help of an interface. This way, a smart contract can be created and uploaded to the chain by drag-and-drop, without the need for technical knowledge.

Because smart contracts on MetaChain are EVM compatible, such libraries and tools can be used that are common in the Solidity software language and existing wallet structures.


---

# 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.metaverse-ico.net/whitepaper/smart-contract/smart-contract-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.