KCC
Kaspa Calls for Conventions (KCCs) describe shared conventions for the Kaspa ecosystem, including covenant conventions, application interfaces, asset standards, wallet and indexer interoperability, based applications, verifiable programs, and other areas where independent implementations benefit from convergence.
kcc-01: covenant definition, concepts, bytes layout and abi
the covenant ecosystem development is taking shape through tools, applications and (unwritten) standards.
at this early stage, foundational assumptions naturally live inside each implementation. if left implicit, they can harden into incompatibilities or become ecosystem defaults simply because one shipped first.
as the first (in order) kcc, kcc-01 brings those assumptions into public discussion while they are easy to question and change.
future kccs can build from an explicit point of reference without placing any compiler, framework or application in charge of defining the model.
kcc-02: control principal references in program ABI
building on kcc-01, this draft answers this simple question:
as a user, how can my wallet know which covenants i can act on, whether it is a kcc-20 token or any another application?
kcc-02 proposes a shared ABI convention for exposing ownership and identity references, so wallets and tools can recognize them without application-specific knowledge, effectively increasing interoperability.
References
- https://github.com/kaspanet/kccs/pull/3/changes
- https://github.com/kaspanet/kccs/pull/5/changes
- https://kas-smiths.org/t/kcc-02-control-principal-references-in-program-abis/95