Glossary
What is KCC?
Kaspa Calls for Conventions: shared standards for covenant apps and native tokens on Kaspa.
KCCs (Kaspa Calls for Conventions) are documents that describe shared conventions for the Kaspa ecosystem: how covenants are laid out, how apps talk to them, how tokens behave, and how wallets and indexers read them. When independent teams follow the same KCC, their tools work together.
KCC vs KIP
KCCs don't change Kaspa's consensus rules or how nodes behave. Those changes go through Kaspa Improvement Proposals (KIPs). A finalised KCC is a point the ecosystem agrees to converge on, not a protocol rule.
The first standards
In October 2026, the first KCCs were marked final:
- KCC-1: covenant concepts, byte layouts and ABI, the shared interface for wallets, compilers and indexers.
- KCC-2: authority schemes, which define who can approve an operation.
- KCC-20: the fungible token covenant specification, for native tokens on Kaspa.
More KCCs are in draft, including KCC-23 for token metadata.
KCC-20 and KRC-20
The names are similar but the designs are different. KRC-20 tokens are tracked by an off-chain indexer reading data in transactions. KCC-20 tokens are covenants, so their transfer rules are enforced by Kaspa itself.