How To Make a YIP
Last updated
Last updated
The yEarn Improvement Proposals (YIPs) describe standards for the yEarn platform, including core protocol specifications, client APIs, and contract standards. This is the definitive, canonical reference specification for the core logic.
Review .
Fork the repository by clicking "Fork" in the top right.
Add your YIP to your fork of the repository. There is a .
Submit a Pull Request to yEarn's .
Your first PR should be a first draft of the final YIP. 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 YIP and assign it a number before merging it. Make sure you include a discussions-to header with the URL to a new thread on where people can discuss the YIP as a whole.
Note: It is important that their be community support behind a proposed
YIP- It is up to the author(s) to shepard their proposal through the process.
If your YIP requires images, the image files should be included in a subdirectory of the assets folder for that YIP as follow: assets/yip-X (for yip X). When linking to an image in the YIP, use relative links such as ../assets/yip-X/image.png.
When you believe your YIP is mature and ready to progress past the WIP phase, you should ask to have your issue added to the next governance call where it can be discussed for inclusion in a future platform upgrade. If the community agrees to include it, the YIP editors will update the state of your YIP to 'Approved'.
WIP - a YIP that is still being developed.
Proposed - a YIP that is ready to be reviewed in a governance call.
Approved - a YIP that has been accepted for implementation by the yEarn community.
Implemented - a YIP that has been released to mainnet.
Rejected - a YIP that has been rejected.
It is possible to run the YIP validator locally:
YIPs MUST pass some validation tests. The YIP repository ensures this by running tests using and .
Copyright and related rights waived via .