Getting Started (Canton)
Chainlink CCIP supports the Canton Network, enabling regulated institutions and enterprises to move tokens and messages between Canton and 85+ supported chains.
What CCIP enables on Canton
- Cross-chain token transfers: Bridge CIP-56 instruments to and from EVM, Solana, and other CCIP-supported chains via token pools.
- Cross-chain messaging: Send arbitrary data between Canton and remote chains using
CCIPSenderandCCIPReceivercontracts. - Programmable token transfers: Combine token movement with destination-chain logic (coming soon in starter-kit tutorials).
How Canton differs from other CCIP chains
Canton uses Daml smart contracts and a privacy model where parties need explicit disclosure of contracts they are not stakeholders on. CCIP on Canton therefore relies on:
- On-ledger CCIP contracts (OnRamp, OffRamp, PerPartyRouter, token pools, Token Admin Registry).
- Off-ledger Explicit Disclosure Services (EDS) operated by Chainlink (global CCIP contracts) and by token pool operators.
- The CCIP CLI / SDK to assemble disclosures, proofs, and ledger submissions for send and execute flows.
Read Overview for end-to-end send and receive flows.
Recommended path
| Goal | Start here |
|---|---|
| Understand cross-chain flows | Overview |
| Issue a Registry token and connect CCIP | Registry Issuer Guide |
| Connect an existing CIP-56 instrument (burn/mint) | BurnMint Token Pool Deployment |
| Connect an existing CIP-56 instrument (lock/release) | LockRelease Token Pool Deployment |
| Operate pool disclosure infrastructure | Explicit Disclosure API |
Before you begin
Coordinate with Chainlink CCIP operations for:
- CCIP owner party ID and hosted contract addresses (Token Admin Registry, FeeQuoter, RMNRemote).
- Remote chain selectors and lane configuration for your target networks.
- CCIP DAR packages on your participant (typically provisioned by ops).
Confirm party IDs and contract addresses with Chainlink CCIP — values in these docs may change, including upgrade-incompatible changes.