KCC-20 is the fungible token standard for covenants on Kaspa layer 1. It became Final in the kaspanet/kccs specification repository on 21 October 2026, source the repository's commit history. A KCC-20 balance lives in a covenant output on the chain itself, so a Kaspa node can see every token without an outside indexer.
A token counts only if at least one of its unspent outputs carries a KCC-20 state that we proved by hash, against the official conformance vectors of the standard. Covenant outputs with any other state do not count.
snapshot 26 October 2026, 12:00 UTC, counted by Kaspa Pulse on our own Kaspa node, every holder output proven by hash against the KCC-20 test vectors.
Ranked by unique holders, the number of different owners of a token. The table shows no amounts and no prices.
| # | ticker | covenant id | holders | holder outputs | transfers |
|---|---|---|---|---|---|
| 1 | THEN | d8c4356d20 | 234 | 440 | 392 |
| 2 | GUZA | 3cb7bd371e | 200 | 353 | 353 |
| 3 | TEK | cecb547d3a | 88 | 181 | 315 |
| 4 | BTE | efcf006e57 | 80 | 131 | 210 |
| 5 | DAGAS | 244cd20dac | 65 | 90 | 111 |
| 6 | ROCKET | 7cf4b45ebf | 64 | 115 | 166 |
| 7 | KB | b75a6e90f5 | 46 | 80 | 112 |
| 8 | LUCIFER | 9f665e60a7 | 34 | 41 | 49 |
| 9 | FROG | e22cebe470 | 28 | 32 | 30 |
| 10 | BFLY | 1c30b57d79 | 25 | 25 | 49 |
the 10 KCC-20 tokens with the most holders, snapshot 26 October 2026, 12:00 UTC, counted by Kaspa Pulse. Transfers since 22 October 2026, 05:53 UTC. Tickers are not unique, the covenant id tells tokens apart. The full list of all 240 tokens is in our repository.
KRC-20 tokens are inscriptions, data written into ordinary transactions and read by an indexer such as Kasplex, so the balances exist in the indexer and not in the chain's rules. KCC-20 tokens sit in covenant outputs on layer 1, so each balance is part of a UTXO and every transfer has to satisfy the covenant script that the network checks. That is why we can count KCC-20 from our own node, while KRC-20 numbers come from an indexer and carry its name as the source.
As of 29 October 2026, no migration from KRC-20 to KCC-20 can be counted. No project runs a migration on mainnet that is described in an official source and leaves a marker on chain that ties a KCC-20 token to a KRC-20 token. The tools we found are drafts and switched off. 62 of the 240 KCC-20 tokens share a ticker with a KRC-20 token, source kasplex. A shared ticker does not make it the same token. As soon as a migration runs with an on-chain marker, we count it per token on this page.
We publish sums per token and no addresses. Our counting tools are open in our repository.
Every number carries its snapshot time. A new count needs a full run of our own node, and we start it by hand. The page takes up every new count on its next build, the date above changes with it.
KCC-20, formally KCC-0020, is the fungible token standard for covenants on Kaspa layer 1. It became Final in the kaspanet/kccs specification repository on 21 October 2026, source the repository's commit history. A KCC-20 balance lives in a covenant output, so a Kaspa node can see it without an outside indexer.
KRC-20 tokens are inscriptions, data written into ordinary transactions and read by an indexer such as Kasplex, so the balances exist in the indexer and not in the chain's rules. KCC-20 tokens sit in covenant outputs on layer 1, so each balance is part of a UTXO and every transfer has to satisfy the covenant script that the network checks. That is why KCC-20 can be counted from a node, while KRC-20 numbers come from an indexer and carry its name as the source.
240 KCC-20 tokens at 26 October 2026, 12:00 UTC, with 857 unique holders and 2,646 holder outputs, counted by Kaspa Pulse on our own Kaspa node. A token counts only if at least one unspent output carries a KCC-20 state that we proved by hash.
Not in a way anyone can count yet. As of 29 October 2026 no project runs an officially described migration on mainnet that leaves a marker on chain. 62 KCC-20 tokens share a ticker with a KRC-20 token, source kasplex, and a shared ticker does not make it the same token.
No. KCC-20 is token logic on top of covenants. The covenants themselves came with the Toccata hard fork, and KCC-20 describes how a token keeps its state and moves inside them. A wallet or explorer that follows the specification can read a KCC-20 balance from the chain.
Building on Kaspa? We review projects and run testnet load tests before launch.
follow kaspa pulse