Search…
πŸ”’
Step-by-Step
Alright, let's break this Governance Process down even further.

Workflow

1. Discord & Forum

This is an informal process to gauge community interest in a potential SW DAO proposal.
Here are some questions a proposer might want to answer:
  • Am I able to informally get any traction for this proposal in the Discord?
  • Has this proposal been tried before?
  • How does this proposal get the community closer to achieving its stated goals?
  • What trade-offs are implicit in this proposal's adoption?

2. Create an SW DAO Proposal

Once a contributor feels they have a rough consensus that their SWIP is valuable, original, and achievable, they should submit either a SWIP based on the SWIP Template on the SW DAO governance forum.

3. Editor Review & SWIP Number Assignment

Once a SWIP Editor has reviewed the proposal for basic adherence to SWIP guidelines, the editor will create a corresponding entry in the SW DAO GitBook, assign the SWIP a number, and create a corresponding discord channel for discussion.

4. Discussion and Minimum Waiting Period

The forum is the formal area to debate the merits of each SWIP. While the SWIP is on the forum in 'Draft' state, the SWIP author is free to make changes to the proposal. Once the SWIP author is satisfied with the proposal, they should change the proposal status from 'Draft' to 'Proposed', and contact a SWIP editor to schedule a snapshot vote.

5. Calling a Vote

All SWIPs are confirmed or rejected by the SW DAO via Snapshot Vote.
The SWIP author is responsible for deciding a snapshot vote date with the following criteria in mind:
  • The snapshot voting period may not begin until at least 48 hours after the SWIP has been proposed.
  • The SWIP has a voting period of 72 hours where token holders may vote FOR or AGAINST.
  • For Standard SWIP and meta-governance votes to pass
    • 20% of circulating SWD tokens must participate
    • >50% must vote FOR.
  • For a Product Addition SWIP to pass
    • 30% of circulating SWD tokens must participate
    • 60% or more must vote FOR.
Should we have 3 or 4 voting options and none clear the 50% hurdle we will host a follow-up vote 7 days after which will repose the same prior question but only with the two most voted for options.

6. Post Voting Process

After the Snapshot voting period has concluded a SWIP Editor will tally votes and update the GitBook SWIP record with the related voting data. If a proposal has passed, the SWIP is moved from proposed to approved. If a proposal is rejected the SWIP may be moved to rejected or back to WIP to be revised for future consideration.

8. Implementation

In the early stages of SW DAO, approved SWIPs will be executed via multisig where necessary.

Resources

​
​
Copy link