NACHO / INTEGRATION REFERENCES
For Exchanges, Wallets & Developers
A starting point for identifying NACHO and finding protocol, service and community references.
Canonical identity
- Community / character
- Nacho the Kat
- Native token ticker
- NACHO
- Network
- Kaspa
- Network coin
- KAS
- Native token protocol
- KRC-20
NACHO's original KRC-20 token is on Kaspa. The migration guides cover KRC-20, Igra and Kasplex as starting points for the move to KCC-20. Match the covenant id, not the ticker.
Go to the source
Identifiers and addresses
A token identifier, a network identifier, a bridge service address and a user’s exchange deposit address serve different purposes. Never treat a listed identifier as an instruction to send funds.
- Exact network identifier
- Not confirmed here. Use the relevant primary documentation and community confirmation.
- NACHO-specific KCC-20 identity / migration
- Not confirmed here. Use the relevant primary documentation and community confirmation.
- Bridged asset identifiers
- Not confirmed here. Use the relevant primary documentation and community confirmation.
- Bridge / service addresses
- Not confirmed here. Use the relevant primary documentation and community confirmation.
Specifications & code
- Rusty Kaspa on GitHubReference node implementation (external site)
- Kasplex KRC-20 nodeKRC-20 protocol software / indexer (external site)
- KCC-20 specification · Last CallCovenant-token specification (external site)
- K.A.T. on GitHubCommunity / ecosystem repositories (external site)
This community website provides introductions and references. Its repository is not a protocol implementation. Individual repositories in an organization may serve different purposes.
NACHO migration: route guidance
Only this covenant ID is official KCC-20 NACHO. Always verify it.41d44970ba6307bcec418f677fd253778d0ffa47750d179dff647061aa6c0d40 kascovThe migration guides cover three starting points: KRC-20 on Kaspa, Igra and Kasplex. Each guide ends at the same KCC-20 covenant. Confirm the route and the deadline before you send tokens. This page is not the transaction screen.
Bridge context
Bridge mechanisms, supported assets and live availability are separate checks. Use the operator’s current documentation and route status; no unconfirmed network identifier or service address is published here.
Current route status and holder guideGo to the source
Brand & logo
The site uses approved Nacho artwork. Redistribution and derivative permissions are still unresolved; ask the community before reusing these assets.
Integration questions
A dedicated public integration contact is not yet confirmed. The community Discord is a place to ask for the appropriate contact; it is not a support commitment.
Nacho Discord (external site)