token-standard
KCC-20
finalCovenant-native tokens — the chain itself enforces the rules
In plain English
Tokens built as covenants, so supply and transfer rules are checked by Kaspa consensus itself — no off-chain bookkeeper has to be trusted. Live on mainnet, and the written standard is Final as of 2026-10-21 — a finalized Kaspa convention.
Tokens whose rulebook is machined into the vault door — nobody outside the chain keeps the score.
At a glance
- Layer
- token-standard
- Network
- L1
- State model
- covenant UTXO
- Composability
- covenant-id ownership
- Token support
- unverified
- Since
- standard Final 2026-10-21
- On mainnet
- yes
- Live tokens
- 121 of 316 tokens (kcc20.info) · 3,491 live token states (kascov)
Best for
- new tokens with L1-enforced rules
- trust-minimized supply logic
What it can't do
- assuming Final means audited software — the standard is final; implementations still carry their own maturity
Live status
From the GitHub API for kaspanet/kccs, refreshed every 4 hours.
no release latest tag 2026-10-21 last push 13 stars 8 open issues
When to choose it over…
- Kaspa Script + Covenants++ — the base rule system built into kaspa transactions
- Silverscript — high-level covenant language that compiles to kaspa script
- Argent — actor-based app language that builds on silverscript
- vProgs / CDAG — native programs living in the dag — public prototype, early development
Links
- Repository github.com/kaspanet/kccs
- Docs kccs.dev
- Playground / explorer kascov.io
The deep-dive guide for this component is in progress. The essentials above are held to the site's data rules: unknown values render as "unverified", never guesses.