Cross-Chain Token (CCT) — Canton
Choose the guide that matches your starting point:
New Registry instrument
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 — 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 — 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:
- Verify on-ledger configuration (TAR mapping, pool address, rate limiters).
- Stand up the Explicit Disclosure Service for your pool.
- Run test transactions — see CCIP on 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.