> For the complete documentation index, see [llms.txt](https://docs.mazze.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mazze.io/tokenomics/token-utility.md).

# Token Utility

The Powerhouse of the Mazze Ecosystem and the fueling Ecosystem Growth

The MAZZE token utility is now described using the current model in `new-docs`.

### <mark style="color:orange;">**Wrapped MAZZE (Ethereum) Utility**</mark>

1. **Facilitates Immediate Liquidity** | Provides early market access on Ethereum.
2. **Supports DEX and CEX Access** | Enables trading and onboarding before full native migration.
3. **Supports Development and Ecosystem Funding** | Helps maintain operations and expansion.
4. **Enables Bridge Onboarding** | Allows Ethereum-side users to move into native MAZZE as bridge capacity allows.

### <mark style="color:orange;">**Native MAZZE (Mazze Chain) Utility**</mark>

1. **Transaction and Execution Fuel** | Used for native-chain transaction economics.
2. **Mining and Security Incentives** | Issuance follows the configured halving schedule.
3. **Fee/Burn Accounting** | Realized supply is affected by mint and burn paths.
4. **Privacy-Related Flows** | Supports shielded pool funding and private transfer mechanics.

### <mark style="color:orange;">**Reference Pages**</mark>

* [Wrapped Token (ERC20)](/tokenomics/wrapped-token-erc20.md)
* [Bridge Liquidity](/tokenomics/bridge-liquidity.md)
* [Issuance](/tokenomics/issuance.md)
* [Shielded Pool Genesis Fund](/tokenomics/shielded-pool-genesis-fund.md)


---

# 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.mazze.io/tokenomics/token-utility.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.