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

# Token utility

$MESH is the lifeblood of the Mindmesh protocol, acting as the coordination and incentive layer across the compute, model, and data economy.

## Key functions

### Staking

Node operators must stake $MESH to participate in the compute mesh. Misbehavior (e.g. downtime, bad output) is penalized via slashing. Staking ensures network reliability and economic security.

### Payments

All services within Mindmesh — such as compute cycles, dataset access, model inference, or API usage — are priced in $MESH. This establishes a native demand sink for the token based on utility.

### Governance

$MESH holders can vote on proposals related to network upgrades, emission rates, treasury usage, grant programs, model whitelisting, and more. This fosters community-driven protocol evolution.

### Incentives

$MESH is distributed to contributors who provide value to the network, such as dataset curators, model developers, and prompt creators. Emissions are dynamically adjusted via DAO governance.

<details>

<summary>Future extensions</summary>

Future extensions may include staking-based access tiers, usage credits, validator delegation, and dual-token fee options.

</details>


---

# 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:

```
GET https://docs.mind-mesh.info/mindmesh/token-utility.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.