> For the complete documentation index, see [llms.txt](https://docs.catalog.cat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalog.cat/catalog-faq.md). # CATalog FAQ Frequently Asked Questions about CATalog ### What is CATalog? CATalog is a decentralized, on-chain shared database containing CAT asset details such as symbols, names, and display images. CAT issuers register their CATs and receive an NFT which can be used to change the corresponding entry's details at any time. Verifiers - usually marketplaces or sites that display CAT data - may maintain curated lists of CATs that meet their listing rules (e.g., 'The CAT is not trying to impersonate another CAT'). Because everything is on-chain and on DataLayer, all websites, wallets, and dApps can see data and act on it. **Registration != verification.** On-chain registration establishes ownership of a TAIL hash in the shared registry. Verifier curation is an optional second layer: marketplaces and sites apply their own policies on top of the on-chain data. ### How is a CAT's owner determined? The owner of a CAT is defined as the first entity to register that CAT's TAIL program on CATalog. For this reason, issuers **must** use a CAT issuance tool that supports CATalog in order to avoid someone else claiming their CAT's entry. ### How should I refer to CATalog? Please always spell CATalog like this sentence does - the first three letters should be in uppercase, while the rest of the word is in lowercase. The only exception to this rule is Rust code, where you may spell CATalog as `Catalog` to meet naming conventions. ### What are the fees to list a CAT? Registration fees are stored on-chain in the registry state as `registration_price` (CAT mojos paid to the payment CAT defined by `cat_maker_puzzle_hash`). At the time of writing, mainnet commonly uses **5 wUSDC.b** per entry, but **always check the current on-chain state** - the price singleton can change both the fee token and the amount. CATalog entries do **not** expire and do not require renewal fees. Verifiers may require additional funds in exchange for listing or curating CATs. Fee governance flows through a **Medieval Vault** multisig (6-of-10 [warp.green validators](https://docs.warp.green/#who-are-the-validators) on mainnet), which updates registry pricing via the `delegated_state` action. ### How do I register a CAT? Registration is a two-phase process: 1. Create a precommitment coin (payment CAT locked with TAIL reveal and NFT recipient) 2. Wait `relative_block_height` blocks (typically 32 on mainnet), then complete registration At launch, a web app that makes this process very easy is planned. You can also use the [slot-machine](https://github.com/Yakuhito/slot-machine) CLI with a running [Sage wallet](https://github.com/xch-dev/sage): ```bash cargo run -- catalog register --tail-reveal --ticker ... --name ... ... ``` If the precommit becomes invalid (wrong fee, wrong CAT, or TAIL already registered), use `catalog register --refund`. Full command reference: [CLI Reference](/technical-manual/cli.md). ### How do I know CATalog was properly deployed? Anyone can use [slot-machine](https://github.com/Yakuhito/slot-machine/) with [chia-wallet-sdk](https://github.com/xch-dev/chia-wallet-sdk) to verify CATalog's deployment: ```bash cargo run -- catalog verify-deployment # mainnet cargo run -- catalog verify-deployment --testnet11 ``` This checks the launcher, premine registrations (`catalog_premine_mainnet.csv`), price schedule (`catalog_price_schedule_mainnet.csv`), and state scheduler wiring against trusted CSVs in the slot-machine repo. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.catalog.cat/catalog-faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.