Skip to content

Latest commit

 

History

History
25 lines (19 loc) · 1.77 KB

README.md

File metadata and controls

25 lines (19 loc) · 1.77 KB
Raw

KIPs

KeyFi Improvement Proposals (KIPs) describe standards for the KeyFi platform, including API and smart contract integrations, asset listings and organizational governance.

Contributing

  • Review KIP-0.
  • Fork the repository by clicking "Fork" in the top right.
  • Add your KIP to your fork of the repository. There is a template KIP here.
  • Submit a Pull Request to KeyFi's KIPs repository.

Your first PR should be a first draft of the final KIP. 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 KIP and assign it a number before merging it.

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

When you believe your KIP 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 KIP editors will update the state of your KIP to 'Approved'.

KIP Statuses

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