MIMD0 - Process Doc (Working)

Marginfi Improvement Document (MIMD) Overview

Summary MIMD0 establishes the framework for all future Marginfi Improvement Proposals (MIMDs), providing essential templates, processes, and guidelines for participation.

Framework Overview

  • MIMD0c1: Definitions - Outlines core concepts of the MIMD Framework.
  • MIMD0c2: Lifecycle of MIMDs - Details stages from creation to conclusion.
  • MIMD0c3: Components and Types - Describes MIMD components and their classifications.

Purpose To enable Marginfi’s transition to a fully decentralized entity, a structured decision-making process is essential. The MIMD Framework aims to standardize interactions for governance participants, facilitating clear and effective governance.

Details

  • MIMD0c1: Framework Definitions
    • MIMDs are formal documents for governance decisions.
    • Marginfi MAMAs assist in the MIMD process.
    • Subproposals are specific instances within the MIMD framework.
  • MIMD0c2: Lifecycle
    • From conception in the forum to formal approval or rejection.
    • Involves community feedback and a formal submission process.
  • MIMD0c3: Components and Types
    • Differentiates between general and process components.
    • Outlines the process for creating and managing subproposals.

Process Flow

  1. Conception: Proposal posting and initial support.
  2. Approval: Formal number assignment and repository merging.
  3. Feedback: Community review and author revisions.
  4. Submission: Official entry into the governance cycle.
  5. Decision: Voting and final status (Accepted/Rejected/Obsolete).

Subproposals

  • Follow similar processes with specific templates and periods defined by their parent MIMD.

Naming Conventions

  • Components: MIMDXcY (X=parent MIMD, Y=component number).
  • Subproposals: MIMDXcY-SPZ (Z=subproposal number).
3 Likes

Decentralisation matters in defi.

2 Likes

There was a request in telegram to rename from ‘MIMD’ to ‘MID’.

1 Like

This overall looks good to me - and I’m excited to do what we can here while we set up formal governance infrastructure.

Practically speaking, my understanding here is that the process flow goes something like:

  1. On this community forum Conception: Proposal posting and initial support.
  2. On github Approval: Formal number assignment and repository merging.
  3. On github Feedback: Community review and author revisions.
  4. For now, approved and merged. In the future, on governance infra Submission: Official entry into the governance cycle.
  5. For now, approved and merged. In the future, on governance infra Decision: Voting and final status (Accepted/Rejected/Obsolete).

Is that correct?

2 Likes

Yes, your breakdown here is what I was thinking, too.

Potentially a Realms like infra for putting proposals up to a vote (i.e. Realms)

Although, I personally prefer something like Nouns DAO for voting on props and giving feedback. Feels more transparent and involved. Here’s my fav version of their client: https://www.nouns.camp/

1 Like