> For the complete documentation index, see [llms.txt](https://one-usd.gitbook.io/fundsfi-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://one-usd.gitbook.io/fundsfi-whitepaper/governance/voting.md).

# Voting

## How voting works:

* To vote you must hold $FUNDS. 
* Atleast **70%** **of the holders** must vote for the vote to pass.
* Atleast **51% voters** must say yes for the proposal for the vote to pass. 
* All votes must have a reason for the vote! A vote without a reason does not get counted towards the end. 
* After that if the team thinks the decision is bad then the core team can veto the decision. 
* All rejected decision can be brought up again for voting after changes are made. 
* If a proposal is denied then the proposer must change the proposal to propose another change. 

## **Propose a change: (Coming Soon)**

## More Details Coming Soon . . .


---

# 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://one-usd.gitbook.io/fundsfi-whitepaper/governance/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.