KIP Index
What Are KIPs?
Kaspa Improvement Proposals (KIPs) are the formal mechanism for proposing changes to the Kaspa protocol. Since Kaspa has no foundation or central authority, KIPs provide a structured, transparent process for community-driven development.
KIPs are discussed and tracked on GitHub.
KIP Index
| KIP | Title | Status |
|---|---|---|
| KIP-1 | Rust Rewrite | Implemented |
| KIP-2 | DAGKnight | Proposed |
| KIP-3 | Block Sampling | Rejected |
| KIP-4 | Sparse DAA | Active (Crescendo) |
| KIP-5 | Message Signing | Active |
| KIP-6 | PoChM Proofs | Draft |
| KIP-9 | Extended Mass Formula | Implemented (Crescendo) |
| KIP-10 | New Opcodes | Implemented (Crescendo) |
| KIP-13 | Transient Storage | Implemented (Crescendo) |
| KIP-14 | Crescendo Hardfork | Implemented |
| KIP-15 | Sequencing Commitments | Implemented (Crescendo) |
Status Definitions
- Implemented — merged and active on mainnet
- Active — accepted and in use, may have ongoing work
- Proposed — submitted for consideration, not yet implemented
- Draft — early stage, still being developed
- Rejected — reviewed and not accepted
Notable KIPs
KIP-1: Rust Rewrite
The proposal to rewrite the Kaspa node from Go to Rust, resulting in rusty-kaspa. This was a foundational change that improved performance and enabled the Crescendo upgrade.
KIP-2: DAGKnight
The proposed next-generation consensus protocol. Would make confirmation times responsive and achieve 50% Byzantine fault tolerance. Not yet implemented.
KIP-14: Crescendo
The hardfork proposal that bundled KIP-4, KIP-9, KIP-10, KIP-13, and KIP-15 into the Crescendo upgrade, taking the network from 1 BPS to 10 BPS.