index.html

---
layout: default
title: mStable Improvement Proposals
---

<h1 class="page-heading">
  mStable Improvement Proposals
  <a href="https://discord.gg/y2r3jXm" rel="nofollow"
    ><img src="https://img.shields.io/discord/525087739801239552" alt="Discord"
  /></a>
  <a href="/last-call.xml"
    ><img src="https://img.shields.io/badge/rss-Last Calls-red.svg" alt="RSS"
  /></a>
</h1>

<h2>MIP</h2>
<p>
  mStable Improvement Proposals (MIPs) describe standards for the mStable
  platform, including core protocol specifications, client APIs, and contract
  standards.
</p>

<h2>MCCP</h2>
<p>
  mStable Configuration Change Proposal (MCCPs) describe a standard for
  modifying one of the system configuration variables
</p>

<h2>TDP</h2>
<p>
  Treasury DAO Proposals (TDPs) describe standards for the Treasury DAO for
  allocating resources from the mStable's Treasury
</p>

<h2>Contributing</h2>
<ol>
  <li>
    Review <a href="MIPS/mip-1.html">MIP-1</a>,
    <a href="MCCP/mccp-1.html">MCCP-1 or TDP-XX.</a> .
  </li>
  <li>
    Fork the <a href="https://github.com/mstable/MIPs">repository</a> by
    clicking "Fork" in the top right.
  </li>
  <li>
    Add your Proposal to your fork of the repository. There is a
    <a href="https://github.com/mstable/MIPs/blob/master/mip-X.md"
      >template MIP here</a
    >,
    <a href="https://github.com/mstable/MIPs/blob/master/mccp-X.md"
      >a template MCCP here</a
    >, and a template TDP here.
  </li>
  <li>
    Submit a Pull Request to mStable's
    <a href="https://github.com/mstable/MIPs">MIPs repository</a>.
  </li>
</ol>

<p>
  Your first PR should be a first draft of the final Proposal. It must meet the
  formatting criteria enforced by the build (largely, correct metadata in the
  header). An editor will manually review the first PR for a new Proposal and
  assign a number before merging it. Make sure you include a
  <code>discussions-to</code> header with the URL to a discussion forum or open
  GitHub issue where people can discuss the Proposal as a whole.
</p>
<p>
  If your Proposal requires images, the image files should be included in a
  subdirectory of the `assets` folder. E.g. for an MIP:
  <code>assets/mip-X</code> (for mip <b>X</b>). When linking to an image in the
  Proposal, use relative links such as <code>../assets/mip-X/image.png</code>.
</p>
<p>
  When you believe your Proposal is mature and ready to progress past the WIP
  phase, you should post the proposal in the
  <a href="https://forum.mstable.org/">mStable's forum</a>. If the community
  agrees to include it, the editors will update the state of your Proposal to
  <code>Approved</code>.
</p>

<h2>Status terms</h2>
<ul>
  <li><strong>WIP</strong> - a Proposal that is still being developed.</li>
  <li>
    <strong>Proposed</strong> - a Proposal that is ready to be reviewed in a
    governance call.
  </li>
  <li>
    <strong>Approved</strong> - a Proposal that has been accepted for
    implementation by the mStable community.
  </li>
  <li>
    <strong>Implemented</strong> - a Proposal that has been released to mainnet.
  </li>
  <li><strong>Rejected</strong> - a Proposal that has been rejected.</li>
</ul>