> For the complete documentation index, see [llms.txt](https://docs.metronome.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metronome.io/metronome-2.0/governance/voting-and-participation.md).

# Voting and Participation

MET DAO members can engage by proposing and developing Metronome Improvement Proposals (MIPs), casting votes on MIPs, and sharing their opinion in our forums.

Votes can only be cast by holders of MET tokens, including holders of locked/vesting tokens. The vote passage/approval requirements are as follows:

| Action                   | Threshold                                                                       |
| ------------------------ | ------------------------------------------------------------------------------- |
| Bring a proposal to vote | Submitters must have the delegation of at least 25,000 MET                      |
| Voting - Reach Quorum    | 4% of the circulating MET supply must vote                                      |
| Voting - Vote Passes     | A minimum of 50%+1 of votes cast with a ‘YES’ votes and quorum has been reached |

##


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.metronome.io/metronome-2.0/governance/voting-and-participation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.