Kwenta Improvement Proposals

Kwenta Improvement Proposals (KIPs) describe standards for the Kwenta platform, including core protocol specifications, client APIs, and contract standards.

Contributing

  1. Review KIP-1.
  2. Fork the repository by visiting the KIPs repo and pressing "Fork" in the top right.
  3. Add your KIP to your fork of the repository. There are templates for the different proposal types:
  4. Submit a Pull Request to Kwenta'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: kips/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 ready to progress past the Draft phase, you should reach out to a Kwenta Council member on Discord. The Kwenta Council will schedule in a call with the KIP author to go through the KIP in more detail.

Once assessed, a KIP is moved into Feasibility. Once the Kwenta Council has formally reviewed the KIP during the KIP presentation they can either move it to a vote or send it back to Draft. A vote is conducted via Snapshot. If a vote by the Kwenta Council reaches a majority, the KIP is moved to Approved, otherwise it is Rejected.

Once the KIP has been implemented the KIP is assigned the Implemented status.

KIP status terms

  • Draft - The initial state of a KIP while it is still being actively developed.
  • Feasibility - The KIP is being discussed with the community.
  • Voting - The KIP is awaiting a vote.
  • Approved - The KIP has successfully reached a majority Kwenta Council vote in favour.
  • Rejected - The KIP has failed to reach a majority Kwenta Council vote in favour.
  • Implemented - The KIP has been released to mainnet.

Proposal Types

  • KIP - A Kwenta Improvement Proposal outlines a change to be made to the Kwenta protocol. These are submitted to the Elite Council for voting and require a majority to pass.
  • CKIP - A Community Kwenta Improvement Proposal outlines a change to be made to the DAO which overrules the Elite Council. These proposals should only be used in the event that there's disagreement between the Elite Council and the Kwenta community. These are submitted to token holders for voting and require quorum (over 50% of the circulating supply) to pass.
  • KTR - A Kwenta Treasury Request outlines a request for funds from the treasuryDAO. These are submitted to the treasuryDAO and require a majority to pass.

Kwenta Improvement Proposals (KIPs) describe standards for the Kwenta platform, including core protocol specifications, client APIs, and contract standards.