MIP: 01
title: Adopt a proper MaskedDAO Governance process
authors: drlorente97.eth
created: 2023-01-04

Simple Summary

This proposal details a process for creating Masked DAO governance proposals and putting them up to vote.

Abstract

This proposal provides a detailed structured process for Masked DAO governance proposals. Any individual or entity wishing to create a proposal and put it up to vote will need to go through those steps to ensure that its proposal is detailed enough to be voted on and its implementation enforceable.

Motivation

The motivation for this proposal is to ensure an orderly process of creating improvement proposals to ensure the quality of the proposals and to keep the Snapshot clean. This proposal was inspired by the Proof of Humanity DAO's HIP-5 which has proven to be effective.

Specification

Masked DAO Governance Process

The governance process will be carried out through Masked Improvement Proposals (MIP). These should be listed in a continuous, non-repeating manner (MIP-XX). The following guidelines should be followed to carry out these proposals.

Masked DAO proposal on Snapshot page must include two voting options: "Accept changes" and "Make no changes"

Duration: 5 days

Passing Requirement: For proposals to be accepted, there must be one outcome with a relative majority of votes in the Snapshot proposal. If the relative majority of votes on the proposal indicates the result Make no changes, the proposal will not be accepted and considered closed.

Format: All proposals must be created according to the template included below

Any snapshot proposal not following these guidelines can be considered non-binding.

MIP Template

MIP: <Number to be assigned>
title: <MIP title>
author: <a list of the author's or authors' name(s) and/or username(s), or name(s) and email(s)
created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
requires (*optional): <MIP number(s)>
replaces (*optional): <MIP number(s)>

Simple Summary

(Required)

If you can’t explain it simply, you don’t understand it well enough. Provide a simplified and layman-accessible explanation of the MIP.

Abstract

(Required)

A short (~200 word) description of the issue being addressed.

Motivation

(Required)

The motivation is critical for MIPs that want to allocate funding or change the Masked DAO. MIP posts without sufficient motivation may be rejected outright.

Specification

(Required)

The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow for it to be reasoned about by participants in the Masked DAO.

Implementation

(If necessary)

It must include all details regarding implementation, including: technical details, costs, implementation time, resources needed.