mStable Improvement Proposals (MIPs) describe standards for the mStable platform, including core protocol specifications, client APIs, and contract standards.
mStable Configuration Change Proposal (MCCPs) describe a standard for modifying one of the system configuration variables
Treasury DAO Proposals (TDPs) describe standards for the Treasury DAO for allocating resources from the mStable's Treasury
- Review MIP-1, MCCP-1 or TDP-XX. .
- Fork the repository by clicking "Fork" in the top right.
- Add your Proposal to your fork of the repository. There is a template MIP here, a template MCCP here, and a template TDP here.
- Submit a Pull Request to mStable's MIPs repository.
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
discussions-to header with the URL to a discussion forum or open
GitHub issue where people can discuss the Proposal as a whole.
If your Proposal requires images, the image files should be included in a
subdirectory of the `assets` folder. E.g. for an MIP:
assets/mip-X (for mip X). When linking to an image in the
Proposal, use relative links such as
When you believe your Proposal is mature and ready to progress past the WIP
phase, you should post the proposal in the
mStable's forum. If the community
agrees to include it, the editors will update the state of your Proposal to
- WIP - a Proposal that is still being developed.
- Proposed - a Proposal that is ready to be reviewed in a governance call.
- Approved - a Proposal that has been accepted for implementation by the mStable community.
- Implemented - a Proposal that has been released to mainnet.
- Rejected - a Proposal that has been rejected.