Summary
This proposal provides guidelines for submitting, voting on, and executing proposals at Mangrove DAO. It aims to streamline the governance process, ensuring clarity and consistency in decision-making within the DAO.
Rationale
Establishing a well-defined governance process is essential for Mangrove DAO’s success. A clear framework ensures trust and legitimacy, as participants understand how decisions are made. It facilitates active engagement by providing clear guidelines on how to participate. Moreover, defining the current process allows for future improvements, ensuring the DAO remains adaptable and responsive to evolving needs.
Specification
1. Scope of General Governance
As established in MIP-1, Mangrove DAO’s general governance focuses on setting high-level goals and strategies. The execution of approved strategies and associated operational management decisions are delegated to the Councils. Mangrove DAO’s governance encompasses:
- Voting on strategic proposals initiated by councils or the community.
- Electing and funding councils.
- Authorizing special operations, such as exceptional spending beyond approved council budgets.
- Metagovernance: updating governance parameters.
2. Discussions
The Mangrove DAO forum’s general category is a space for open discussions on governance-related topics.
For more focused proposal development, participants should use the temp check category. This section is designed to gauge stakeholder sentiment and foster informal debate around specific ideas that may lead to formal proposals. Posts in this category should be structured as follows:
- Header: Includes the title, authors, and date of the post, and specifies the type as either ‘protocol’ or ‘ecosystem’.
- Body:
- Summary: A concise overview of the post’s content.
- Rationale: The reasoning behind the idea or question.
- Specification: Detailed description of the proposal or idea.
- Disclaimer (optional): Any necessary legal or contextual disclaimers related to the post.
- Next Steps (optional): Suggested actions or considerations following the discussion.
- Voting Options (optional): Set choices proposed (Yes/No/Abstain or Option 1,2,3/No/Abstain, depending on the proposal).
- Poll (optional): A poll can be offered when an idea is gaining traction but its proponents feel that they need a better sense of the community’s support.
3. Proposals
Proposals are formalized and posted by Councils in the proposals category of the Mangrove DAO forum. These proposals may originate from community-submitted ideas discussed in the temp check category or from the Councils themselves.
The structure of proposals mirrors that of the discussions in section 3.2, with the addition of a unique identifier. Proposals should include:
- Header: A unique ID constructed as ‘MIP’ followed by a chronological number (e.g., MIP1, MIP2), title, authors, date, and type (protocol or ecosystem).
- Body: As outlined in section 3.2, including summary, rationale, specification, and optional disclaimer and next steps.
Proposals must be submitted on the forum for comments and deliberation at least 5 days before any voting occurs (including the temp check period). This period is crucial for participatory deliberation, allowing proposals to be refined and improved based on community feedback. Once proposals are in the proposals category, authors are required to make all edits visible, either through tracked changes or by adding subsequent posts, ensuring that any modifications to the original proposal are easily identifiable.
4. Voting
Voting is conducted on Snapshot. Votes can be initiated either by council members, or by token holders with at least 5% MGVs held/delegated.
The following groups each represent one third of the total voting power in general governance:
- MGV Token Holders: Their voting weight is proportional to the number of held or vested tokens compared to the total circulating supply of MGVs.
- Builders Group: The voting power of Builders is based on an activity score reflecting their period of contribution and full-time engagement. Quadratic voting is applied to balance voting power discrepancies within the group.
- Pods Group: Comprising teams of strategists and developers, Pods initially have equal voting influence. Eventually, their voting power will be proportional to the economic value they generate for the protocol.
Key voting parameters:
- Proposals must be posted in the proposals category of the Mangrove DAO forum at least 5 days before voting on Snapshot.
- The voting duration should be a minimum of 5 days, include one weekend day, and not exceed 7 days.
- A quorum of 15% is required, calculated based on thrice the circulating supply of MGV tokens to equally empower Builders and Pods alongside MGV holders.
- Delegation is available to voters in every group.
5. Execution
Councils are responsible for implementing governance decisions. The Protocol Council handles ‘protocol’ type proposals, while the Ecosystem Council manages ‘ecosystem’ proposals. On-chain executable proposals are processed by the relevant Council’s multisig.
6. Changes to Governance Process
This governance process is subject to evolution. Any modifications require general governance approval.