# Voting

{% file src="/files/AiqAmhc64ntA0oQWcW5O" %}
A graphical format of the Voting Framework can be found here.
{% endfile %}

***On September 1, 2022**, an* [*amendment*](https://snapshot.org/#/rugcommunity.eth/proposal/0xfa1574926ef4f4245eded42490089479d39ce31d0fbadf1b0b0b1a1544bc77e5) *to this framework was passed that set up a tiered quorum structure.*

***On December 27, 2022,** a second* [*amendment*](https://snapshot.org/#/rugcommunity.eth/proposal/0x3ebdc95900cfc2707c0f92b5529e877cfec6b1a3eae1e70e50d22ada9bbb65df) *to this framework was passed that reduced quorum tiers, increased voting timeframes, and more.*

 

## Glossary of Key Terms

**Person** \
A human being regarded as an individual; validation will rely on our strict Humanity Proof Mechanism 

**Quadratic voting** \
A voting mechanism that allows a single person to repeatedly vote for the same option to express the strength of their will, but with diminishing returns. For example, 1 vote may require 1 $RDAO, then 2 votes will require 4 $RDAO, 3 votes will require 9 $RDAO, and so on. This voting mechanism is often favored by Vitalik Buterin. 

**Moloch voting** \
1 person = 1 vote 

**Quorum** \
The minimum percentage of members capable of voting that must participate in a voting proposal to make it valid 

**Delegation** \
People may delegate their $RDAO votes to representatives; there will be a cap on the number of moloch and quadratic votes that may be delegated to a single representative. 

**Veto** \
Intended as a last resort to ensure obviously harmful governance proposals are not passed; would require a Moloch majority approval from the Core Team and DAO Council. Veto power would be revoked in a subsequent Voting proposal when deemed safe.

 

## Humanity Proof Mechanism

To ensure malicious actors or bots do not manipulate voting outcomes, we will leverage a system for individuals to confirm their humanity. 

Gitcoin uses the following authentication interface, where users can complete various items to reach a certain number of "points" that will help confirm their humanity.

<figure><img src="/files/17mnGyM2v02MRIE8DKRp" alt=""><figcaption><p>This shows just a few of "stamps" that can be used to verify humanity</p></figcaption></figure>

&#x20;

## Proposal and Voting Process

<figure><img src="/files/TyaEK9YzLJpRYe3PIUjL" alt=""><figcaption><p>RugDAO Proposal Voting Process</p></figcaption></figure>

&#x20;

## Voting Structure by Proposal Type

<figure><img src="/files/10KHstjFFTeQxrjPOoDM" alt=""><figcaption></figcaption></figure>

&#x20;

## Voting Proposal Requirements

Future proposals to change the voting structure for various proposal types will require a minimum amount of information in order to be considered. See the following guidelines, which are similar to the columns in the Voting Matrix above.&#x20;

**{**

**“proposal\_type": "",** \
**"title": "",** \
**"summary": "",** \
**"voting\_structure": "",** \
**"sponsorship\_details": "",** \
**"quorum”,** \
**“votes\_needed": "",** \
**"comment \_duration": "",** \
**"voting\_duration": "",**

**}**

<br>


---

# 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://wiki.rug.fm/rug-radio/rugdao/frameworks/voting.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.