# What is Chainlink CCIP? Source: https://docs.chain.link/ccip/overview Last Updated: 2026-03-13 > For the complete documentation index, see [llms.txt](/llms.txt). Blockchains don't natively talk to each other. If your application, platform, or backend needs to work across multiple chains, you'd normally have to build and maintain a separate integration for each one, and that's costly and complex. Chainlink CCIP solves this. It's a single interoperability layer that lets you transfer messages without building bespoke infrastructure for every chain pair. Whether you're a DeFi protocol expanding to new networks, an institution connecting traditional systems to multiple chains, or a developer building cross-chain applications, CCIP provides one consistent interface backed by Chainlink's battle-tested oracle infrastructure. ## How CCIP fits into the Chainlink platform CCIP is part of Chainlink's broader suite of decentralized services. While [Data Feeds](/data-feeds) bring real-world data onchain and [CRE](/cre) handles smart contract execution, CCIP connects the chains themselves, so you can build applications that span multiple networks as if they were one. For institutions adopting blockchain, CCIP is a unified connectivity layer. You integrate once and can reach any supported chain. ## What can CCIP do? CCIP supports three core capabilities: 1. **Send data across chains (Arbitrary Messaging):** Send any encoded data to a smart contract on another blockchain. This lets you trigger actions remotely: rebalance a portfolio, mint an NFT, call a function, or orchestrate multi-step workflows across chains. Token transfers and programmable token transfers are built on arbitrary messaging. 2. **Move tokens across chains (Token Transfer):** Transfer tokens to a wallet or contract on a different blockchain. Token pools lock or burn the tokens on the source chain and release or mint them on the destination chain. 3. **Move tokens + data together (Programmable Token Transfer):** Send tokens and instructions in one CCIP message. For example, you can transfer tokens to a lending protocol on another chain with instructions to use them as collateral and send the borrowed asset back. ## What's new in CCIP 2.0 CCIP 2.0 introduces these new features: 1. **Additive Security:** Add issuer, third-party, or institution-operated Cross-Chain Verifiers (CCVs) where required for additional verification and control: - **Asset-specific verifications** - **Chain-specific verifications** 2. **Faster-Than-Finality (FTF) transfers:** Control confirmation parameters to choose standard or FTF cross-chain execution, based on your needs and risk threshold. 3. **Permissionless Execution / No Exec:** Set the executor to No Exec (for more controlled execution), use a custom executor, or execute permissionlessly. 4. **Modular fee components:** Customize fees for your token or your verifier. 5. **Built-in Compliance Functions:** CCIP integrates natively with the Chainlink [Automated Compliance Engine (ACE)](/ace), so you can run policy checks without breaking composability. All of these are opt-in features. ## CCIP 2.0 Defaults As in previous versions, CCIP 2.0 works this way by default: 1. The Chainlink decentralized oracle network (Chainlink Committee Verifier) verifies each message. 2. Messages wait for full source-chain finality before execution on destination chains. 3. The default Chainlink executor attempts to execute each message. 4. Existing Cross-Chain Tokens (CCTs), sender contracts, and receiver contracts use the default settings and run as-is, so integrators and token issuers don't need to make any changes. All the new features are opt-in. ## Security Model Cross-chain bridges have historically been high-value targets. CCIP is designed with defense-in-depth security, built on the same Chainlink infrastructure that secures tens of billions in DeFi value today. - **Decentralized validation:** Independent, decentralized oracle networks (DONs) validate cross-chain transactions by default. CCIP doesn't rely on a single verifier, machine, or infrastructure provider. It is operated by the same globally distributed, security-reviewed node operators that secure Chainlink Data Feeds, validate major blockchain networks, and run enterprise-grade Web2 infrastructure. A message needs at least 9 of 16 signed attestations to be verified. The operators are Sybil-resistant and independent, with significant experience running mission-critical infrastructure across telecommunications, cloud, and Web3. - **Rate limiting:** Configurable policies cap token flows on both source and destination chains, limiting exposure in the event of an exploit. Token issuers can set separate limits (capacity and refill rate) for FTF and standard transfers. - **Timelocked upgrades:** All security-critical changes go through a timelock contract with a review period. [Node operators](https://ccip.chain.link/nops) can veto upgrades, which reduces the risk that a single party can push through a malicious change. For a detailed breakdown of how messages move through the system, see the [Architecture Overview](/ccip/concepts/architecture/overview). ## Getting Started with CCIP - [**Check supported networks and tokens (CCIP Directory)**](/ccip/directory/mainnet): View available chains, supported tokens, and valid routes between them. - [**Understand how CCIP works (Architecture Overview)**](/ccip/concepts/architecture/overview): See how messages are verified offchain and enforced onchain. - [**Build your first cross-chain flow (Tutorials)**](/ccip/evm/tutorials/application-developers): Step-by-step examples for sending tokens and data. - [**Talk to a CCIP expert**](https://chain.link/ccip-contact): Get implementation guidance from the Chainlink team. > **CAUTION: Disclaimer** > > Chainlink CCIP is an interoperability messaging protocol. Chainlink does not hold or transfer any assets. The > performance and behaviour of applications using Chainlink CCIP may depend on coding, engineering, configuration, and > other technical implementation choices made by developers, token issuers, Cross-Chain Verifiers, and other > participants. Users remain responsible for evaluating, configuring, testing, deploying, operating, and maintaining > their own applications and integrations, including assessing any applicable operational, security, technical, and > legal or regulatory risks. Please review the [Chainlink Terms of Service](https://chain.link/terms) which provides > important information and disclosures. By using Chainlink CCIP, you expressly acknowledge and agree to accept these > terms. Cross-Chain Verifiers (CCVs) may be operated by third parties. The security, availability, governance, and > operational profile of a CCV varies depending on the verifier selected. Users are solely responsible for evaluating > any CCVs used in connection with their applications or integrations and determining whether they are appropriate for > their intended use case. This code represents an example of using a Chainlink product or service. It is provided "AS > IS" and "AS AVAILABLE" without warranties of any kind, has not been audited, and may omit checks or error handling. > Each party intending to use this reference implementation must perform its own audits, security and code review, and > testing before any production deployment and ensure the operation and performance of such code matches expectations. > Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for outcomes due to > errors in this example or how it is deployed or operated. Use of the Chainlink Network is subject to the Chainlink > Foundation Terms of Service, which provides important information and disclosures. By using this code, you acknowledge > and agree to these terms.