> For the complete documentation index, see [llms.txt](https://docs.mento.org/mento-v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mento.org/mento-v3/dive-deeper/governance-and-mento.md).

# Governance & MENTO

Mento is community-governed through the MENTO token. Learn how governance works, explore tokenomics, distribution, discover how to participate in decisions, and understand safety mechanisms in place.

Mento V3 is **community-governed** through the **MENTO** token. Governance controls protocol parameters (fees, rebalance incentives, TradingLimitsV2, circuit breaker thresholds), oracle and feed configuration, pool allowlists, and Reserve policy. **veMENTO** (vote-escrowed MENTO) gives increased voting power for longer lock-ups. Protocol revenue is intended to flow to MENTO holders **indirectly** through governance-directed **MENTO token buybacks**, not through direct veMENTO revenue sharing.

**What is governed:** Protocol parameters (fee structures, risk parameters, pool configuration), oracle management (provider selection, feed configuration), and technical upgrades (contract updates, security patches, integration approvals). All decisions execute on-chain with timelocks and optional watchdog veto during the transition period.

**Next:** [Understanding Mento Governance](/mento-v3/dive-deeper/governance-and-mento/understanding-mento-governance.md) — how voting and proposals work. [MENTO Tokenomics](/mento-v3/dive-deeper/governance-and-mento/mento-tokenomics.md) — supply, distribution, and value accrual.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mento.org/mento-v3/dive-deeper/governance-and-mento.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 `automate deployments from our CI pipeline` 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.