# 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 — a costly and complex undertaking.

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 — making it possible to build applications that span multiple networks as if they were one.

For institutions adopting blockchain, CCIP acts as a unified connectivity layer: integrate once, 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.

2. **Move tokens across chains (Token Transfer)** — Transfer tokens to a wallet or contract on a different blockchain. Simple, direct asset movement between chains.

3. **Move tokens + data together (Programmable Token Transfer)** — Send tokens and instructions in one transaction. For example: 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 key 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 transfers:** Control confirmation parameters, enabling standard or faster-than-finality cross–chain execution tailored to your needs and risk threshold.

3. **Permissionless Execution / No - Exec:** Customize execution by either setting to No Exec (for a more controlled execution), use a custom executor, or permissionlessly execute

4. **Modular fee components:** Customize fees for your token or your verifier

5. **Built in Compliance Functions:** Native integration with Chainlink [Automated Compliance Engine (ACE)](/ace) allows policy checks without breaking composability.

All of these are opt-in features.

## CCIP 2.0 Defaults

Just as in previous versions, in CCIP 2.0, 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. Messages get attempted for execution by the default Chainlink executor
4. Existing CCTs, sender-receivers will use the default settings and run as-is - no changes are needed by integrators or token issuers.

All the new features are opt-in features.

## 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:** Cross-chain transactions are validated by default by independent, decentralized oracle networks (DONs).

- **Rate limiting:** Configurable policies cap token flows on both source and destination chains, limiting exposure in the event of an exploit.

- **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, ensuring no single party can push through a malicious change.

- **Battle-tested infrastructure:** CCIP 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. Cross-chain systems introduce additional failure modes compared to single-chain applications. Messages must be verified correctly, and protected against replay or manipulation.

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/cross-chain-tokens/register-from-eoa-burn-mint-foundry) — 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.