A Cardano Improvement Proposal (CIP) is a formalised design document for the Cardano community and the name of the process by which such documents are produced and listed. A CIP provides information or describes a change to the Cardano ecosystem, processes, or environment concisely and in sufficient technical detail. In this CIP, we explain what a CIP is; how the CIP process functions; the role of the CIP Editors; and how users should go about proposing, discussing and structuring a CIP.
The Cardano Foundation intends CIPs to be the primary mechanisms for proposing new features, collecting community input on an issue, and documenting design decisions that have gone into Cardano. Plus, because CIPs are text files in a versioned repository, their revision history is the historical record of significant changes affecting Cardano.
For more about the human factors of the CIP process, and to learn how to get involved, click the Wiki tab above (CIP Wiki).
Note For new CIPs, a reference template is available in .github/CIP-TEMPLATE.md
A Cardano Problem Statement (CPS) is a formalised document for the Cardano ecosystem and the name of the process by which such documents are produced and listed. CPSs are meant to complement CIPs and live side-by-side in the CIP repository as first-class citizens.
Note For new CPSs, a reference template is available in .github/CPS-TEMPLATE.md
Extend or discuss ‘ideas’ in the Developer Forums, Cardano’s Official Developer Telegram Group or in #developers in Cardano Ambassadors Slack.
CIP editors facilitate discussions and progress submissions on GitHub, reviewing progress in bi-weekly meetings held on Discord which are open to the public. The Discord server also has channels for developer working groups to discuss details and implementations of selected CIPs.
Note To facilitate browsing and information sharing for non-Github users, an auto-generated site is also provided at cips.cardano.org.
Last updated on 2024-10-29
💡 For more details about CIP statuses, refer to CIP-0001.
The following link lists "candidate" CIPs still under discussion with the community; these are assigned numbers to avoid later clashes and to facilitate community discussion (see further below for stalled proposals):
CIP pull requests under active review
| # | Title | Status |
|---|---|---|
| 0005 | Plutus Script Usability | Open |
| 0007 | Voltaire era Governance | Open |
| 0008 | Domain Name Resolution | Open |
| 0009 | Coin Selection Including Native Tokens | Open |
| 0010 | Wallet Connectors | Open |
| 0011 | Universal JSON Encoding for Domain Types | Open |
| 0012 | Query Layer Standardization | Open |
| 0013 | Better builtin data structures in Plutus | Open |
| 0014 | Register of CBOR Tags | Open |
| 0016 | Cardano URIs | Open |
Last updated on 2024-09-03
💡 For more details about CPS statuses, refer to CIP-9999.
The following link lists "candidate" CPSs still under discussion with the community; these are assigned numbers to avoid later clashes and to facilitate community discussion (see further below for stalled proposals):
CPS pull requests under active review
The following link shows updates to existing CIPs and CPSs that have entered the review process:
CIP and CPS updates under consideration
The following links list proposals deemed ready for review but requiring further update from the original author(s) or other confirmation of proposal elgibility (if considered deprecated):
Stalled CIPs and CPSs - consisting of:
Proposals stalled without any updates from their authors will eventually be closed. However, authors are invited to re-open pull requests or open new ones should they want to bring the discussion back to life.
| Robert Phair @rphair |
Ryan Williams @Ryun1 |
Adam Dean @Crypto2099 |
Thomas Vellekoop @perturbing |
|---|