Getting Started (Canton)

Connect a Canton party to CCIP and run a cross-chain workflow on testnet.

In this guide, you will:

  1. Learn Canton-specific concepts CCIP relies on (Key Concepts)
  2. Choose the right tooling (ccip-starter-kit-canton tutorials vs ccip-tools-ts SDK/CLI for production)
  3. Complete prerequisites and run your first Canton ↔ Sepolia tutorial (send or receive, including manual execution when Canton is the destination)

Who this is for

Institution and enterprise engineers who need to:

  • Bridge CIP-56 instruments or Registry-issued tokens across CCIP lanes
  • Send arbitrary data or programmable token transfers to or from Canton
  • Operate token pool and EDS infrastructure for their instruments

No permission from Chainlink is required for your party to send on a configured lane — you need participant access, disclosures, and fee-token holdings.

What you can build

GoalStart here
First testnet send or receive (Canton ↔ Sepolia)Canton as Source or Canton as Destination
Deploy a token pool and register on TARCross-Chain Token (CCT)
Issue a Registry token end to endRegistry Issuer Guide
Understand send/execute flowsOverview
Operate pool EDSExplicit Disclosure API

Tooling

ToolRole
@chainlink/ccip-sdk / ccip-cliProduction library and CLI — disclosures, fees, send, execute, proofs
ccip-starter-kit-cantonTestnet tutorial scripts (canton2any:*, any2canton:*, cct:*) pre-configured for Canton CCIP testnet ↔ Sepolia

The starter kit uses the same SDK and ledger submit model as ccip-cli with canton-config.json. Use the starter kit to learn; use the SDK or CLI directly for your own applications.

Fees (summary)

  • Sending from Canton: CCIP fees are paid on-ledger in Amulet by default, or LINK with --feeToken link. See Key Concepts — Fees.
  • Sending to Canton: Fees are paid on the source chain (Sepolia ETH or LINK in the starter kit).

Fund your party before running tutorials — npm run check-balance in the starter kit.

Quick start (testnet tutorial)

  1. Read Key Concepts (parties, privacy, manual execution, fees).
  2. Clone and configure the starter kit (party, ledger URL, validator user, transferInstructionUrl).
  3. Pick a direction and tutorial:

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)

What's next

Get the latest Chainlink content straight to your inbox.