Kaspa’s (@kaspaunchained) $KAS KCC-20 token standard has entered its final review stage before potential finalization. The proposal sets out a common format for fungible tokens on the Kaspa l
Kaspa’s (@kaspaunchained) $KAS KCC-20 token standard has entered its final review stage before potential finalization. The proposal sets out a common format for fungible tokens on the Kaspa layer 1 network, covering ownership, balances and the transaction process.
The standard also addresses how wallets and apps interpret token information and how they handle borrowed tokens. If it is finalized, developers building token tools on Kaspa would have a shared approach to follow rather than designing their own token logic.
KCC-20 is designed for fungible tokens built on Kaspa’s covenant system. According to the project’s community FAQ, a KCC20 token can be owned by a wallet or by another covenant, and supply rules are enforced through contract logic rather than an external execution layer.
The proposal is authored by Sivan Helfer, Michael Sutton and Romain Billot, and was created on 15 July 2026, based on a third-party reading of the Kaspa standards repository. That reading also notes that KCC-20 predates the formal standards process, which runs from idea to draft, review, last call and final. Final status requires a completed last call, among other conditions.
Developer commentary indicates that a reference implementation has been merged and is open for testing, though that is a local test environment rather than a live token rollout. Kaspa’s status tracker had earlier listed KCC-20 as a draft, so the move to last call marks the latest step in that process.
The standard builds on Kaspa’s Toccata upgrade. Toccata went live on Kaspa’s mainnet on 30 June 2026, adding programmable outputs through covenants, transaction introspection, native zero-knowledge verification and support for based applications, according to TokenPost.
Cointribune describes the upgrade as having turned Kaspa from a fast payments chain into a programmable layer 1, with native contracts, built-in token support, ZK verification opcodes and the SilverScript compiler. Kaspa remains a proof-of-work network.
A finalized KCC-20 would not by itself guarantee wider adoption. Wallets and apps still need to implement the standard for it to deliver a consistent experience for users and developers.
Sources
