Skip to content

Rari-Capital/rari-improvement-proposals

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

55 Commits
 
 
 
 
 
 
 
 

Repository files navigation

RIPs Discord Telegram Twitter Follow

History

The RIP document was derived heavily from the SIP Synthetix Improvement Proposal document and YIP yEarn Improvement Proposal document and in many places, the text was simply copied and modified. Any comments about the RIP document should be directed to the RIP editors.

Background

Rari Improvement Proposals (RIPs) describe advancements for the Rari Capital platform, including core protocol specifications, client APIs, and contract enhancements.

Contributing

  1. Review RIP-0.
  2. Fork the repository by clicking "Fork" in the top right.
  3. Add your RIP to your fork of the repository. There is a template RIP here.
  4. Submit a Pull Request to Rari’s RIPs repository.

Your first PR should be a first draft of the final RIP. 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 RIP and assign it a number before merging it. Make sure you include a discussions-to header with the URL to a new thread on forums.rari.capital where people can discuss the RIP as a whole.

If your RIP requires images, the image files should be included in a subdirectory of the assets folder for that RIP as follow: assets/RIP-X (for RIP X). When linking to an image in the RIP, use relative links such as ../assets/RIP-X/image.png.

When you believe your RIP is mature and ready to progress past the WIP phase, you should ask to have your issue added to the future governance calls where it can be discussed for inclusion in a future platform upgrade. If the community agrees to include it, the RIP editors will update the state of your RIP to 'Approved'.

RIP Statuses

  • WIP - a RIP that is still being developed.
  • Proposed - a RIP that is ready to be reviewed in a governance call.
  • Approved - a RIP that has been accepted for implementation by the Rari community.
  • Implementing -- This RIP is currently being implemented.
  • Implemented - a RIP that has been released to mainnet.
  • Rejected - a RIP that has been rejected.
  • Withdrawn - a RIP that has been withdrawn by the author(s).
  • Deferred - a RIP that is pending another RIP/some other change that should be bundled with it together.
  • Moribund - a RIP that was implemented but is now obsolete and requires no explicit replacement.

Copyright

Copyright and related rights waived via CC0.

About

The Rari Improvement Proposal Repository

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published