bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 8쪽 중 2쪽
provement Proposals): Fund Allocation, Partnership Consideration, and Process or Informational. Any proposal that requires resubmission must be classified accordingly.
<mark style="color:red;">**Fund Allocation**</mark>
Fund allocation proposals are for the utilization of the SuperVerse DAO Treasury.
<mark style="color:red;">**Fund Allocation Resubmission**</mark>
Resubmitted proposals for utilization of the SuperVerse DAO Treasury.
<mark style="color:red;">**Partnership Consideration**</mark>
Partnership consideration proposals aim to highlight opportunities where collaboration with other projects or individuals can benefit the ecosystem.
<mark style="color:red;">**Partnership Consideration Resubmission**</mark>
Resubmitted partnership consideration proposals that aim to highlight opportunities where collaboration with other projects or individuals can benefit the ecosystem.
<mark style="color:red;">**Process and Informational**</mark>
Process or informational proposals are for changes to an existing process, changes to the implementation, or general information for the community. Examples include changes to existing DAO procedures, guidelines, or the use of tools by the DAO.
<mark style="color:red;">**Process and Informational Resubmission**</mark>
Resubmitted proposals for changes to an existing process, changes to the implementation, or general information for the community. Examples include changes to existing DAO procedures, guidelines, or the use of tools by the DAO.
### <mark style="color:yellow;">SVIP Template</mark>
In order for a proposal to be considered, it must include the following criteria (Proposal Criteria) unless otherwise specified.
* <mark style="color:red;">**Summary**</mark> - A few sentences summarizing the proposal
* <mark style="color:red;">**Community Incentive**</mark> - Explain why the SuperVerse community should implement the proposal
* <mark style="color:red;">**Risks**</mark> - Highlight any potential risks involved with implementing the proposal
* <mark style="color:red;">**Rationale**</mark> - Explain how the proposal benefits the future of the project, furthers the SuperVerse mission, and aligns with the guiding values
* <mark style="color:red;">**Key Terms**</mark> - Include an explanation of any unique terms included within the proposal – only if applicable
* <mark style="color:red;">**Specifications**</mark> - Provide a detailed breakdown of the platforms and technologies required to implement the proposal
* <mark style="color:red;">**Steps to Implement**</mark> - Provide the steps to implement the proposal including the number of resources and the associated cost of each step
* <mark style="color:red;">**Timeline**</mark> - Include all relevant details in regard to timing. This should include the projected start date, completion date, and milestones along the way
* <mark style="color:red;">**Overall Cost**</mark> - Be clear on the total cost to implement the proposal
The SVIP Author can add additional fields or details to the SVIP template if necessary to fully communicate the intentions, specifics, and implications of the proposal.
Proposals that did not make it through the respective approval process and are being resubmitted should also include:
* The link to the original proposal
* The reason(s) it was not approved previously
* The changes that have been made and the reason it should now be approved
## <mark style="color:yellow;">Proposal Phases</mark>
<mark style="color:red;">**Phase One:**</mark> SVIP Idea
An idea is submitted by the community as a post in the forum. The person or persons submitting the SVIP idea are the SVIP Authors. More than one DAO member can work on an SVIP idea, but it should only be submitted once. The community then has the opportunity to provide feedback via comments on the forum. The SVIP Authors can propose changes to the original idea, but only through comments on the forum. To keep discussions transparent, the SVIP Authors may not change the original post.
<mark style="color:red;">**Phase Two:**</mark> SVIP Draft
When SVIP Authors determine they have enough information to draft a proposal, an admin engaged by SuperVerse will close the topic on the forum and send the proposal template to the SVIP Authors along with the next steps for submission. The SVIP Authors should consider including any community feedback that furthers the idea as part of their draft before continuing. The admin may inform the SVIP Authors of any necessary changes required to comply with the DAO-approved guidelines. At this time, an SVIP Author will be required to authenticate their wallet to prove they have met the staking requirements for submitting a proposal. If the SVIP Authors do not respond to all requests from the admin within 30 days, the SVIP draft will be automatically rejected. If and when the admin confirms the SVIP draft complies with the DAO-approved guidelines, a number will be assigned to the SVIP for identification purposes. From that point on, the SVIP is referred to as “SVIP-#; (Name) - (Category)”. For example, this first SVIP is “SVIP-1: Proposing the DAO - Process and Informational”.
<mark style="color:red;">**Phase Three:**</mark> SVIP Analysis Report and Moderation
The SVIP Draft is reviewed by an admin team engaged by SuperVerse. The admin team will analyze the proposal and provide a report detailing costs, steps to implement, legal considerations, third-party review requirements, potential conflicts of interest, and any further complications that have been identified. Knowing that some SVIP Authors may be submitting drafts with little to no resources, this phase is important to ensure that DAO members have enough information about proposals to make informed decisions when voting. During this time, the admin team also decides if the proposal adheres to the DAO-approved guidelines. If approved, it becomes a Pending SVIP and moves to Phase Four. If not approved, it is eligible for resubmission except in extreme circumstances. SVIP's that violate the law, include misleading information, or have reasonable suspicion of fraud will not be eligible for resubmission.
<mark style="color:red;">**Phase Four:**</mark> SVIP Designation
Pending SVIPs that have passed SVIP Moderation are designated as “Ready to Vote” or “Needs Administrative Review”.
The “Ready to Vote” designation is given to a pending SVIP whose details meet the proposal criteria and are of no risk to the well-being of the DAO. Any Pending SVIP that is designated as “Ready to Vote” will go to the board for final approval. If final approval is given by the board, skip to Phase Six. In a case where the board does not approve the Pending SVIP, clear rationale will be provided to the SVIP Authors of the proposal and the proposal will be eligible for resubmission.
The “Needs Administrative Review” designation is given to a Pending SVIP whose costs, content, or implications are considered complicated or a potential risk to the well-being of the DAO. Any Pending SVIP that is designated as “Needs Administrative Review” must go through Phase Five.
<mark style="color:red;">**Phase Five:**</mark> SVIP Admin Review (If Applicable)
For Pending SVIPs that have been designated as “Needs Administrative Review,” the Board will determine whether clarification or action is required before moving a Pending SVIP to Phase Six. If clarification or action is not needed, the Pending SVIP is designated as “Approved for Voting” and proceeds to Phase Six. If the Board decides to return a Pending SVIP for further clarification or action, they must provide a clear explanation of why and designate it as either “Return for Clarification” or “Return for Reconstruction.”
Reasons to tag as “Return for Clarification” may include but are not limited to:
* The cost to implement is unclear or not able to be calculated
* The proposal would use more than 5% of the DAO treasury
* The proposal conflicts with another proposal
Reasons to tag as “Return for Reconstruction” may include but are not limited to:
* The proposal conflicts with the mission and values of the DAO
* The proposal is at odds with the well-being of the DAO
* Violations of law, or against the advice of counsel for Super Foundation
* Reasonable suspicion of fraud or other misleading information
<mark style="color:red;">**Phase Six:**</mark> SVIP Vote
Drafts that have passed their respective approval processes will go live for voting on Snapshot. Once live on Snapshot, SVIPs are open to voting for six days. SuperVerse admins are the only ones that can post SVIPs to the voting tool, because they must confirm that each one has gone through the correct approval process.
<mark style="color:red;">**Phase Seven:**</mark> SVIP Determination
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. In all other cases, SVIPs are moved to one of two Final SVIP categories. Rejected Final SVIPs can be resubmitted via the appropriate Resubmission Template if the SVIP Author contacts an admin. Accepted Final SVIPs move into SVIP Implementation.
<mark style="color:red;">**Phase Eight:**</mark> SVIP Implementation
For Accepted Final SVIPs, implementation will begin based on the steps outlined in the SVIP template. The admin engaged by the Super Foundation is responsible for ensuring this happens, but is not responsible for doing it themselves.
### <mark style="color:yellow;">Proposal Conflicts</mark>
If a suggested proposal directly conflicts with a proposal that is currently up for a vote, the second proposal should not go for a vote until a decision is made on the first proposal to avoid approval of opposing requirements.
A suggested proposal that directly conflicts with another approved proposal cannot go to vote for three months after the original proposal has been implemented to avoid wasting community assets.
# Voting
The goal of the SuperVerse DAO’s voting process is to make voting transparent, fair, and low-cost for the community. That is why Snapshot is the proposed voting tool for the DAO. DAO members can participate in the decision-making of the DAO through a voting system on Snapshot. The voting mechanism will be continuously monitored to ensure it meets all the requirements of the DAO.
## <mark style="color:yellow;">Voting Process</mark>
1. SuperVerse admins are responsible for posting SVIPs to Snapshot or the DAO approved voting tool. SVIPs are only posted after ensuring that each one has gone through the appropriate approvals process. Once the SVIP is posted, the six-day voting window commences.
2. SuperVerse DAO members vote on Snapshot. One staked $SUPER is equal to one vote. Votes cannot be divided into fractions and the total number of votes shouldn’t ever exceed the number of tokens minted. The number of votes will be rounded down if a fractional number of tokens is owned by the voter (i.e., 100.1 tokens will result in 100 votes, and so will 100.9 tokens). 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 — you may vote “Against” to encourage the SVIP Author to resubmit the SVIP after making changes.
3. The voting for each proposal will be for six days and closed by an admin once the voting has closed.
4. Proposals that receive a minimum engagement of 5% of the circulating supply of $SUPER and have at least 60% of votes “In favor” of the proposal are moved into implementation. Proposals that are rejected will have the chance to be resubmitted via the appropriate Resubmission Template if the SVIP Author contacts an admin to initiate this process. If by the Vote Close Time the SVIP has not gotten any votes or is tied, it will be designated as “Stalled” and be eligible for Resubmission.
# Reference Guide
<mark style="color:red;">**SVIP - SuperVerse Improvement Proposal**</mark> - A formal document proposing a new feature, project, goal, or change to any proposal that has already been implemented.
<mark style="color:red;">**SVIP Idea**</mark> - This is the first step in the process of creating an SVIP. The SVIP idea is presented to the community for feedback for a seven-day period.
<mark style="color:red;">**SVIP Draft**</mark>** -** The second step in the process of creating an official SVIP. An SVIP draft must be submitted directly to an admin using a predetermined template.
<mark style="color:red;">**SVIP Template**</mark>** -** The required SVIP Template for SVIP Proposals.
<mark style="color:red;">**SVIP Author**</mark>** -** The DAO member or members behind the SVIP. The SVIP Author is responsible for incorporating community feedback, answering any questions or points of clarification regarding the proposal, and following the steps of the SVIP proposal process.
<mark style="color:red;">**SVIP Categories**</mark>** -** the SVIP Author, in partnership with an admin, selects one of the following categories for the SVIP based on the intent of the proposal:
<mark style="color:red;">**Fund Allocation Proposal**</mark>** -** Fund allocation proposals are for the utilization of the DAO fund.
<mark style="color:red;">**Partnership Consideration Proposal**</mark>** -** Partnership consideration proposals aim to highlight opportunities where collaboration with other projects or individuals can benefit the ecosystem.
<mark style="color:red;">**Process and Informational Proposal**</mark>** -** Process or informational proposals are for changes to an existing process, changes to the implementation, or general information for the community. Examples include changes to existing DAO procedures, guidelines, or the use of tools by the DAO.
<mark style="color:red;">**Resubmission Proposal**</mark>** -** a proposal that was previously submitted but did not pass due to initial rejection by admins or the Board, or by not passing a vote. All proposal categories have a special template for resubmission that the SVIP Author must link to the original proposal, clearly state why it did not pass, and clearly explain how the resubmission is different.
<mark style="color:red;">**SVIP Analysis Report**</mark>** -** A report conducted by a project management team engaged by the Super Foundation to ensure that all costs, steps to implement, legal considerations, third-party review requirements, potential conflicts of interests, and any further implications have been properly vetted. This is considered to be a service for the community given that SVIP Authors will be submitting SVIP Drafts with little to no resources.
<mark style="color:red;">**SVIP Moderation**</mark>** -** The act of reviewing an SVIP Draft to determine whether or not it meets the predetermined and DAO-approved guidelines. If an SVIP passes the SVIP Moderation phase, it becomes a Pending SVIP.
<mark style="color:red;">**Pending SVIP**</mark> - The SVIP status after it passes the SVIP Moderation phase.
<mark style="color:red;">**Post-Moderation Designation**</mark>** -** The process of designation of all Pending SVIPs that have successfully been through the SVIP Analysis Report and SVIP Moderation phases. There are two designations given at this stage: 1) “Straight to Vote,” which is for any Pending SVIP where costs, content, and implications are considered to be straightforward and of no risk to the well-being of the DAO. 2) “Needs Administrative Review,” which is for any Pending SVIP with costs, content, or implications that are considered to be complicated or a potential risk to the well-being of the DAO and therefore must be reviewed by the Board of the DAO.
<mark style="color:red;">**Administrative Review**</mark>** -** The process of evaluating Pending SVIPs that have been tagged as “Needs Administrative Review” to determine whether they should be halted or sent to vote by the community.
<mark style="color:red;">**Return for Clarification**</mark>** -** A type of administrative classification that requires the SVIP Author to clarify certain information regarding the Pending SVIP. This classification would be given in cases such as cost to implement being unclear, proposing to utilize a larger percentage of the Ecosystem Fund than is justified based on the value it would provide to the community, or being in direct conflict with an active SVIP.
<mark style="color:red;">**Return for Reconstruction**</mark>** -** a type of administrative classification that requires the proposer to restart the proposal submission process because the Pending SVIP violates DAO-approved requirements, or in cases of violation of the law, reasonable suspicion of fraud or other misleading information, or the pending SVIP being at odds with the mission, values, or well-being of the Foundation or DAO.
<mark style="color:red;">**SVIP Vote**</mark>** -** An SVIP that has passed all required approval stages and is launched for the community to vote on it. 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 voter is against implementing the SVIP exactly as-is — voters may vote “Against” to encourage the SVIP Author to resubmit the SVIP after making changes.
<mark style="color:red;">**Final SVIP**</mark>** -** An SVIP that has completed the voting process. There are two subcategories here: Accepted and Rejected.
<mark style="color:red;">**Implementation of Accepted SVIP**</mark>** -** The process of implementing an SVIP that has met the voting requirements and has been accepted by the community via a vote, based on the predetermined steps laid out in the SVIP Draft/SVIP Template and SVIP Analysis Report phases.
# DAO Proposals Passed
<mark style="color:yellow;">SVIPs that have been voted on and approved by $SUPER token holders:</mark>
{% content-ref url="/pages/g6PoWyEo7TaNvZ37lo2H" %}
[SVIP-1](/governance/dao-proposals-passed/svip-1)
{% endcontent-ref %}
{% content-ref url="/pages/3I6KTzuIr9kzTW88ZEvJ" %}
[SVIP-2](/governance/dao-proposals-passed/svip-2)
{% endcontent-ref %}
{% content-ref url="/pages/KP8ah5VIr6n5wT5XMI38" %}
[SVIP-3](/governance/dao-proposals-passed/svip-3)
{% endcontent-ref %}
{% hint style="info" %}
This vote ended on December 5th, 12pm PST and can be seen on [snapshot.org.](https://snapshot.org/#/superversedao.eth)
{% endhint %}
# SVIP-1
{% 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;">Proposing the DAO</mark>
**Category:** Process and Informational
**Submitted By**: Thare
<mark style="color:red;">**Summary:**</mark>
This document proposes the structure of a decentralized autonomous organization (DAO) governed by $SUPER holders staking within the designated DAO pools.
<mark style="color:red;">**Community Incentive:**</mark>
The SuperVerse DAO community will have the power to submit proposals and vote on the ideas they feel are most beneficial for the project.
The guiding values of SuperVerse DAO are:
* Equality: One staked $SUPER = one vote
* Transparency: We created a process that is clear and visible to our community.
* Collective Responsibility: We act in the best interest of the future of the project.
* Innovation: We strive to inspire the next trend.
<mark style="color:red;">**Rationale:**</mark>
The SuperVerse DAO is a community of Web3 enthusiasts who are inspired by a common 프로젝트로 돌아가기