MIP38: DAO Primitives State

MIP38: DAO Primitives State

Preamble

MIP#: 38
Title: DAO Primitives State
Author(s): @juanjuan
Contributors: @elprogreso, @iammeeoh
Type: Informational
Status: Formal Submission
Date Proposed: <2021-01-18>
Date Ratified: <yyyy-mm-dd>
Dependencies: MIP39, MIP40, MIP41, MIP4c2-SP10, MIP4c2-SP12
Replaces: n/a

References

N/A

Sentence Summary

DAO Primitives State is a MIP that keeps track of all the states related to Core Units, Budgets and Facilitators.

Paragraph Summary

DAO Primitives State is a MIP that keeps track of the current state related to Core Units, Budgets and Facilitators. The state of the Primitives is maintained in the DAO Primitives MIP. The Primitives cannot be modified through this MIP but by the corresponding dedicated MIP Component in the MIP Set.

Component Summary

MIP38c1: Core Unit State Maintenence
This component defines the Core Unit State list, its format and its upkeep.

MIP38c2: Core Unit State
The component that contains all of the DAO Primitives State, with Core Units as the key.

Motivation

This MIP lays down a basic structure based on Core Units (MIP39) capable of supporting the increasing complexity of the DAO and its continuous expansion. It also documents and keeps track of the state of the elements that make up this new structure and their dependencies.

Under its stripped-down, homogeneous nature, this structure avoids the hassle of ad-hoc implementations that are hard to analyze and interface.

Thinking forward, it also provides Governance with a straightforward process to fund teams beyond the dissolution of the Foundation.

Specification / Proposal Details

MIP38c1: Core Unit State Maintenence

This dataset contains all of the Core Units approved by the community, alongside the Core Units’ data. It includes:

  • Core Unit Mandates
  • Budget Implementation and Breakdown
  • Facilitator name, information, and commitment.
  • Key Dates

This dataset is updated by the MIP Editors when a subproposal from MIP39, MIP40, or MIP41 becomes accepted.

List Entry Template:


NAME-XXX

ID - XXX# (assigned by the Operational Support Core Unit or a MIP Editor)
Summary - 30 word max summary.
Date Ratified -
Mandate - MIP39c2-SPX
Budget Amount - xxx,xxx DAI / year
Budget Implementation - Manual/Simple/Advanced - MIP40c2-SPX
Budget Breakdown - MIP40c2-SPX
Facilitator A - Awes M. Example - MIP41c2-SPX
Facilitator B - Gre T. Example - MIP41c2-SPY


MIP38c2: Core Unit State

There are currently no active Core Units. Entry ‘EXMPL-000’ exists as an example for formatting Core Unit State Entries.


EXMPL-000

Example Core Unit - Provides a decent descriptive name for a Core Unit example.
Summary - Provides an awesome and great example of a Core Unit List template.
Date Ratified - 1970-01-01
Mandate - MIP39c2-SP0
Budget Amount - 100,000 DAI / year
Budget Implementation - Manual - MIP40c2-SP0
Budget Breakdown - MIP40c2-SP0
Facilitator A - Awes M. Example - MIP41c2-SP0
Facilitator B - Gre T. Example - MIP41c2-SP00





Edit: Incorporated feedback for clarity, added to my github (accepting PRs) and also PRed the Maker Github.
Thanks to @blimpa, @Deimos, @LongForWisdom, and everyone else that helped with the revision.
Edit2: removed the MIP4c2-SP11 from dependencies, moved to formal submission.

7 Likes

Thoughts

  1. Title can be better, it wasn’t immediately clear. Maybe MIP38: State of Core Units?
  2. What other DAO primitives are there beyond Core Units? It seems this MIP is designed to include more in the future.
3 Likes

Should go into more detail. This shouldn’t be solely the benefits of , but rather why it’s important to do this thing and why we’re doing this important thing in this way and not some other way.

I would suggest splitting this into components for each of the core primitives. IE, a list of Facilitators, a list of Core Units, and a list of approved budgets. I’m aware that many of these will contain duplicate information, but it would be nice for governance / any users to be able to see a clear list of all the facilitators, all of the core units, all of the budgets, etc separately.

Who is responsible for keeping this MIP up to date? What is a budget implementation versus a budget breakdown? Would a glossary or definitions component be useful here? I think a one sentence explanation with a link to the MIP containing the full details would be useful.

Lists of elements and/or long form text don’t lend themselves well to a list entry with a defined structure. I feel like you could maybe avoid this via having separate lists for each DAO primitive. For example, the facilitator list would list which Core Units the Facilitator was heading, the details of which could then be in the Core Unit list.

Not sure what this is at this point. Again, glossary might be useful.


I would suggest that each facilitator be required to publish a permissions address that can be used as keys for any multi-sig or permissions related to their Core Unit(s). These should be included in the list of Facilitators.

Edited incorporating feedback + PR in github.