Kaspa

Core

<p>Three standards for building on <a href="https://x.com/search?q=%24KAS&amp;src=cashtag_click" rel="noopener noreferrer nofollow">$KAS</a> were recently finalized in #Kaspa's official standards repository, giving developers a common reference for native tokens. KCC-1 sets a common format for covenant apps, the base-layer feature that controls how coins can be spent. KCC-2 defines who can sign off on an action, and KCC-20 covers fungible tokens.</p>
<p>With one format, wallets, apps and block explorers can all read tokens the same way. Every token balance sits inside a coin output on the base layer. Core developer Michael Sutton (<a href="https://x.com/michaelsuttonil" rel="noopener noreferrer nofollow">@michaelsuttonil</a>) is listed among the authors of KCC-20, according to the standard's text in the Kaspa repository.</p>
<h2 id="what-each-standard-does">What each standard does</h2>
<p>According to <a href="https://crypto.news/kaspa-finalizes-kcc-native-token-app-standards/" rel="noopener noreferrer nofollow">crypto.news</a>, the KCC Coordination Forum said in an Oct. 21 announcement that KCC-1, KCC-2 and KCC-20 were final and ready for adoption across the ecosystem. KCC stands for Kaspa Call for a Convention, a design document for shared practices that ecosystem participants may choose to adopt, <a href="https://www.tokenpost.com/news/technology/37762" rel="noopener noreferrer nofollow">TokenPost reported</a>.</p>
<p>KCC-1 defines shared terms and data layouts for covenant programs, along with an application binary interface (ABI) for interacting with them. KCC-2 sets out five authority methods: Schnorr public keys, Schnorr key hashes, ECDSA key hashes, scripts and covenant identifiers, per the same TokenPost report.</p>
<p>KCC-20 builds on the first two. <a href="https://primexbt.com/news/kaspa-finalizes-three-kcc-standards-for-covenants-authorization-and-tokens/" rel="noopener noreferrer nofollow">PrimeXBT's news desk reported</a> that it defines token amounts, ownership and transfer interfaces, and that each token covenant must publish program information software can use to decode state and construct transfers. The KCC-20 text in the Kaspa repository also describes a feature called borrowed receive.</p>
<h2 id="optional-conventions-not-a-network-change">Optional conventions, not a network change</h2>
<p>The standards are not a consensus upgrade. TokenPost noted that the conventions do not change Kaspa's consensus rules or require projects to implement them, which leaves adoption to builders.</p>
<p>They follow the Toccata upgrade, which <a href="https://www.tokenpost.com/news/technology/27921" rel="noopener noreferrer nofollow">TokenPost reported</a> went live on Kaspa's mainnet on June 30, 2026. That upgrade added programmable outputs through covenants, transaction introspection, native zero-knowledge verification and sequencing support for based applications. Covenants let transaction outputs carry spending conditions and state-transition rules, the base capability that token standards such as KCC-20 build on.</p>
<p>For developers, the practical benefit is interoperability. If wallets, indexers and explorers follow the same specifications, a token issued by one team should display and transfer the same way across tools. Whether projects adopt the standards in practice will determine how much that matters for the Kaspa ecosystem.</p>
<h2 id="sources">Sources</h2>
<p><a href="https://crypto.news/kaspa-finalizes-kcc-native-token-app-standards/" rel="noopener noreferrer nofollow">crypto.news: Kaspa finalizes 3 standards for native tokens and covenant apps</a><br><a href="https://www.tokenpost.com/news/technology/37762" rel="noopener noreferrer nofollow">TokenPost: Kaspa finalized KCC-2 and KCC-20 before KCC-1</a><br><a href="https://github.com/kaspanet/kccs/blob/main/kcc-0020.md" rel="noopener noreferrer nofollow">Kaspa KCC repository: KCC-20 specification</a></p>

Kaspa now has one shared playbook for its native tokens

목차

BSCN

2026년 10월 27일에 게재된 다른 기사

무료 뉴스레터에 가입하여 매일 최신 암호화폐 소식을 받아보세요!