> 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/participating-in-governance.md).

# Participating in Governance

## Introduction

Mento governance puts the protocol's future in the hands of its community. Through on-chain voting, MENTO token holders directly influence protocol parameters, treasury allocations, and strategic direction.

The governance process is designed to be transparent, secure, and accessible. By locking MENTO tokens to receive veMENTO (vote-escrowed MENTO), participants gain voting power proportional to their commitment to the protocol's long-term success.

## How Governance Works

Mento uses a decentralized governance model where:

* **veMENTO** holders vote on all protocol changes and propose new ones.
* **Proposals** follow a structured lifecycle from forum discussion to on-chain execution
* **Watchdogs** provide security oversight with veto power
* **Time delays** ensure transparency and allow for community review

Whether you want to vote on existing proposals or create your own, the governance system provides clear pathways for participation at every level.

## Getting Started

Your governance journey typically follows these steps:

1. **Acquire voting power** by locking MENTO for veMENTO
2. **Participate in discussions** on the governance forum
3. **Vote on proposals** that shape the protocol
4. **Create proposals** to implement your ideas

Each aspect of governance has its own guide to help you participate effectively.

## Governance Guides

### [veMENTO & Voting Power](/mento-v3/dive-deeper/governance-and-mento/participating-in-governance/vemento-and-voting-power.md)

Learn how to lock your MENTO tokens, understand voting power calculations and manage your position.

### [Creating Proposals](/mento-v3/dive-deeper/governance-and-mento/participating-in-governance/creating-proposals.md)

Step-by-step guide to crafting proposals, from initial forum discussions through technical specifications and on-chain submission.

### [Voting Process](/mento-v3/dive-deeper/governance-and-mento/participating-in-governance/voting-process.md)

Understand how to evaluate proposals, cast your vote, track results, and monitor the execution of passed proposals.

## Key Resources

* **Governance Interface**: [governance.mento.org](https://governance.mento.org/)
* **Forum Discussions**: [forum.mento.org](https://forum.mento.org/)

## Why Participate?

Active governance participation:

* **Shapes the protocol** according to community needs
* **Protects value** through careful parameter management
* **Drives innovation** by funding new developments
* **Builds community** through collaborative decision-making
* **Directs revenue** by deciding how protocol flows are distributed ($MENTO buybacks, liquidity incentives)

Your voice matters in Mento governance. Every vote contributes to the protocol's decentralized decision-making process.


---

# 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/participating-in-governance.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.