Chainlink CCIP
Cross-Chain Interoperability Protocol (CCIP) enables secure cross-chain token transfers and arbitrary messaging between blockchains. Unlike simple token bridges, CCIP supports programmable cross-chain interactions - send tokens with instructions, trigger multi-chain workflows, and build chain-abstracted dApps.
Cross-Chain Message Flow
Click "Send Message" to watch a CCIP cross-chain transfer: source chain -> Committing DON -> Risk Management check -> Executing DON -> destination chain.
? Security Architecture Comparison
CCIP's multi-layer security model vs typical bridge architectures.
Token Transfer Modes
Tokens are locked in a pool on the source chain. Wrapped versions are minted on the destination. Used for tokens that don't natively exist on the destination chain.
Tokens are burned on the source chain and minted natively on the destination. Used for tokens with native multi-chain deployments. No wrapped tokens needed.
Tokens are locked on source and unlocked from a pre-funded pool on the destination. Fastest settlement since tokens already exist on both sides.
* Programmable Token Transfers
Send any encoded data cross-chain - not just tokens. Trigger function calls, sync state, pass governance votes, or update configurations across chains. The destination contract's ccipReceive() handler processes the message.
Combine token transfers with instructions in a single cross-chain message. Example: send USDC to a lending protocol on another chain with encoded instructions to deposit into a specific vault and set a liquidation threshold.