CCIP Tutorials: Canton as Destination
Canton as Destination (any2canton) tutorials cover receiving on Canton — Ethereum Sepolia is the source in the starter kit, Canton is the destination.
Tutorials use the ccip-starter-kit-canton on @chainlink/ccip-sdk.
Getting Started
- Prerequisites for Canton as Destination — Clone the starter kit, configure Sepolia and Canton access, and fund TEST/ETH.
- Canton as Destination flow — Execute path in the overview.
Tutorials by Use Case
| Tutorial | Scripts | Description |
|---|---|---|
| Arbitrary Messaging | any2canton:data + manual-exec | Execute an incoming data message on Canton |
| Token Transfers | any2canton:token + manual-exec | Execute an incoming token transfer on Canton |
| Programmable Token Transfers | any2canton:data-and-token + manual-exec | Execute an incoming PTT on Canton |
Common Flow (all any2canton tutorials)
- Send from Sepolia with an
any2canton:*script - Poll message status via the CCIP API or CCIP Explorer
- Run
any2canton:manual-exec— the SDK finds or creates a compatibleCCIPReceiverfor message finality - Fetch proofs from the indexer and disclosures from Global CCIP EDS (+ token pool operator EDS for token messages)
- For token messages: accept the
TransferInstructionto receive LINK on-ledger
Prerequisites
- Starter kit setup
- Funded Sepolia account with ETH (or LINK for fees) and TEST for token tutorials
- Canton party with JWT access for manual execution
- Token pool registered for the instrument — see CCT guides