Kaspa's proposed KCC20 token standard has entered 'last call', the final public review stage before it can be finalised. The development was reported by @MSBIntel and relates to work coordina
Kaspa's proposed KCC20 token standard has entered 'last call', the final public review stage before it can be finalised. The development was reported by @MSBIntel and relates to work coordinated through the @kaspaunchained ecosystem, and it is a notable step for the $KAS network's push into native token support.
KCC20 is a fungible-token standard for Kaspa's base layer. According to a KuCoin-hosted summary of a Kaspa developer roundup, the standard has entered last call, its final public review stage, with a reference implementation merged so developers can test against the proposed Layer 1 token standard.
The aim is to make life easier for wallet and app builders. A separate KuCoin-hosted post says the standard proposes a shared way to describe who owns tokens, how many they hold and how transfers work. In practice, that would give developers one common format rather than each application building its own token logic.
The reference code is still at a testing stage. One developer commentary shared on KuCoin notes that the merged reference implementation covers local tests, not a live token rollout. In Kaspa's convention process, last call is the last review window before a standard can be marked final, and a status of final is not yet in place for KCC20.
The standard depends on Kaspa's Toccata hard fork. The upgrade was designed to introduce covenants and zero-knowledge infrastructure at Layer 1. Kaspa's core developer Michael Sutton described Toccata as the point where the network's monetary base layer meets programmability in two layered forms, namely native L1 covenant systems and based ZK systems, according to KasMedia's coverage of his April 2026 outlook.
Covenants are programmable rules attached to transactions, and KCC20 uses them to represent fungible tokens. Wallet developers are already responding: the Kaspire wallet says its Android app supports the new KCC20 Last Call reference profile, with local covenant validation.
If the standard moves to final status, it could give projects a consistent route to issue tokens directly on Kaspa's base layer. That would make the fourth quarter an important period for the $KAS ecosystem, though adoption by wallets, exchanges and developers will determine how far the standard is used.
Sources
KuCoin News: Kaspa weekly dev roundup on KCC20 last callKasMedia: Toccata hard fork covenant and ZK infrastructureKaspire: wallet support for KCC20 Last Call reference profile
