KCCs.dev

Kaspa Calls for Conventions (KCCs)

Browse Kaspa Calls for Conventions (KCCs) for covenants, token standards, application interfaces, wallets, and interoperable ecosystem tooling.

Browse

/ to search

5 documents

No.TitleTypeStatus
0 KCC 0: KCC Purpose and Guidelines Username@Saefstroem Email[email protected] Meta Final
1 KCC 1: Covenant Concepts, Byte Layouts, and ABI Username@IzioDev Email[email protected] Email[email protected] Email[email protected] Standards Track, Covenant Last Call
2 KCC 2: Authority Schemes Username@IzioDev Email[email protected] Email[email protected] Standards Track, ABI Last Call
20 KCC 20: Fungible Token Covenant Specification Username@Manyfestation Email[email protected] Username@michaelsutton Email[email protected] Email[email protected] Username@IzioDev Email[email protected] Standards Track, Application Last Call
23 KCC 23: MJ: Metadata JSON Username@Manyfestation Email[email protected] Standards Track, Application Draft

What are KCCs?

A Kaspa Call for a Convention (KCC) describes a shared convention around which independent ecosystem implementations can converge. Subjects include covenant concepts, Program ABIs, authority schemes, and fungible-token covenants.

KCCs and KIPs

KCCs support interoperability between applications and tools. Changes to consensus or core-node behavior belong in Kaspa Improvement Proposals (KIPs).

For submission and review, read KCC 0: Purpose and Guidelines.