> For the complete documentation index, see [llms.txt](https://argon-4.gitbook.io/argon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argon-4.gitbook.io/argon-docs/using-enclave/collectibles-and-names.md). # Collectibles and names Collectibles (KRC-721 and ERC-721) and names (KNS on Kaspa, INS on Igra): viewing, transferring, registering, and managing them. Enclave keeps collectibles and names in their own registers, apart from fungible balances. Both kinds of asset are **indexed facts**: Kaspa confirms the transactions, and an indexer or contract read tells Enclave which item they represent. Enclave says so on every page, and shows nothing when an indexer cannot answer. ## Collectibles Compact: **Home → Collectibles**. Studio: **Collectibles** on the rail. The gallery groups works by collection. Open one for its dossier: artwork (or *No artwork published yet*), title and token id, description, traits, protocol and source, the account that holds it, and its contract or ticker. | Protocol | Network | Source of truth for ownership | | -------- | ------- | --------------------------------------------------------------------------------- | | KRC-721 | Kaspa | KAT's KRC-721 indexer (a second replica can be selected under Settings → Network) | | ERC-721 | Igra | The collection contract, read through the Igra endpoint | **Transfer** sends a collectible to a Kaspa address (KRC-721, a commit-and-reveal package) or an Igra address (ERC-721, a Kaspa-carried Igra transaction). Transfers to the collection's own contract are refused. Eligible **NACHO KAT** holders see **Stake on Zealous** in both Compact and Studio; it opens the staking desk under [Earn](/argon-docs/using-enclave/earn.md#nacho-kat-staking). Watch-only items do not offer staking. ### Bridging a collectible Collections that KAT has deployed on Igra can move between the two networks through **Kat Bridge**. A KRC-721 from such a collection shows **Bridge to Igra**; its bridged ERC-721 shows **Return to Kaspa**. Today that is **NACHO KATs**; other collections gain the action only once the bridge has deployed a contract for them, so a collectible is never sent somewhere it cannot arrive. Each direction is one approval. Going out, SureSign locks the collectible with your Igra address bound to it and sends it to KAT's vault; KAT mints the same token id to you on Igra, usually within a few minutes. The 10 KAS bridge fee is paid on that transaction and is waived when the paying address holds a KATCLAIM collectible numbered 736 to 843 (see [Fees](/argon-docs/using-enclave/fees.md)). Coming back, the bridged copy is burned on Igra for the bridge's live burn fee in iKAS and KAT releases the original to this wallet's Kaspa address. The destination is always an address Enclave derives itself; there is nothing to type. Kat Bridge is a **custodial** bridge: between the two legs, KAT holds the collectible. If the second leg does not arrive, the party to ask is KAT. If Enclave closes between the Kaspa commit and reveal, **Resume** uses the encrypted journal to finish the same deposit. Review the original Igra recipient again. Recovery preserves the embedded bridge authorization and does not charge the bridge fee a second time. A completed Kaspa reveal still needs the bridge to process it; it does not prove the collectible has arrived on Igra. When the KRC-721 indexer is catching up the page says **Indexer catching up** and offers **Try other replica**. *Collectibles have not loaded yet. Nothing is shown rather than a guess.* Collectibles ends with **Collectible tools**: minting and creating collections are described under [Tools → Collectible tools](/argon-docs/using-enclave/tools.md#collectible-tools). ## Names Compact: **Home → Identities**. Studio: **Names** (reached from Home and Collectibles). The page shows your **primary identity** on each network, every other name you hold under *Also held*, the address each resolves to, and its state. Names are lookup facts from the KNS and INS indexers, and the page says so. ### Kaspa names (KNS) A KNS name ends in `.kas` and is an inscription on Kaspa, recognized by the KNS indexer. * **Look up a name** checks whether a name is taken and what it resolves to. * **Register** lives under [Tools → Identity tools](/argon-docs/using-enclave/tools.md#identity-tools), reached from **Identity tools** at the foot of Names. Availability and the length-based fee are shown as you type; the review names the fee again. * **Set as primary** signs a message (no KAS moves) that the indexer uses to mark the name as this address's primary. * **Inscribe text**, also under Identity tools, attaches a text record for 1 KAS. * **Transfer** sends the name to another Kaspa address. Anyone paying a `.kas` name relies on the KNS indexer to resolve it. Enclave resolves a name again at the moment of approval and stops if it changed. See [Transfer](/argon-docs/using-enclave/transfer.md#send-kas). ### Igra names (INS) An INS name ends in `.igra` and lives in the INS registry contracts on Igra mainnet. Enclave pins the registry, controller, listing, and reverse-record contracts and refuses any other. | Operation | Notes | | --------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Register** | Under [Tools → Identity tools](/argon-docs/using-enclave/tools.md#identity-tools). *Forever* or *Annual* (1 to 10 years); availability and the price are read from the registry as you type and again before you plan. | | **Renew**, **Make forever** | Extend an annual name, or convert it to a forever name. | | **Set primary** | Make this the name your Igra address resolves back to. | | **Set target** | Point the name at an Igra address. | | **Approve market**, **List**, **Buy**, **Cancel listing** | Sell or buy names on the INS listing contract. | Subnames are not offered: the INS Registry V2 has them disabled, and SureSign refuses to plan them. Every INS write is an Igra transaction carried by Kaspa and reviewed by SureSign; see [Igra](/argon-docs/using-enclave/igra.md).