> For the complete documentation index, see [llms.txt](https://docs.superverse.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superverse.co/governance/dao-proposals-passed/svip-2.md).

# SVIP-2

{% hint style="info" %} <mark style="color:yellow;">Please note:</mark> Proposals SVIP-1, SVIP-2 and SVIP-3 <mark style="color:green;">**have been voted on and passed**</mark> by $SUPER token holders. Voting closed December 5th, 12pm PST which can be seen on [snapshot.org.](https://snapshot.org/#/superversedao.eth)
{% endhint %}

## <mark style="color:yellow;">Voting</mark>

**Category:** Process and Informational

**Submitted By:** Thare

<mark style="color:red;">**Summary:**</mark>

This document proposes the voting protocol for the DAO outlined in SVIP-1. Snapshot.org will be used initially for voting on improvement proposals. Proposals that have followed the respective guidelines and have been approved will be available for voting on Snapshot.

<mark style="color:red;">**Community Incentive:**</mark>

The goal of this proposal is to create voting infrastructure for SuperVerse DAO members to participate in the decision-making of the DAO. That is why Snapshot is proposed as the voting tool for the SuperVerse DAO. The benefits of the proposed voting system are:

* not requiring a gas payment
* ensuring transparency
* expanding governance participation to all SuperVerse DAO members

Without a voting system in place, arriving at a consensus on proposals would be centralized, with only a few people holding decision-making abilities. This proposal aims to avoid this result.

<mark style="color:red;">**Rationale:**</mark>

As the ecosystem evolves and expands, a well-defined system is required to gather new community ideas and provide a clear path for these ideas to be approved for implementation. A proposal process is foundational to this system becoming a reality. This proposal outlines a voting tool that seeks to balance the pros and cons of various voting approaches and to hold up the core of the SuperVerse DAO’s guiding values. This voting tool can be found below in the following specifications section.

### <mark style="color:yellow;">Specifications</mark>

Assuming SVIP-1 is approved, implement Snapshot as the voting tool for the SuperVerse DAO where:

* Only SuperVerse DAO members may vote
* New SVIPs that meet the required guidelines will be put to a community vote
* The voting opens immediately upon posting and is open for six days
* The voting options for a live SVIP are “In favor” and “Against.” Voting “In favor” means the voter is in favor of implementing the SVIP exactly as-is. Voting “Against” means the vote is against implementing the SVIP exactly as-is — one may vote “Against” to encourage the SVIP Author to resubmit the SVIP after making changes.
* If a live SVIP Vote has not received the minimum engagement of 5% of the circulating supply of $SUPER or at least 60% of the total votes “in favor” of the proposal, it will be designated as “Stalled” and be eligible for Resubmission
* Proposals that are approved by the members of the DAO are implemented by the SuperVerse DAO
* Only SuperVerse admins can post SVIPs to Snapshot because they must ensure that each one has gone through the correct approvals process

<mark style="color:yellow;">**Steps to Implement**</mark>

* Complete setup of the forum platform and settings
* Purchase ENS domain
* Create specific space on Snapshot
* Implement ecosystem-specific voting strategy
* Set administrator addresses
* Set voting rules
* Set restrictions in Snapshot so that only admins can launch proposals
* Open ratification of SVIP-1 and SVIP-2

<mark style="color:yellow;">**Timeline**</mark>

All steps have been prepared and ready to be implemented

<mark style="color:yellow;">**Overall Cost**</mark>

No cost to implement


---

# 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://docs.superverse.co/governance/dao-proposals-passed/svip-2.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.