Kaspa's KCC Coordination Forum announced the completion of three technical specifications designed to standardize development of covenant-based applications and fungible tokens on the network. The standards — KCC-1, KCC-2, and KCC-20 — establish shared conventions for how software interacts with covenants, authorization mechanisms, and token transfers, without altering core consensus rules.

KCC-1 defines standardized interfaces for tools including wallets, compilers, and indexers that process covenant programs. It specifies data formats, application binary interfaces, and transaction handling rules, enabling consistent encoding of program calls and state management across implementations. The specification allows developers to select their own programming languages and frameworks while adhering to common structural requirements.

KCC-2 outlines five standardized authorization schemes that determine who can validate operations within covenants. These include public key signatures (Schnorr and ECDSA), script-based approvals, and lineage-based authorities tied to covenant histories. The standard assigns fixed identifiers to these schemes and permits custom authorization models provided they meet defined format and verification criteria.

KCC-20 establishes rules for fungible token creation, transfer, and reception. It requires token covenants to publish program details for state decoding and mandates specific disclosures about ownership schemes and transaction limits. A notable feature allows senders to utilize existing compatible token outputs as destinations, though the standard cautions that such transfers modify the output's transaction reference, potentially invalidating pending spends.

The forum emphasized that adoption of these standards is optional and does not require universal implementation. Finalization signifies readiness for developer use following completion of review cycles and verification of test vectors and reference implementations. The repository hosting the standards maintains separation between these conventions and core protocol changes, which remain subject to separate Kaspa Improvement Proposals.

Developers seeking guidance or collaboration are directed to the public KCC coordination channel for technical discussions and implementation support. The forum's announcement, dated October 21, 2026, confirmed the standards' final status and invited ecosystem participants to engage with the specifications as they advance application development on Kaspa.