# Kaspa Finalized KCC-2 and KCC-20 Before KCC-1 Despite Dependency Rule By Simon Yoon Canonical URL: https://www.tokenpost.com/news/technology/37762 Published: 2026-10-22T11:11:00.000Z Updated: 2026-10-22T11:11:00.000Z Section: Technology > All three standards reached Final on Oct. 21, but KCC-1, a dependency of the other two, was finalized last. Kaspa’s covenant and token standards all reached Final on Oct. 21, but the order left a gap between the dependency rule and when two specifications advanced. The status changes came in the order KCC-2, KCC-20 and KCC-1. A KCC (Kaspa Call for a Convention) is a design document for shared practices that ecosystem participants may choose to adopt. The process rule requires a standard’s KCC dependencies to be Final before it advances to that status. KCC-2 relies on KCC-1, and KCC-20 relies on the other two specifications. KCC-1 was still at Last Call when KCC-2 and KCC-20 advanced. The sequence was mixed: KCC-2 reached Final before KCC-20, matching their dependency order, but both advanced before KCC-1. All three now carry Final status, while the sequence leaves unexplained why the dependency condition was not met at the time of those earlier status changes. The standards cover separate parts of a developer framework. 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. KCC-20 sets state and transfer rules for fungible-token covenants. One KCC-20 feature, borrowed receive, lets a sender use a recipient’s compatible token output without the recipient’s authorization. The transfer must increase the token amount, preserve ownership and extended state, and keep the output’s value in Kaspa (KAS) from decreasing. Changing the output reference can invalidate unconfirmed transactions that use its previous reference. Final status marks a shared reference point for developers. It does not change Kaspa’s consensus rules, require wallets or applications to adopt the standards, or establish how many projects have adopted them. The milestone extends [earlier coverage of KCC-20’s Final status]() with the sequence of its related specifications. ## Links in this article - [earlier coverage of KCC-20’s Final status](https://www.tokenpost.com/news/technology/37279)