View here: https://github.com/Rari-Capital/rari-improvement-proposals

What is a RIP?

RIP stands for Rari Improvement Proposal, it has been adapted from the SIP (Synthetix Improvement Proposal) and YIP (yEarn Improvement Proposal). RIPs are structured to present proposals to improve the Rari protocol and/or ecosystem. They should provide relative information surrounding the proposed change and objectively inform the community. The author is responsible for building consensus within the community and documenting dissenting opinions.

RIP Rationale

We intend RIPs to be the primary mechanisms for proposing new features, collecting community input on an issue, and for documenting the design decisions for changes to Rari Capital. 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 RIP only contain a single key proposal or new idea. The more focused the RIP, the easier it is to digest and the more successful it is likely to be.

A RIP must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement.

RIP Work Flow

Parties involved in the process are the author, the RIP editors, and the Rari community.

Before you begin, vet your idea, this will save you time. Ask the Rari community first if an idea is original to avoid wasting time on something that will be rejected based on prior research (searching the Internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will have the intended effect. The appropriate public platform to gauge interest around your RIP is the Rari Capital Telegram, Rari Capital Discord, or Rari Capital Forums.

Your role as the champion is to write the RIP using the style and format described below, shepherd the discussions in the appropriate forums, and build community consensus around the idea. Following is the process that a successful RIP will move along:

https://lh6.googleusercontent.com/BvlGdbqfmiPNuCKz3DjLoAi4C5t58nKz1zkoBxCnZc1eDrOA_ViCYndWQH9xj_XR0cKzu9VdKJuJzZw__sY_Yj4IvIjvIW-TGKPi3Y0xucDvnJexzvYIfJ6THRz8xLriZlGNAe63

Each status change is requested by the RIP author and reviewed by the RIP editors. Use a pull request to update the status. Please include a link to where people should continue discussing your RIP. The RIP editors will process these requests as per the conditions below.

• Work in progress (WIP) – Once the champion has asked the Rari community whether an idea has any chance of support, they will write a draft RIP as a pull request. Consider including an implementation if this will aid people in studying the RIP.
• Proposed If agreeable, a RIP editor will assign the RIP a number (generally the issue or PR number related to the RIP) and merge your pull request. The RIP editor will not unreasonably deny a RIP. Proposed RIPs will be discussed on governance calls and in Discord. If there is a reasonable level of consensus around the change on the governance call the change will be moved to approved. If the change is contentious a vote of token holders may be held to resolve the issue or approval may be delayed until a consensus is reached.
• Approved – This RIP has passed community governance and is now being prioritized for development.
• Implemented – This RIP has been implemented and deployed to mainnet.
• Rejected – This RIP has failed to reach community consensus.
• Withdrawn – This RIP has been withdrawn by the author(s).
• Deferred – This RIP is pending another RIP/some other change that should be bundled with it together.