# Cross-Chain Token (CCT) — Canton
Source: https://docs.chain.link/ccip/tutorials/canton/cross-chain-tokens
Last Updated: 2026-06-27

> For the complete documentation index, see [llms.txt](/llms.txt).

Choose the guide that matches your starting point:

## New Registry instrument

**[Registry Issuer Guide](/ccip/tutorials/canton/cross-chain-tokens/registry-issuer-guide)** — Full workflow from Registry onboarding through instrument creation, mint, BurnMint pool deployment, and Token Admin Registry registration. Includes optional `canton-registry-kit` CLI automation.

Use when: you are issuing a token through Digital Asset's Registry utility and connecting it to CCIP for the first time.

## Existing instrument — BurnMint

**[BurnMint Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/burn-mint-token-pool)** — Deploy a BurnMint pool, register on TAR, and enable a lane. Assumes supply is already on-ledger and the instrument supports `BurnMintFactory`.

Use when: your instrument admin equals the intended pool owner and the token supports burn/mint.

## Existing instrument — LockRelease

**[LockRelease Token Pool Deployment](/ccip/tutorials/canton/cross-chain-tokens/lock-release-token-pool)** — Deploy a LockRelease pool, fund liquidity, configure pre-approval, register on TAR, and enable a lane.

Use when: fixed total supply, transfer pre-approvals available, and you prefer lock/release over burn/mint.

## After deployment

All guides end with a **Go Live** checklist:

1. Verify on-ledger configuration (TAR mapping, pool address, rate limiters).
2. Stand up the [Explicit Disclosure Service](/ccip/concepts/canton/explicit-disclosure) for your pool.
3. Run test transactions — see [CCIP on Canton — Overview](/ccip/concepts/canton/overview) for send/execute flows.

Cross-chain send and receive (`CCIPSender.Send`, `CCIPReceiver.Execute`) are validated by Chainlink operations once your token is registered and lanes are configured.