# Kaspa Finalizes KCC-20 Token Standard, Leaving Adoption to Builders By Simon Yoon Canonical URL: https://www.tokenpost.com/news/technology/37279 Published: 2026-10-22T01:24:33.000Z Updated: 2026-10-22T01:24:33.000Z Section: Technology > KCC-1 and KCC-2 also reached Final on Oct. 21. The conventions do not change Kaspa’s consensus rules or require implementation. Kaspa finalized KCC-20, a convention for fungible tokens built with the network’s covenants, on Oct. 21, setting a shared technical reference while leaving projects free to decide whether to implement it. KCC-1 and KCC-2 also reached Final status that day. KCC means Kaspa Call for a Convention. KCC-1 describes covenant concepts and interfaces, while KCC-2 defines authority schemes. KCC-20 applies those conventions to fungible-token use. The KCC-20 specification covers token-state rules, transfer interfaces, borrowed-receive rules and program information that software can use to interpret token state and construct transfers. Final status marks an ecosystem convention. It does not change Kaspa’s consensus or core-node behavior, and it does not require projects to adopt the standard. The status change also does not establish how widely applications will implement KCC-20 or show that network use has increased. The move concludes the review phase described in [earlier KCC-20 coverage](). ## Links in this article - [earlier KCC-20 coverage](https://www.tokenpost.com/news/technology/35138)