Revision History
These Guidelines are superseding:
The rules below can only be changed by a DAO vote
Proposals
Policies
- Voting is done on Snapshot.
- The SSV token is used for voting on all SSV Network decisions.
- A minimum of 100 SSV Tokens is required to start a vote. Participation in a vote requires any number of SSV tokens.
- [DIP-32] A minimum of 1.75% of the total SSV supply must take part in the vote for quorum to be met.
- A vote on a proposal is 7 days long, requiring a simple majority to be accepted.
- [DIP-2] Execution of passed votes is done by the Multi-Sig Committee. If the execution details are unclear, the multisig committee will indicate so. The proposer will have 7 days to respond and resolve the issue.
- If a proposal depends on a previous proposal, the dependency proposal must be passed and executed before the execution of the original proposal.
Life Cycle
- A proposal should start its life as a forum discussion to receive community consensus.
- A proposer should write a proposal following the best practices established by other successful proposals to get accepted by the community and increase the probability of success.
- [DIP-32] Alternatively, the proposer can use the [TEMP CHECK] route to have a staged process and acquire support in drafting and promoting the proposal.
Delegation
- Apply as a Delegate for SSV Network DAO to become a delegation target and acquire voting power.
- [DIP-40] Delegators can split voting power across multiple delegates.
Governance Hub
Check out our Hub for a high-level overview of the DAO Governance and its tooling landscape.