Meta-Proposals (DMP)
The DMP process for changing governance and protocol-level decisions
Meta-Proposals — DMPs — are the mechanism for changing how governance itself works. They are also used for protocol-level decisions that need a formal onchain signal from token holders.
DMPs are suggested changes to the governance process. The purpose is to make governance self-correcting while keeping the process transparent.
Where DMPs live
Written and discussed: forum.dhedge.org
Voted on: Snapshot (vote must link back to the DMP, and the DMP back to the vote)
Format
Each DMP is a forum post with this structure:
Title:
DMP-Xwhere X is the next sequential numberHeader fields: Author, Created (YYYY-MM-DD), Status
Sections: Motivation, Description
Discussion happens in the comments on the forum post.
States
A DMP is always in one of five states:
Draft
Proposal made, but not voted on
Under Review
A vote is ongoing
Included
Passed vote
Rejected
Failed vote
Superseded
Replaced by a new proposal
Once voting concludes, DMPs are immutable. Any change requires a new DMP that supersedes the old one.
Voting
Minimum voting period: 2 days
Voting power: DHT balance in the voting wallet, read on Snapshot
Voting happens on Snapshot by connecting the wallet that holds the DHT
How to propose
Draft the proposal on forum.dhedge.org with the title
DMP-Xand the required header fieldsLet the community discuss it in the thread
Move it to a Snapshot vote once the thread has converged
Link the vote back to the DMP and the DMP back to the vote
On pass, the DAO multisig executes
What DMPs are used for
Changes to the DMP process itself
Changes to fee structure or fee split
Treasury actions: reallocations, liquidations, major spends
Grants programs and partnerships
Anything that needs a formal, recorded token holder signal
Last updated