🗳️Proposal, voting, election and other mechanics
An overview
Several consensus mechanisms, namely proposals, voting and elections allow the Perion SubDAOs and DAO modules to interact, while aiming to ensure all components of the DAO operate in the interest of every PERC holder.
Consensus levels
3 grades of consensus exist within DAO ecosystem in order to facilitate decentralised governance, below are the grades of consensus and when they are used.
Subcommittee consensus (SC)
Consensus at the Core SubDAO subcommittee level
What it means:
A internal subcommittee vote between all subcommittee members of a Core SubDAO
Subcommittee consensus during the Phase 1 governance rollout has significantly more guardrails to ensure fair consensus
Global subcommittee consensus (GC)
Consensus across all Core SubDAO subcommittees
What it means:
Consensus across all CoreSubDAOs
Aggreagation of Subcomitttee consensus votes
Community consensus (CC)
Allows all PERC stakers to vote
What it is
A vote between all PERC holders
Further details
Vote approval thresholds
In the case of all consensus methods, a vote is successfully approved if it achieves >50% of votes in favour of approval. In the case of community consensus, a minimum participation threshold of 10% of circulating PERC supply is required. The circulating supply may be referenced via CoinGecko.
Subcommittee votes do not carry a minimum participation threshold, which is unnecessary due to their small cohorts.
Abstaining
If a member of a subcommittee, or the community abstains from a vote, the threshold for >50% consensus is lowered. For example if once member of a 4 member subcommittee abstains a 3/4 approval threshold is reduced to a 2/3 threshold. The same logic applies for all types of voting within the DAO, whether GC, SC or CC.
Staking requirement
Any entity wishing to vote using the PERC in their wallet must stake it for a minimum of 1 month to participate in community consensus voting.
Subcommittee votes
Both global subcommittee consensus and subcommittee consensus require individual subcommittee members, or member organisations, to vote on submitted proposals. This voting capacity is enabled by whitelisting wallet addressed, key details as follows:
Upon successful election to a subcommittee, the wallet of that individual or entity attached to the subcommittee will be whitelisted for voting
Each subcommittee wallet will be controlled via an individual or entity, any one individual or entity may not control more than 1 voting wallet per subcommittee
Each whitelisted wallet has an equally weighted capacity to vote on snapshot governance decisions
Subcommittee size
Subcommittee size is a key component to ensuring the DAOs operations are efficient is a minimum 3, maximum 5 members, or member organisations, per subcommittee.
Tools utilised
All mandates and discussion will utilise a discourse.org forum, all voting will utilise a customised architecture with snapshot.org backend.
Governance mechanics
Proposals and voting exist at several points of the governance process, and function in the form of various mechanics. The initial mechanic types in use cover broad categories as outlined below.
Rollout
Governance mechanics will be rolled out in 2 distinct phases:
Phase 1 will include Funding, DAO modification and Independent validator elections
Phase 2 will include Elections and Additional SubDAO formation
Phase 1
The governance mechanics utilised in Phase 1 are outlined below:
Funding (GC/SC/CC)
Before a Core SubDAO receives Treasury assets, a proposal must be submitted and pass a multi-stage vote.
DAO modification (GC/SC/CC)
Being that the Perion DAO is a relatively new ecosystem, there may come a time where governance parameters should be updated, or new mechanics introduced. To integrate these updates to the DAO will require the same multi-step approval process as as funding mandate.
Independent validator elections (CC)
Electing the independent validator is a process that is wholly community governed.
Phase 2
Phase 2 governance mechanics are outlined below:
Electing (CC)
Submission of candidates and election for Core SubDAO subcommittees is a community-led process that requires submission of candidates and elections.
Should a Core SubDAO find that its duties become too great or that there would be benefit in segmenting the SubDAO into multiple Core SubDAOs, a process of subcommittee consensus, followed by global consensus is required.
Last updated