Skip to main content

Chain keys

Chains are written <family>:<id>:

Which chain does what

  • Mint chain: your program mints on one chain, returned as mint_chain by the catalog. An EVM program has one ERC-721 contract; a Solana program has one Metaplex Core collection.
  • Payment chains: customers pay on Base or Solana, whatever your mint chain (Payments). On EVM one key is the same address on every EVM chain, so a customer paying from Base receives the NFT at that same address on your chain.
  • Payout chain: sell-backs pay USDC, by default on the token’s own family: Base (evm:8453) for an EVM program, Solana (solana:mainnet) for a Solana program.
  • Refunds always go out as USDC on Base.
  • Addresses: EVM addresses are returned lowercase; Solana addresses as base58 (case-sensitive).
Solana payouts are not switched on yet (PAYOUT_CHAIN_NOT_ENABLED). Until they are, a Solana program sends payout_chain: "evm:8453" and a Base payout_address with every sell-back quote.

Token identity

Every token has a decimal token_id, which is the {tokenId} in every token path, on both chain families.

The EVM contract

The EVM contract (name CatchBack Cards, symbol CBCARD) exposes what an integration needs:
The Quote tuple, the ABI and a viem example are on Sell-back.

Metadata

Every token carries a standard metadata URL that wallets and marketplaces read without a key, from anywhere:
  • Attributes include Category, Set, Year, Number, Grade, Cert, Language, Brand, Size and Condition where the item has them, and Status (Vaulted, or Redeemed once burned).
  • The metadata never includes a price.
  • It is cached for a few minutes, and a token whose mint hasn’t been sent yet answers 404.
Details: Token metadata.