Kaspa Formalizes Smart Contract Standards for Native Tokens

The finalized specifications—KCC-1, KCC-2, and KCC-20—provide the necessary blueprints for wallets, indexers, and compilers to interact with the Kaspa ecosystem. KCC-1 sets the foundation by defining common data layouts and the application binary interface for covenants. This allows developers to maintain flexibility in their choice of programming language while ensuring that independent software implementations remain interoperable.

Building on this, KCC-2 formalizes five distinct authorization schemes, including Schnorr and ECDSA signatures, scripts, and covenant lineages. By assigning standard identifiers to these methods, the protocol dictates how programs verify approval, providing a structured registry for both standard and custom implementations. The final piece, KCC-20, governs fungible tokens, introducing a "borrowed receive" feature that allows users to send tokens to existing outputs without diminishing their underlying KAS value.

These standards follow the rigorous requirements set by KCC-0, which mandates the inclusion of machine-readable test vectors and public implementations before a protocol can reach final status. While these conventions provide a unified path for application development, they remain distinct from Kaspa Improvement Proposals, which handle changes to core-node behavior. Builders are now encouraged to utilize these finalized documents to ensure their tools align with the broader network architecture.