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.
Note For new CIP, 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 CPS, 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 will review discussions and progress in bi-weekly meetings held on Discord, then transcribe and summarise them in the BikweeklyMeetings folder.
CIP Editors meetings are public, recorded, and published on Youtube: do join and participate in discussions/PRs of significance to you.
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-03-06
💡 For more details about CIP statuses, refer to CIP-0001.
Below are listed tentative CIPs still under discussion with the community. They are listed below for easing navigation and tentatively allocating numbers to avoid later clashes.
Last updated on 2024-03-06
| # | Title | Status |
|---|---|---|
| 0005 | Plutus Script Usability | Open |
| 0007 | Voltaire era Governance | Open |
| 0010 | Wallet Connectors | Open |
| 0011 | Universal JSON Encoding for Domain Types | Open |
| 0013 | Better builtin data structures in Plutus | Open |
| 0014 | Register of CBOR Tags | Open |
Last updated on 2024-03-06
💡 For more details about CPS statuses, refer to CIP-9999.
Below are listed tentative CPSs still under discussion with the community. They are listed below for easing navigation and also tentatively allocating numbers to avoid clashes later on.
| # | Title |
|---|---|
| 0001? | Metadata Discoverability and Trust |
| 0004? | Spending Script Redundant Execution |
| 0006? | Governance Security |
| 0008? | Domain Name Resolution |
| 0009? | Coin Selection Including Native Tokens |
| 0012? | Query Layer Standardization |
Last updated on 2024-03-06
The following list contains proposals that have been under review and for which actions are now awaiting updates from their original authors. Proposals stalled for several months without any updates from their authors and 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.
- UPLC Serialization Optimizations
- Address Resolution Through DNS
- Transferring Stake Pool Ownership
- Extended Local Chain Sync Protocol
- Tiered Pricing Protocol
- Properly burning NFTs/tokens
- On-chain Transaction Chaining
- Merklised Plutus Scripts
- Rejected Ideas w.r.t Spending Policies
Last updated on 2023-06-09
| Matthias Benkort @KtorZ |
Sebastien Guillemot @SebastienGllmt |
Robert Phair @rphair |
Ryan Williams @Ryun1 |
Adam Dean @Crypto2099 |
|---|