Nacho's KCC-20 migration is live. Here is what holders need to know

After more than two years on KRC-20, Nacho opened a one-way move to a covenant token on Kaspa L1 on October 30. The route is live, but the deadline, supply change and thin new-market liquidity all deserve a close read.

Nacho the Kat announced on October 30 that its KRC-20 to KCC-20 migration had opened. It directed holders to the KAT Bridge migration page, published a KCC-20 covenant ID and set January 31, 2027 as the final day to move. That is a real change from its October 27 status, when final testing was still underway and no verified holder procedure was available.

What is moving, and why?

KRC-20 records token operations in Kaspa transactions, but a separate indexer interprets those operations and keeps token balances. KCC-20 is a convention for tokens controlled by Kaspa L1 covenants. Moving NACHO requires a project-specific transfer process. The new standard does not convert old balances by itself.

The move followed a September 20 incident involving the Kasplex KRC-20 indexer and bridged NACHO and ZEAL balances. Nacho's account of the incident says the vulnerability was in that indexer, not Kaspa's base network or KAT Bridge. It says the combined NACHO supply across KRC-20, Igra and Kasplex L2 exceeded the original 287 billion after the attack. The community then announced a 330 billion starting supply for KCC-20 NACHO. That increase means dilution, a material part of the story for holders. Nacho says buybacks, auction proceeds and voluntary burns are intended to reduce the excess. Those measures are plans, not a guarantee of a particular final supply or market outcome.

How the holder route works

The project's official guide asks holders to select where their NACHO currently sits: Kaspa KRC-20, Igra, or Kasplex L2. Each origin has its own route to the KCC-20 token on Kaspa L1. Nacho describes the process as one-way and holder-initiated, with a standard 1:1 conversion ratio and an option to burn part of the balance voluntarily during the move. It is not automatic. Holders need the guide for their specific starting network rather than assuming one wallet procedure works everywhere.

The official migration interface is katbridge.com/migrate. Nacho identifies 41d44970ba6307bcec418f677fd253778d0ffa47750d179dff647061aa6c0d40 as the sole official KCC-20 NACHO covenant ID and points to its Kascov record for verification. The project's site says the migration window ends January 31, 2027. It also says tokens left on the old networks after the window will not be eligible for a later KCC-20 migration. The community is still discussing what happens to unmigrated tokens; its homepage says no final burn decision has been made.

The token moved. The market is still catching up.

A live migration does not mean KCC-20 NACHO has deep trading liquidity. On November 2, Nacho cautioned against trading the new token for now. It said ZealousSwap was not yet live on Kaspa L1 and Kron did not have sufficient liquidity to support trading. That is the team's current market warning, not a forecast about where liquidity will be later. Nacho also posted a KasWare wallet update after launch concerning the KCC-20 ticker, logo, decimals and token UTXO compounding.

Where Ashton fits

Ashton, @argonmining, was identified by KasMagazine as a Nacho co-founder and is an important technical voice around the project. Public Katpool engineering decisions name him as a decision maker on NACHO payout architecture. He invited listeners to a discussion in the days before the launch. Those public records support his broader technical role; they do not by themselves establish which parts of the migration bridge he built. We have not verified a contributor list or audit trail for the bridge.

How did the move go for you?

For holders, the useful questions are practical: Which starting network did you use? Was the route clear? Did the destination token appear correctly in your wallet? Were fees and timing what you expected? Did you encounter an issue, and was support able to resolve it? Tell Kaspa News on X what happened, including the good parts. Do not post seed phrases, private keys or sensitive wallet details. We will use attributable, checkable experiences to follow the rollout.