Chainlink CCIP - Cross-Chain Interoperability Protocol
Build with CCIP
Build cross-chain applications using the CCIP API, SDK and CLI. Send data and tokens across blockchains with built-in security, whether you’re prototyping locally or running in production.
Read the CCIP 2.0 announcement on the Chainlink blog: additive security with cross-chain verifiers, built-in compliance, and configurable settlement speeds.
Quick Links
Enable a Cross-Chain Token
Configure how a token behaves across chains, including supply management, permissions, and supported networks.
Programmable Token Transfers
Combine value and execution in a single cross-chain operation. Use this when value transfers alone are not enough.
CCIP Message Lifecycle
Understand the lifecycle of a CCIP 2.0 message, from creation to finality across chains.
Tools
CCIP REST API
REST API for querying CCIP message status, execution details, and network data.
TypeScript SDK
Client library for interacting with CCIP from applications and backend services.
CLI
Command-line tooling for interacting with CCIP and automating common development and operational workflows.
Starter Kits and Utilities
CCV Starter Kit
Run your own Cross-Chain Verifier (CCV) cell for CCIP: deploy the verifier and aggregator into Kubernetes you already operate, expose it, and scale to a committee.
Foundry Starter Kit
Opinionated starter project for building CCIP applications with Foundry. Includes Solidity-first workflows for testing and extending CCIP integrations.
Hardhat Starter Kit
Opinionated starter project for building CCIP applications with Hardhat. Includes preconfigured contracts, scripts, and workflows for common CCIP use cases.
CCIP Solidity Interfaces & Contracts
Solidity interfaces and contracts for integrating CCIP directly into smart contracts.
Developer Resources
Transfer Tokens (Contract)
Unlock seamless token transfers from contracts; learn, code, and deploy.
Transfer Tokens with Data (PTT)
Programmable Token Transfers: attach data/logic to token movements.
Defensive Transfers
Patterns for safer programmable transfers and failure modes.
Register CCT — Burn & Mint (Hardhat/Foundry)
Implement burn-mint token registration using Hardhat or Foundry.
Register CCT — Lock & Mint (Hardhat/Foundry)
Implement lock-mint token registration using Hardhat or Foundry.
Set Token Pool Rate Limits
Update rate limiter settings for CCTs using your dev toolchain.
Send Arbitrary Messages
Application-level cross-chain messaging patterns and examples.
A → B → A Confirmation Pattern
Reliable two-step acknowledgement pattern for cross-chain workflows.
Test CCIP Locally
Run local test environments for CCIP development and experimentation.
Changelog
Announcing CCIP 2.0
CCIP 2.0 introduces new opt-in features:
- Additive security: Add issuer, third-party, or institution-operated Cross-Chain Verifiers (CCVs) for additional verification and control. The default remains the secure, battle-tested CCIP DON.
- Faster-than-finality (FTF) transfers: Control confirmation parameters for standard or faster-than-finality cross-chain execution, tailored to your needs and risk threshold. The default remains waiting for full finality.
- Modular fee components: Customize fees for your token or your verifier.
- Built-in compliance functions: Native integration with the Chainlink Automated Compliance Engine (ACE) enables policy checks without breaking composability.
- Permissionless execution / No Exec: Customize execution by opting into No Exec (more controlled execution), using a custom executor, or executing permissionlessly. The default remains the Chainlink executor service.
The CCIP Architecture Overview explains the new modular architecture of CCIP 2.0. The Router contract, CCIP's single point of interface, remains unchanged on all networks.
This release ships with a full suite of developer tooling, including the CCIP API, SDK, CLI, and CCV Starter Kit.