This is the suggested template for new M03IPs.
Note that a M03IP number will be assigned by an editor. When opening a pull request to submit your M03IP, please use an abbreviated title in the filename, m03ip-draft_title_abbrev.md.
M03IP: <to be assigned>
Title: <M03IP title>
Author: <list of authors' names, crypto wallet addresses, GitHub or chat usernames, and optionally, email addresses>
Status: Draft
Created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
Requires (*optional): <M03IP number(s)>
Replaces (*optional): <M03IP number(s)>
Superseded-By: <M03IP number(s)>
Permalink:
"If you can't explain it simply, you don't understand it well enough." Provide a simplified and layman-accessible explanation of the M03IP.
A short (~200 word) description of the technical issue being addressed.
The motivation is critical for M03IPs that want to change the world. It should clearly explain why the existing structure and function of civilization is inadequate to address the problem that the M03IP solves. M03IP submissions without sufficient motivation may be rejected outright.
The technical specification should describe in technical detail any new feature, functionality, process, policy, business model, product, service, or other cryptoeconomic system enhancement being proposed. The specification should be detailed enough to allow competing, interoperable implementations by any software developer or Decentralized Hedge Fund Manager who decides to implement the M03IP.
The rationale fleshes out the specification by describing what motivated the cryptoeconomic engineering design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the proposal addresses international regulatory compliance concerns. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.
The implementations must be completed before any M03IP is given status "Final", but it need not be completed before the M03IP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of technical details.
Copyright and related rights waived via CC0.