Kaspa's KCC Coordination Forum has finalized three standards covering covenant interfaces, authorization and fungible tokens. They set shared specifications for developers, but they change no consensus rules and not every participant has to adopt them.
The KCC Coordination Forum declared KCC-1, KCC-2 and KCC-20 final in an Oct. 21 announcement, saying they are ready for adoption across the Kaspa ecosystem. The forum also invited builders to join its public channel for questions, implementation discussions and support.
KCC-1 and KCC-2 cover interfaces and authorization
KCC-1 defines common terms, data layouts and an application binary interface for covenants. Compilers, wallets, indexers and transaction builders need to agree on those details, according to its authors. The specification leaves developers free to choose their programming language, compiler and framework.
KCC-2 then addresses who can approve an operation. It assigns standard identifiers to five authorization schemes, and an authority can be a public key, a commitment to a key, a script or a continuing covenant lineage. Participants may also adopt custom schemes without waiting for standardization, provided their definitions specify the format, meaning and approval checks.
KCC-20 sets token transfer rules
KCC-20 builds on the first two standards and defines token amounts, ownership and transfer interfaces. Each token covenant must publish program information that software can use to decode state and construct transfers.
A feature called borrowed receive lets a sender use a recipient's existing compatible token output as the destination. The transaction recreates that output with more tokens and cannot reduce its KAS value. The security section warns that replacing the output invalidates unconfirmed transactions spending the previous reference.
Finalization requires test vectors and a public implementation
The governing document, KCC-0, requires human-readable and machine-readable test vectors for a standards-track convention. It also requires at least one public implementation that passes the machine-readable checks.
Kaspa's application development has previously included separate Layer 2 infrastructure. Gate announced a Kasplex Layer 2 integration in April, enabling KAS deposits and withdrawals through the EVM-compatible network.
Source: crypto.news
Trading involves risk.
Risk Disclaimer
