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

# Governance and Voting

#### **Introduction to Governance** <a href="#introduction-to-governance" id="introduction-to-governance"></a>

The SYRUP token is the governance token for the Maple ecosystem and aligns stakeholders, drives governance and incentives participation. With the approval of [MIP-019](https://snapshot.box/#/s:maple.eth/proposal/0x8151eb49b56770b882e8d9b6affd4a698572fc6eec31001c74bd977f61c84374), both SYRUP and stSYRUP are eligible for participation in voting.

Governance voting include decisions on token distribution, recapitalising the Maple Treasury, launching new products, and upgrading the smart contract infrastructure.

#### **Voting** <a href="#introduction-to-governance" id="introduction-to-governance"></a>

Voting is conducted by connecting a wallet with sufficient SYRUP or stSYRUP balance to [Snapshot](https://snapshot.org/#/maple.eth). Governance proposals have a 7-day voting window, during which participating wallets can vote for against a proposal. Once a quorum has been reached for or against a decision, and the 7-day voting window is over the vote has passed. If a quorum is not reached, or there are more votes against the proposal than for, the vote is rejected.


---

# 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.maple.finance/maple-for-token-holders/governance-and-voting.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.