Kaspa Finalizes Three Standards for Native Tokens and Covenants

Kaspa’s KCC Coordination Forum has finalized three standards covering covenant interfaces, authorization, and fungible tokens, establishing shared specifications for developers building applications on the network. According to an announcement on Oct. 21, standards KCC-1, KCC-2, and KCC-20 are now final and ready for ecosystem adoption.

The finalization establishes ecosystem conventions without altering consensus rules or requiring every participant to adopt them. Kaspa’s canonical standards repository lists all three documents as Final, separating these conventions from core-node behavior changes, which are handled via Kaspa Improvement Proposals.

Standards Overview

KCC-1 defines shared interfaces for wallets, compilers, indexers, and other tools working with covenants, including an application binary interface for state and function calls. KCC-2 specifies five standard authorization schemes, including public keys, scripts, and covenant identifiers. KCC-20 builds on the first two standards to define token transfer rules, ownership, and receiving mechanisms.

Key facts

• KCC-1 defines shared interfaces for wallets, compilers, and indexers working with covenants.
• KCC-2 specifies five authorization schemes, covering public keys, scripts, and covenant identifiers.
• KCC-20 sets token transfer rules and supports receiving tokens through compatible outputs.
• Finalization establishes ecosystem conventions without modifying consensus rules.