Meta Proposals
Motivation
dHEDGE Meta Proposals (DMPs) are suggested changes to the governance process. The purpose of this category is to make governance self-correcting, and changes to the governance process transparent.
This DMP will specify the DMP process which will be used to create a transparent and formal governance process for dHEDGE DAO.
The governance process should be accessible and simple as to not gatekeep contributions, and transparent as to ensure confidence and trust in the process.
Description
DCPs go through the following stages
Draft: Proposal made, but not voted on
Under Review: A vote is ongoing
Included: Passed vote
Rejected: Failed vote
Superseded: Proposal has been replaced by a new proposal
To be put to vote, a post must be made in forum.dhedge.org. As the proposal is made as a forum post, discussion may happen underneath the post.
The title of the DMP must start with DMP-X, where X is the DMP number (ie. DMP-1). The DMP number must increase in order (eg. a DMP posted after DMP-1 must be named DMP-2).
Under the title should be the header. Header fields include:
Author: Author of the proposal
Created: Creation date in YYYY-MM-DD
Status: Statuses include - Draft, Under Review, Included, Rejected, Superseded
The DCP must contain the following sections:
Motivation - The reason for making this change
Description - A description of what the change is
Once the post is created in this format, it can be put up to vote. The vote must link back to the DMP, and the DMP back to the vote. The voting period must be 2 days minimum.
DMPs are immutable. Once a DMP receives a passing or failing vote, the contents of the DMP are considered final or frozen. To make changes to a DMP at this state, a new DMP must be created that supersedes the original.
Last updated