About the Nexus Mutual DAO Proposals category

Governance Discussions Nexus Mutual DAO Proposals
1

A Nexus Mutual DAO Proposal (NMDP) is a proposal that can be used to submit a grant request for funding, create a new DAO team, or request a renewal and funding for an existing DAO team. These proposals are used to engage with the community, reach consensus, and distribute funding from the DAO treasury to fund projects and teams.

About NMDPs

Members can post, discuss, and vote on proposals using Snapshot. Proposals fall into one of the following categories:

NMDP governance process

Step 1: Post a Request for Comment (RFC)

Every governance discussion should start as a Request for Comment (RFC) to get feedback from the community.

RFCs should be posted for at least 12 days before they are raised as formal NMDPs. The feedback you receive can be used to revise your proposal ahead of an NMDP posting.

RFC format

  • Title. [RFC]: [Concise title for proposal]. For example: [RFC]: Invest some of the mutuals funds in LIDO stETH

  • Summary. Short summary, no more than 250 words, of your proposal.

  • Rationale. Explain why your proposal is important: what problem does it solve?

  • Specification. The what and how of your proposal. What is the purpose of your proposal and how does it solve the stated problem, benefit members, or improve the protocol?

Step 2: Post an NMDP

When you write an NMDP, you should include the required information, which is specific to the NMDP type. At a minimum, you must include:

  • Title. NMDP: [Concise title for proposal]. For example: NMDP: Should we give BootNode a grant to design an ERC-4626 compliant covered vault?

  • Summary. Short summary, no more than 250 words, of your proposal.

  • Specification. The what and how of your proposal. What is the purpose of your proposal and how does it solve the stated problem, benefit members, or improve the DAO or protocol?

  • Budget request. If funds are being requested, then a breakdown of resources and expenses with line-item requests is required either in the main NMDP or a supplementary proposal.

  • Proposal status. Depending on what stage your proposal is in, you must include:

    • Stage. One of the following should be added: 1) Open for Comment, 2) Closed, 3) Open for voting, 4) Accepted, or 5) Rejected.
      • If you choose to conduct a signaling vote using Snapshot, please update status to Signaling Vote and link to that vote. Signaling votes can be used but are not required.
    • If it is in the Open for Vote stage, add the link to the Snapshot proposal

Review and discussion period

An NMDP should be open for review and comment for at least seven (7) days before transitioning your proposal to a Snapshot vote.

NMDPs can be in the open for comment stage for longer periods of time, but there is a minimum to ensure review, feedback, and discussion can occur before the proposal is moved to a Snapshot vote.

Step 4: Snapshot vote

After the necessary review period, the proposal can be put to a Snapshot vote. The Snapshot vote should include:

  1. Title. NMDP: [Concise title for proposal]. For example: NMDP: Should we give BootNode a grant to design an ERC-4626 compliant covered vault?
  2. Summary. Short summary, no more than 250 words, of your proposal.
  3. Budget request. If funds are being requested, then a breakdown of resources and expenses with line-item requests is required either in the main NMDP or a supplementary proposal.
  4. Link to the original NMDP as posted on the forum.

To learn more about how DAO proposal vote outcomes are processed, read the NMDP section in the documentation.