🚧DAO modification
Overview
Purpose:
Allow updates to the governance process
Allows a pathway to introduce new DAO features
Vote types used:
Templates
DAO modifications
Being that the Perion DAO is a relatively new ecosystem, there will likely come a time where DAO parameters will need to be updated, new mechanics introduced and new features added. Integration of updates to the DAO will require the same multi-step approval process as a funding mandate, ensuring the DAO is not adjusted unless there is overall consensus:
1. Creating and refining the mandate:
Anyone wishing to make improvements to the DAO, must develop a proposal outlining the changes.
Timeline and voting details:
The initial proposal development timeline is open ended
A commentary window of up to 7 days on the forum allows input from the community, subcommittees and independents
An adjustment window of up to 7 days allows the prposer(s) to adjust the mandate
2. Voting stage I: Subcommittee consensus
The Subcommittee consensus vote is significant during Phase 1 of the governance rollout, as detailed in the reference diagram. This vote aims to secure alignment between the subcommittees, the community of PERC holders and independent validator(s).
Timeline and voting details:
Once the proposal is complete, the 3-way vote is used to determine whether the proposal passes to the next phase
The voting window will be up to 72 hours
3. Voting stage II: Global subcommittee consensus
The process moves to admission to the treasury grant module, with a final vote whereby each SubDAO subcommittee votes to approve or deny the proposal. In order to achieve successful approval each Core SubDAO subcommittee votes internally to approve or deny the proposal, with the proposal passing if >50% of the Core SubDAOs subcommittees independently vote to approve.
Timeline and voting details:
The voting window will be 72 hours
A GC vote is used to determine whether the proposal passes
Further details
Budget
Should significant changes be required budget must be considered in the scope, works will be scoped by the Product SubDAO, and utilise Support SubDAO contributors.
Critical bugs
Any bugs that are deemed critical to the functioning of the DAO such as security and smart contract vulnerabilities will be updated as required without the need for a vote.
Last updated
