> For the complete documentation index, see [llms.txt](https://whitepaper.nuon.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.nuon.fi/governance/vote-power-weighting.md).

# Vote Power Weighting

When you stake MaxCap, you vote for a vault and begin accumulating MaxCap rewards, which cannot be transferred between wallets. Claiming USDC or changing your vote resets the voting power of the user back to 0.

Voting power is calculated for each individual based on their share of the staked MaxCap and the locking time of their staked MaxCap. The lockup choices are 3 months, 6 months, 9 months, and 1 year, where 1 year- lockup equals 100% of voting power and 3 month lockup equals 25% of the voting power.&#x20;

The amount of MaxCap allocated to each vault is also tracked to determine how to proportionally allocate USDC in the treasury that is being converted to yield-bearing assets. The more MaxCap a vault has, the more USCC capital will flow into it.

Proposals last for 1 epoch (7 days) and can be rejected via a veto of mib 2% of the total voting power. A minimum veto bounty of 1000 USDC is required to start a proposal. If a proposal is vetoed, then the bounty is distributed proportionally to those who vetoed it. If a proposal for a vault is accepted, the proposer reclaims the bounty.


---

# 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://whitepaper.nuon.fi/governance/vote-power-weighting.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.
