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

# Governance Voting

Resupply governance is fully on-chain. All contracts on Resupply will be owned by a main core contract with a separate voter contract that is able to execute any transactions as though it is core.

Staking **RSUP** tokens is required to participate in governance voting. Unstaking of **RSUP** tokens is subject to a cooldown period in which no rewards will be given. The staking contract will work on a one week epoch system. New stakers must wait 1 epoch before they are granted voting power.

Resupply contracts are owned by **Core**, and a dedicated **Voter** contract (`0x1111…E6`, the active instance.

### Live parameters (verified on-chain, 2026-08-11)

| Parameter                                | Value                         |
| ---------------------------------------- | ----------------------------- |
| Epoch length                             | 7 days (weekly)               |
| Staking cooldown                         | 2 epochs (14 days)            |
| Weight of 1 staked RSUP                  | \~1 weight (no lock boost)    |
| Min weight to create proposal            | **1% of total staked weight** |
| Quorum to pass                           | **30%** of total weight       |
| Cooldown between proposals (same wallet) | 1 day                         |
| Voting period                            | 1 week                        |
| Execution delay after vote passes        | 1 day                         |
| Execution deadline                       | 3 weeks (after creation)      |


---

# 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.resupply.finance/resupply-governance/governance-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.
