> For the complete documentation index, see [llms.txt](https://manual.gitcoin.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.gitcoin.co/governance-processes/voting.md).

# Voting

The Gitcoin community makes decisions by voting on proposals. Anyone who has delegated GTC to themselves or has been delegated GTC by someone else is able to cast their vote.

In order for a proposal to go to a vote, it must meet the following requirements:

1. Posted for a minimum of 5 days on the Governance Forum
2. Have received a minimum of 5 comments from Stewards (excluding the proposer)

Once a proposal goes to vote, it typically goes to:

* An off-chain vote (to see if the community wants to proceed with the proposal), then
* An on-chain vote (to ratify the results of the off-chain vote)

This process is in place to eliminate gas fees for Stewards. The results of any off-chain vote (win/lose) are immediately replicated on-chain.

Voting mechanisms vary by proposal. Gitcoin currently exclusively follows a 1-token, 1-vote system. That said, we've also used quadratic voting to select our Steward Council, and intend to continue experimenting with other voting mechanisms.

Key links:

* Off-chain voting: <https://snapshot.org/#/gitcoindao.eth>
* On-chain voting: <https://www.tally.xyz/gov/gitcoin>


---

# 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://manual.gitcoin.co/governance-processes/voting.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.