Upgrades

βž• The mStable protocol is open source and can be built upon by anyone. Upgrades and changes to the system are formalised and recorded as MIPs and MCCPs

Rationale

We intend MIPs and MCCPs to be the primary mechanisms for proposing new features, collecting community input on an issue, and for documenting the design decisions for changes to mStable. Because they are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal.

It is highly recommended that a single MIP contain a single key proposal or new idea. The more focused the MIP, the more successful it is likely to be.

An MIP or MCCP must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement or change, and present a rationale for why it would contribute positively to the mStable ecosystem.

MIPs

mStable Improvement Proposals (MIPs) describe standards for the mStable platform, including core protocol specifications, client APIs, and contract standards.

MCCPs

mStable Configuration Change Proposals (MCCPs) detail and record changes made to system parameters such as swap fees, max weights, and bAsset addition or removal