> For the complete documentation index, see [llms.txt](https://tokenlon.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tokenlon.gitbook.io/docs/docs.en/blog/whatsnew/tokenlisting/mnt-mantle.md).

# MNT (Mantle)

**MNT**

Supported pairs: MNT / ETH, MNT / USDT

Contract address: 0x3c3a81e81dc49A522A592e7622A7E711c06bf354

Mantle Network is an L2 technology stack for scaling Ethereum, and is the first core product of Mantle Ecosystem. Mantle Network strives to be compatible with the Ethereum Virtual Machine. Mantle Network’s modular architecture separates transaction execution, data availability, and transaction finality into modules — which can be individually upgraded and adopt the latest innovations.

As the world’s first DAO-spawned L2, Mantle Network is pioneering a vision for the mass adoption of token-governed technologies.

MNT is the native token used for:

* Paying gas fees
* Growing the ecosystem
* Governance by the community


---

# 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://tokenlon.gitbook.io/docs/docs.en/blog/whatsnew/tokenlisting/mnt-mantle.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.