Cross-Chain Tokens (CCT)
Cross-Chain Tokens (CCT) let a token administrator configure a token pool and its remote chains so the token can move across chains through CCIP. The SDK exposes one manager per chain family rather than a single cross-family API:
| Chain family | Manager | Import |
|---|---|---|
| EVM | EVMTokenManager | @chainlink/ccip-sdk/cct/evm |
| Solana | SolanaTokenManager | @chainlink/ccip-sdk/cct/solana |
| Canton | CantonTokenManager | @chainlink/ccip-sdk/cct/canton |
Pick your path by what you need to do:
- To set up a new token pool end to end, follow the guide for your chain family.
- To look up pool types and version support, see Reference › Pool types.
- To inspect a pool that's already deployed, see Reference › Inspecting pools.
Choose an execution mode
Every write operation comes in two forms, so you can sign directly or hand off to an external signer:
generateUnsigned<Operation>builds an unsigned transaction or instruction set for multisig, offline, or external signing workflows.<operation>signs and submits with the chain-family wallet you supply.
Choose the unsigned form when the account that owns the token, registry, or token pool is a multisig. The signed form validates the wallet and waits for the submitted transaction to confirm.
Typical setup flow
Every chain family follows roughly the same arc:
- Deploy a new token, or use an existing token on the local chain.
- Register the token administrator (
registerAdmin, thenacceptAdmin) where required. - Deploy or initialize the token pool.
- Configure each remote chain's token, pool, rate limit, and any allowlist or verifier requirements.
- Associate the pool in the TokenAdminRegistry (
setPool). This comes after the remote-chain configuration on every chain family; on Solana it also needs a populated address lookup table. - Fund a lock/release pool before sending transfers.
- Read back the pool and registry state to verify the final configuration.
The exact sequence and required parameters differ by chain family, so follow the guide for your chain family rather than copying parameters between chains.
Guides by chain family
- EVM: ERC-20 token, TokenAdminRegistry, v2 pool, lockbox, and remote-chain operations.
- Solana: SPL mint, canonical pool programs, PDAs, lookup tables, and remote-chain operations.
- Canton: registry-pool deployment, atomic lane initialization, and Canton read operations.
Pool administration changes what can be transferred cross-chain. Test with the target pool type, token authority, router, and remote-chain configuration before using a production token.