Skip to content

golddydev/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.

Note For new CIP, 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 CPS, 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 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.

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 Draft
0007 Curve Pledge Benefit Proposed
0008 Message Signing Draft
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 Draft
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 Active
0018 Multi-Stake-Keys Wallets Draft
0019 Cardano Addresses Active
0020 Transaction message/comment metadata Active
0021 Transaction requirements for interoperability with hardware wallets Draft
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 Draft
0027 CNFT Community Royalties Standard Draft
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 Draft
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 Proposed
0050 Pledge Leverage-Based Staking Rewards Proposed
0052 Cardano Audit Best Practice Guidelines Proposed
0054 Cardano Smart NFTs Draft
0055 Protocol Parameters (Babbage Era) Active
0057 Plutus Smart-Contract Blueprint Active
0058 Plutus Bitwise Primitives Proposed
0059 Terminology Surrounding Core Features Active
0060 Music Token Metadata Active
0067 Asset Name Label Registry Proposed
0068 Datum Metadata Standard Proposed
0069 Plutus Script Type Uniformization Proposed
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
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
0105 Conway Era Key Chains for HD Wallets Proposed
0381 Plutus Support for Pairings Over BLS12-381 Proposed
1694 A proposal for entering the Voltaire phase Proposed
1852 HD (Hierarchy for Deterministic) Wallets for Cardano Active
1853 HD (Hierarchy for Deterministic) Stake Pool Cold Keys for Cardano Active
1854 Multi-signatures HD Wallets Draft
1855 Forging policy keys for HD Wallets Active
9999 Cardano Problem Statements Active

Last updated on 2024-01-09

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

Proposals Under Review (CIP)

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.

# Title
0038? Arbitrary Script as Native Script Spending Conditions
0039? Language Annotated Address
0056? Treasury Donation
0062? Governance API for dApp Connectors
0073? Oracle Datum Standard
0076? Hash-Checked Data
0077? Verified Stake Pool Identity
0079? Implement Ouroboros Leios to increase Cardano throughput
0087? Maybe Datum
0089? Beacon Tokens & Distributed Dapps
0090? Extendable dApp-Wallet Web Bridge
0091? Don't force Built-In functions
0092? First-class errors in Plutus
0096? On-chain dApp Certification Metadata
0097? Representing the Script Context as a SOP term
0103? Web-Wallet Bridge - Bulk transaction signing
0104? Web-Wallet Bridge - Account public key
0106? Web-Wallet Bridge - Mutlisig wallets
0107? URI Scheme - Block and transaction objects
0108? Governance Metadata - Governance Actions
0109? Modular Exponentiation Built-in for Plutus Core
0110? Plutus v1 compatible script references

Last updated on 2024-01-09

Cardano Problem Statements (CPS)

# Title Status
0005 Plutus Script Usability Open
0007 Voltaire era Governance Open

Last updated on 2023-07-02

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

Proposals Under Review (CPS)

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
0010? Wallet Connectors

Last updated on 2023-11-28

Stalled / Waiting For Authors

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.

Last updated on 2023-06-09

Editors

Matthias Benkort
@KtorZ
Sebastien Guillemot
@SebastienGllmt
Robert Phair
@rphair
Ryan Williams
@Ryun1
Adam Dean
@Crypto2099

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%