Mhairi
March 2, 2022, 12:28pm
1
UMIPs (“UMA Improvement Proposals”) are the design documents used to propose changes to the UMA ecosystem. They provide information to the UMA community that describes a new feature for the UMA protocol, or its ecosystem. The UMIP should provide a concise technical specification of the feature and a rationale for the feature.
# UMIPs
UMIPs (“UMA Improvement Proposals”) are the design documents used to propose changes to the UMA ecosystem.
They provide information to the UMA community that describes a new feature for the UMA protocol, or its ecosystem.
The UMIP should provide a concise technical specification of the feature and a rationale for the feature.
They are modeled after [EIPs](https://eips.ethereum.org/) and [ZEIPs](https://blog.0xproject.com/0x-protocol-governance-voting-walkthrough-and-faq-3becfd57a370).
See here for an [EIP template](https://github.com/ethereum/EIPs/blob/master/eip-template.md) and [ZEIP template](https://github.com/0xProject/ZEIPs/blob/master/ISSUE_TEMPLATE.md).
We intend UMIPs to be the primary mechanism for proposing new features, collecting community technical input on an issue, and for documenting the design decisions that have gone into the UMA protocol.
UMIPs are a convenient way to track the progress of an implementation.
# What is the lifecycle of a UMIP?
A successful UMIP will move along the following stages: Draft ⟶ Last Call ⟶ Final ⟶ Approved.
Unsuccessful states are also possible: Abandoned and Rejected.
## Draft
A UMIP that is open for consideration and is undergoing rapid iteration and changes.
In order to proceed to “Last Call,” the implementation must be complete.
Every UMIP author is responsible for facilitating conversations and building community consensus for the proposal.
show original