KIPs.dev

Kaspa Improvement Proposals (KIPs)

Browse Kaspa Improvement Proposals (KIPs) for consensus, network upgrades, node behavior, and client APIs, with specifications and proposal statuses.

Browse

/ to search

15 documents

No.TitleLayerStatus
1 KIP 1: Rewriting the Kaspa Full-Node in the Rust Programming Language Emailmsutton@cs.huji.ac.il Core Implemented
2 KIP 2: Upgrade consensus to follow the DAGKNIGHT protocol Yonatan Sompolinsky Consensus, API/RPC Proposed
3 KIP 3: Block sampling for efficient DAA with high BPS Emailshai.wyborski@mail.huji.ac.il Consensus, DAA Rejected
4 KIP 4: Sparse Difficulty Windows Emailshai.wyborski@mail.huji.ac.il Consensus, DAA Active
5 KIP 5: Message Signing coderofstuff Applications Active
6 KIP 6: Proof of Chain Membership (PoChM) Emailshai.wyborski@mail.huji.ac.il Consensus, Block Validation Draft
9 KIP 9: Extended mass formula for mitigating state bloat Emailmsutton@cs.huji.ac.il Mempool, P2P, Consensus Active
10 KIP 10: New Transaction Opcodes for Enhanced Script Functionality Username@biryukovmaxim Consensus, Script Engine Active
13 KIP 13: Transient Storage Handling Emailmsutton@cs.huji.ac.il Consensus, Block Size Active
14 KIP 14: The Crescendo Hardfork Emailmsutton@cs.huji.ac.il Consensus Active
15 KIP 15: Canonical Transaction Ordering and SelectedParent Accepted Transactions Commitment Emailfeanorr@gmail.com Username@reshmem Consensus Active
16 KIP 16: New Transaction Opcodes for Verifiable Computation Username@saefstroem Script Engine, ZK Active
17 KIP 17: Covenants and Improved Scripting Capabilities Emailorinewman1@gmail.com Consensus, Script Engine Active
20 KIP 20: Covenant IDs Emailmsutton@cs.huji.ac.il Consensus, Script Engine Active
21 KIP 21: Partitioned Sequencing Commitment with O(activity) Proving Emailmsutton@cs.huji.ac.il Username@biryukovmaxim Emailhans.moog@kaspafoundation.org Consensus, Chain-Block UTXO Validation Active

What are KIPs?

A Kaspa Improvement Proposal (KIP) documents a proposed change or specification for the Kaspa network. Topics include consensus rules, node behavior, network upgrades, and client APIs. This collection lets you read the technical documents and compare their recorded statuses.

KIPs and KCCs

KIPs cover protocol development. Kaspa Calls for Conventions (KCCs) describe shared conventions for applications, covenants, assets, wallets, and other ecosystem tools.