# Governance & MENTO

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: 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.mento.org/mento-v3/dive-deeper/governance-and-mento.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.