Skip to content

fallen-icarus/CIPs

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Cardano Improvement Proposals (CIPs)

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

Cardano Problem Statements (CPS)

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

Communication Channels

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.

Cardano Improvement Proposals (CIP)

# Title Status
0001 CIP Process Active
0002 Coin Selection Algorithms for Cardano Active
0003 Wallet key generation Active
0004 Wallet Checksums Proposed
0005 Common Bech32 Prefixes Active
0006 Stake Pool Extended Metadata Active
0007 Curve Pledge Benefit Proposed
0008 Message Signing Active
0009 Protocol Parameters (Shelley Era) Active
0010 Transaction Metadata Label Registry Active
0011 Staking key chain for HD wallets Active
0012 On-chain stake pool operator to delegates communication Proposed
0013 Cardano URI Scheme Proposed
0014 User-Facing Asset Fingerprint Active
0015 Catalyst Registration Transaction Metadata Format Active
0016 Cryptographic Key Serialisation Formats Active
0017 Cardano Delegation Portfolio Inactive
0018 Multi-Stake-Keys Wallets Proposed
0019 Cardano Addresses Active
0020 Transaction message/comment metadata Active
0021 Transaction requirements for interoperability with hardware wallets Active
0022 Pool operator verification Active
0023 Fair Min Fees Proposed
0024 Non-Centralizing Rankings Proposed
0025 Media Token Metadata Standard Active
0026 Cardano Off-Chain Metadata Active
0027 CNFT Community Royalties Standard Active
0028 Protocol Parameters (Alonzo Era) Active
0029 Phase-1 Monetary Scripts Serialization Formats Active
0030 Cardano dApp-Wallet Web Bridge Active
0031 Reference Inputs Active
0032 Inline Datums Active
0033 Reference Scripts Active
0034 Chain ID Registry Proposed
0035 Plutus Core Evolution Active
0036 Catalyst Registration Transaction Metadata Format Proposed
0037 Dynamic Saturation Based on Pledge Proposed
0040 Collateral Output Active
0042 New Plutus Builtin: serialiseBuiltinData Active
0045 Decentralized WebRTC dApp-Wallet Communication Active
0049 ECDSA and Schnorr signatures in Plutus Core Active
0050 Pledge Leverage-Based Staking Rewards Proposed
0052 Cardano Audit Best Practice Guidelines Proposed
0054 Cardano Smart NFTs Proposed
0055 Protocol Parameters (Babbage Era) Active
0057 Plutus Smart-Contract Blueprint Active
0058 Plutus Bitwise Primitives Inactive
0059 Terminology Surrounding Core Features Active
0060 Music Token Metadata Active
0067 Asset Name Label Registry Proposed
0068 Datum Metadata Standard Active
0069 Plutus Script Type Uniformization Active
0071 Non-Fungible Token (NFT) Proxy Voting Standard Proposed
0072 DApp Registration Proposed
0074 Set min-pool-cost to 0 Proposed
0075 Fair Stake Pool Rewards Proposed
0080 Transaction Serialization Deprecation Cycle Active
0082 Improved Rewards Scheme Parameters Proposed
0083 Encrypted Transaction message/comment metadata (Addendum to CIP-0020) Active
0084 Cardano Ledger Evolution Active
0085 Sums-of-products in Plutus Core Proposed
0086 NFT Metadata Update Oracles Proposed
0088 Token Policy Registration Proposed
0091 Don't force Built-In functions Proposed
0093 Authenticated Web3 HTTP requests Proposed
0094 SPO On-chain Polls Active
0095 Web-Wallet Bridge - Conway ledger era Active
0099 Proof of Onboarding Active
0100 Governance Metadata Proposed
0101 Integration of keccak256 into Plutus Proposed
0102 Royalty Datum Metadata Proposed
0103 Web-Wallet Bridge - Bulk transaction signing Active
0104 Web-Wallet Bridge - Account public key Proposed
0105 Conway Era Key Chains for HD Wallets Proposed
0106 Web-Wallet Bridge - Multisig wallets Proposed
0107 URI Scheme - Block and transaction objects Proposed
0108 Governance Metadata - Governance Actions Proposed
0109 Modular Exponentiation Built-in for Plutus Core Proposed
0110 Plutus v1 compatible script references Active
0112 Observe script type Proposed
0114 CBOR Tags Registry Proposed
0115 CBOR tag definition - ED25519-BIP32 Keys Proposed
0116 Universal JSON Encoding for Domain Types Proposed
0117 Explicit script return values Active
0119 Governance Metadata - DReps Proposed
0121 Integer-ByteString conversions Active
0122 Logical operations over BuiltinByteString Proposed
0123 Bitwise operations over BuiltinByteString Proposed
0124 Extend token metadata for translations Proposed
0127 Integration of ripemd_160 into Plutus Proposed
0128 Preserving Order of Transaction Inputs Proposed
0133 Plutus support for Multi-Scalar Multiplication over BLS12-381 Proposed
0134 Cardano URIs - Address Representation Proposed
0135 Disaster Recovery Plan for Cardano networks Active
0137 Decentralized Message Queue Proposed
0381 Plutus Support for Pairings Over BLS12-381 Proposed
1694 A First Step Towards On-Chain Decentralized Governance Active
1852 HD (Hierarchy for Deterministic) Wallets for Cardano Active
1853 HD (Hierarchy for Deterministic) Stake Pool Cold Keys for Cardano Proposed
1854 Multi-signatures HD Wallets Active
1855 Forging policy keys for HD Wallets Active
9999 Cardano Problem Statements Active

Last updated on 2024-10-29

💡 For more details about CIP statuses, refer to CIP-0001.

Proposals Under Review (CIP)

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

Cardano Problem Statements (CPS)

# 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.

Proposals Under Review (CPS)

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

Updates Under Consideration

The following link shows updates to existing CIPs and CPSs that have entered the review process:

CIP and CPS updates under consideration

Stalled / Waiting For Authors

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.

Editors

Robert Phair
@rphair
Ryan Williams
@Ryun1
Adam Dean
@Crypto2099
Thomas Vellekoop
@perturbing

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 38.4%
  • TypeScript 26.6%
  • PHP 15.6%
  • HTML 10.3%
  • Haskell 6.9%
  • Shell 2.2%