---
rip: <to be assigned>
title: <RIP title>
status: WIP
author: <a list of the author's or authors' name(s) and/or username(s), or name(s) and email(s), e.g. (use with the parentheses or triangular brackets): FirstName LastName (@GitHubUsername), FirstName LastName <[email protected]>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
discussions-to: <Create a new thread on https://forums.rari.capital/ and drop the link here>
created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
requires (*optional): <RIP number(s)>
implementation (*optional): <Added if RIP passes>
---This is the suggested template for new RIPs. Note that an RIP number will be assigned by an editor. When opening a pull request to submit your RIP, please use an abbreviated title in the filename, rip-draft_title_abbrev.md. The title should be 44 characters or less.
"If you can't explain it simply, you don't understand it well enough." Simply describe the outcome the proposed change intends to achieve. This should be non-technical and accessible to a casual community member.
A short (~200 word) description of the proposed change, the abstract should clearly describe the proposed change. This is what will be done if the RIP is implemented, not why it should be done or how it will be done. If the RIP proposes deploying a new contract, write, "we propose to deploy a new contract that will do x".
This is the problem statement. This is the why of the RIP. It should clearly explain why the current state of the protocol is inadequate. It is critical that you explain why the change is needed, if the RIP proposes changing how something is calculated, you must address why the current calculation is innaccurate or wrong. This is not the place to describe how the RIP will address the issue!
This is a high level overview of how the RIP will solve the problem. The overview should clearly describe how the new feature will be implemented.
The technical specification should outline the public API of the changes proposed. That is, changes to any of the interfaces Rari Finance currently exposes or the creations of new ones.
Test cases for an implementation are mandatory for RIPs but can be included with the implementation.
Copyright and related rights waived via CC0.