# Veto System Nuon uses a veto system similar to Frankencoin’s, where a minority quorum of voters can veto a vault proposal. A veto-based voting system confers several advantages over a traditional majority vote method. It mitigates the ability to acquire a stake large enough to force through malicious proposals by requiring broader consensus for changes, as it is much easier for actors to block proposals than a majority vote system. It is more efficient while also encouraging collaboration, fostering stability, and ensuring only well-considered proposals are implemented. Proposals are made on-chain by users, who suggest a token contract address and provide a veto bounty for their submission. The veto bounty acts as an anti-spam mechanism to prevent the submission of frivolous or malicious proposals. This mechanism ensures that users have a financial stake in the quality and validity of their proposals. Once a proposal is submitted, there is a predefined veto period during which other users can challenge the proposal. 2% of the total amount of staked MaxCap is required to veto a proposal. MaxCap stakers who disagree with the proposal can submit a veto by staking a higher bounty than the original proposer. --- # Agent Instructions: 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: ``` GET https://whitepaper.nuon.fi/governance/veto-system.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.