CCIP Tutorials (Canton)
These tutorials cover the primary integration paths for CCIP on Canton. The initial release focuses on Cross-Chain Token (CCT) deployment for institutional issuers.
Cross-Chain Token (CCT)
Connect a Canton instrument to CCIP so it can move across supported chains.
| Guide | When to use |
|---|---|
| Registry Issuer Guide | Issue a new token via Digital Asset Registry and connect CCIP end to end |
| BurnMint Token Pool Deployment | Existing CIP-56 instrument with burn/mint authority |
| LockRelease Token Pool Deployment | Fixed-supply instrument with transfer pre-approvals |
Application integration (coming soon)
Organized by direction to match other non-EVM CCIP tutorials and chain-family switching in the sidebar.
| Source (Canton → remote) | Destination (remote → Canton) | |
|---|---|---|
| Token Transfers | Source | Destination |
| Arbitrary Messaging | Source | Destination |
| Programmable Token Transfers | Source | Destination |
Tutorials will reference a ccip-tools-ts starter kit. Destination flows use the SDK's find-or-create CCIPReceiver behavior — no separate receiver deployment page.
Prerequisites (all CCT guides)
- CCIP DAR packages on your participant (
contracts/dars/v2_0_0) - CCIP contract references from Chainlink ops (owner party, TAR, RMNRemote, FeeQuoter)
- OAuth client with
can_act_asrights for your ledger parties - Understanding of token pools and explicit disclosure