[RFC] - Wonderland Governance Framework Amendment
Provide better timeframes, transparency and implement a better way to vote on treasury management proposals.
This proposal aims at improving the transparency and efficiency of the current governance process by introducing minimum requirements and reducing existent timeframes.
- Reduce and implement minimum timeframes.
- Provides minimum requirements for steps before a proposal is voted.
- Implement Treasury Management Proposals (TMP)
|Governance Stage||Min. Timeframe||Quorum||Views||Votes|
|DAO Discussion||2 days||20 users||300||60%|
|Request for Comments||3 days||40 users||500||60%|
|Wonderland Improvement Proposal||3 days||N / A||N / A||N / A|
|WIP Vote||4 days||5k TIME||N/A||50%|
|Treasury Management Proposal||N/A||N/A||N/A||50%|
|TMP Vote||4 days||5k TIME||N/A||50%|
The number of users require for the minimum requirement met excludes users involved in the proposal. Comments, likes and/or poll votes can be used towards the quorum.
Polls and official votes should always have an option to maintain the status quo.
In consultation with the delegated official1 , elected officials may bypass the DAO Discussion step when submitting a proposal. If the proposal goes against or in a different direction than an already voted proposal, the DAO Discussion should not be skipped.
RFCs, WIPs and TMPs are to be reviewed and approved by the delegated official1 to ensure the proposals are clear, coherent and DAO guidelines followed. When submitted by the delegated official1 they must be reviewed by another elected official for approval.
Minimum requirements can be adjusted at the discretion of the delegated official1 following an informal discussion with the community. The poll should be announced and last at least 4 days.
1Until voted otherwise, forum moderators and administrators will act as the delegated officials enforcing the framework.
A TMP is a request to alter specific parameters regarding the management of the treasury, renew previously approved budgets, or assist treasury personnel with decision making processes when required by previous governance such as WIP 14 and the current Treasury Allocation Proposal.
These proposals are to be formally voted on by the DAO. However, unlike a WIP, the TMP does not need to go through the complete governance process. A TMP should be posted by an elected official and should explain the reason for the TMP as well as the available options proposed to the DAO.
Due to a TMP bypassing the regular governance process, there needs to be certain limits to prevent the mismanagement of the treasury funds by rushing the process.
A TMP should not be used to modify terms of previously voted WIP that are not directly related to treasury management or does not allow that flexibility (e.g. liquid staking, redemption, $SIFU investment, etc).
A TMP should not be used for seed investments or buying specific tokens.
- A TMP could be used to ask the DAO to make a specific asset a strategic asset without voting on how much should be bought.
In a situation where there is a conflict of interest, the regular governance process should be followed to ensure due diligence is done.
If it is unclear whether a certain treasury management situation can be dealt with using a TMP, the guidelines should be clarified and the regular governance process used.
There are limited requirements to implement this proposal.
Current voting tool’s (Snapshot) settings will have to be adjusted. Moderators and elected officials will need to adjust to the new requirements.
- Yes, amend framework
- Yes, but see my comment(s) below
- Make No Changes
Since an RFC is a “work in progress” Proposal, not all of these points need to be filled out from the beginning. They can be added over time as the RFC evolves into a mature Proposal.