# Veto

## What is Veto? <a href="#what-is-veto" id="what-is-veto"></a>

Veto is a governance safeguard that enables:

* **Community Veto**: Community token holders can block proposals
* **Council Veto**: Council members can block proposals
* **Quorum-based Rejection**: Proposals are vetoed when rejection votes meet the configured quorum

This provides an additional layer of protection against proposals that may have passed the approval threshold but face strong opposition.

## Veto Configuration <a href="#veto-configuration" id="veto-configuration"></a>

DAOs can configure veto settings separately for both community and council governance.

### Community Veto Settings <a href="#community-veto-settings" id="community-veto-settings"></a>

* **Veto Quorum (%)**: The percentage of community voting power required to veto a proposal
* **Enable/Disable**: Toggle community veto capability on or off

### Council Veto Settings <a href="#council-veto-settings" id="council-veto-settings"></a>

* **Veto Quorum (%)**: The percentage of council members required to veto a proposal
* **Enable/Disable**: Toggle council veto capability on or off

### Setting Up Veto <a href="#setting-up-veto" id="setting-up-veto"></a>

{% stepper %}
{% step %}

#### Access DAO Configuration

Navigate to your DAO's **Settings** section to view current governance settings.
{% endstep %}

{% step %}

#### Create Configuration Proposal <a href="#step-2---create-configuration-proposal" id="step-2---create-configuration-proposal"></a>

Create a proposal to modify the DAO configuration and enable veto settings.

* Create Proposal
* Edit Wallet Rules
* Advanced Community Settings/ Advanced Multisig Settings
* Enable/ Disable
  {% endstep %}

{% step %}

#### Configure Veto Parameters <a href="#step-3---configure-veto-parameters" id="step-3---configure-veto-parameters"></a>

Set the veto quorum for community and/or council:

* **Community Veto Quorum**: Percentage of community tokens needed to veto
* **Council Veto Quorum**: Percentage of council votes needed to veto
  {% endstep %}

{% step %}

#### Submit and Vote <a href="#step-4---submit-and-vote" id="step-4---submit-and-vote"></a>

Submit the configuration proposal for community/council approval.
{% endstep %}

{% step %}

#### Execute Changes <a href="#step-5---execute-changes" id="step-5---execute-changes"></a>

Once approved, execute the proposal to apply the new veto settings.
{% endstep %}
{% endstepper %}

## How Veto Works <a href="#how-veto-works" id="how-veto-works"></a>

### During Voting <a href="#during-voting" id="during-voting"></a>

1. Members vote **Yes**, **No**, or **Veto (If enabled)** on a proposal
2. **Veto** votes count toward the veto quorum
3. If veto quorum is reached, the proposal is blocked regardless of approval votes

### Veto Outcome <a href="#veto-outcome" id="veto-outcome"></a>

* **Vetoed**: Proposal blocked when rejection votes meet veto quorum
* **Passed**: Proposal approved if it meets approval threshold without triggering veto
* **Failed**: Proposal fails to meet approval threshold


---

# 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://docs.realms.today/realms-v2/features/veto.md?ask=<question>
```

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.