Nacho says KCC-20 testing is in its final stage

Nacho the Kat says final testing is underway and tutorials are being prepared. The team has not published a verified date or step-by-step process for holders to move their KRC-20 tokens.

On October 26, Nacho's official account said final testing would continue over the next few days and that tutorials and guides were in progress. Its post included the KCC-20 tag. On October 27, it said the community was looking forward to KCC-20 integration as soon as possible. Neither post gives holders a migration link, a start date or a procedure to follow now.

Why a new token standard does not move old balances

KRC-20 uses Kaspa transactions interpreted by an external indexer. KCC-20 specifies a fungible token convention for native Kaspa covenants. Its status in the Kaspa Calls for Conventions repository is Final. The repository explains that Final marks an agreed convention, not automatic support from wallets or exchanges.

A KRC-20 balance does not become a KCC-20 balance just because the specification is final. A migration must account for the old token supply and define how holders receive a new asset. Our KRC-20 history and migration guide explains the two systems in more detail.

Where KatBridge stands

In a October 13 update, the Kaspa Alliance for Transparency said KatBridge's KRC-20 routes remained closed and their contracts paused, while migration tooling for KCC-20 was being finalized. A September outline described plans for optional, holder-initiated KRC-20 to KCC-20 transfers. That outline preceded the September indexer incident and is not a current instruction sheet. We have not verified a subsequent notice reopening those KRC-20 routes or announcing a holder migration window.

Ashton's role in Nacho

Ashton, who posts as @argonmining, is a Nacho the Kat co-founder and one of its leading technical contributors. KasMagazine identified him as a co-founder, and Nacho's public Katpool engineering records name argonmining as a decision maker on its NACHO payout architecture. KaspaCom covered his interview about the project's origins and community work. He describes himself on X as a volunteer with the Kaspa Alliance for Transparency and shared an October 26 discussion on the KRC-20 and ERC-20 move to KCC-20. His public work makes him an important technical voice on the transition. We have not independently reviewed that recording or found a formal developer title published by the project.

What holders still need to know

Before anyone acts, the project and bridge operators need to publish the exact eligible balances or snapshot rules, any conversion ratio, supported wallets and exchanges, the destination token identifier, fees, and what happens to tokens already bridged or held on an exchange. The status of the paused KRC-20 route also needs a fresh, dated update. These are reporting questions, not instructions to connect a wallet today.

Until an official process is published and checked, use the project's verified channels to follow updates. Do not treat a direct message, a search ad or a lookalike migration site as the official route. No legitimate migration requires a seed phrase or private key.