Chainlink has launched CCIP 2.0, a major upgrade to its Cross-Chain Interoperability Protocol that gives institutions and digital asset issuers more control over how assets move between blockchains.
The upgrade introduces Cross-Chain Verifiers (CCVs), allowing issuers to add their own independent verification layer on top of Chainlink’s default security infrastructure. It also adds built-in compliance controls, configurable transaction finality and faster cross-chain execution options.
CCIP 2.0 is already live and available to institutions and digital asset issuers. Chainlink says assets representing more than $84 billion in cross-chain token value are currently secured through CCIP, with more than $15 billion migrating to the protocol during the past four months.
CCIP 2.0 Lets Institutions Add Their Own Verifiers
The biggest change is the introduction of Cross-Chain Verifiers. Under the standard CCIP setup, Chainlink’s decentralized oracle infrastructure validates cross-chain transactions.
CCIP 2.0 now allows an institution or asset issuer to add another verifier that must also approve a transaction before it can execute on the destination chain.
For example, a bank could operate its own CCV and require both Chainlink’s default verifier and the bank’s infrastructure to cryptographically sign a transaction.
An issuer can also use a third-party CCV instead of operating one internally.
| CCIP 2.0 Feature | What It Does |
| Cross-Chain Verifiers | Adds issuer or third-party verification to transfers |
| Additive security | Requires additional approval on top of default CCIP security |
| Configurable finality | Lets issuers choose confirmation requirements |
| Faster-than-finality transfers | Allows selected transfers to execute before full chain finality |
| Compliance integration | Adds programmable KYC, AML and transaction controls |
| Custom execution | Supports alternative or permissionless execution options |
Table 1. Major Features Introduced With Chainlink CCIP 2.0
Chainlink’s default infrastructure remains in place. The new verifier system is additive, and not a replacement for the existing security model.
Issuers Can Set Their Own Cross-Chain Security Rules
CCIP 2.0 also gives issuers more control over when additional verification applies.
An organization could require an extra verifier only for transactions above a certain value or apply different security rules to different assets.
Chainlink gives the example of requiring additional approval for transfers above $1 million.
Third-party companies can also operate CCVs and charge their own verification fees through an open marketplace.
Infosys, Further Asset Management and Nethermind are among the organizations developing or operating CCV infrastructure, while Amazon Web Services (AWS) and Google Cloud provide starter environments for institutions that want to run their own verifier, giving issuers several choices such as to operate their own verifier, use an external provider or rely on the standard CCIP configuration.
CCIP 2.0 Adds Built-In Compliance Controls
Cross-chain transfers can also carry issuer-defined compliance rules.
CCIP 2.0 integrates with the Chainlink Automated Compliance Engine (ACE), which lets institutions apply policies to assets as they move between networks.
Those rules can include the following:
- Know Your Customer (KYC) checks
- Anti-Money Laundering (AML) controls
- Sanctions screening
- Allowlists and denylists
- Transaction limits
- Exposure limits
- Approval workflows
A token issuer could, for example, restrict transfers so that only approved addresses can receive a regulated asset across multiple blockchains.
That is particularly relevant for tokenized securities, funds and other institutional assets where unrestricted bridging may conflict with regulatory or internal risk requirements.
Institutions Can Choose How Fast Transfers Settle
CCIP 2.0 also changes how institutions can manage transaction finality.
The default setting still waits for full source-chain finality before a cross-chain transfer proceeds. That remains the more conservative option.
Issuers can now choose custom confirmation thresholds for transactions where speed matters more.
Chainlink calls this ‘faster-than-finality’ execution.
For example, an institution might allow a smaller payment to move after fewer confirmations while requiring a large wholesale settlement to wait for full finality.
The system can therefore apply different risk tolerances depending on the transaction.
Ethereum Transfers Could Settle in Seconds
Chainlink is also preparing CCIP for Ethereum’s planned Fast Confirmation Rule.
The feature is being developed with Ethlabs and is intended to let Ethereum transactions reach confirmation within seconds, instead of waiting for full finality before cross-chain execution.
CCIP 2.0 can use those faster confirmation signals once the Ethereum feature launches.
Several decentralized finance protocols are already adopting faster-than-finality transfers, including Aave, Maple and Re.xyz.
The faster option remains configurable rather than mandatory, allowing institutions to choose between speed and stronger finality depending on the transaction.
Security Is a Major Focus After Another Bridge Hack
The upgrade arrives as cross-chain bridge security remains a major issue across crypto.
CCIP 2.0 follows a $292 million exploit [Kelp DAO] of a rival bridge earlier this year, an incident that again highlighted the risks of relying on a single verification mechanism for cross-chain transactions.
Chainlink’s response is to let issuers layer independent verification on top of the default CCIP network rather than placing all trust in one validator or security mechanism.
Under the new model, an attacker would need to satisfy the additional verification requirements selected by the issuer before a cross-chain transfer can execute.
However, that does not eliminate bridge risk, but it lets institutions build additional controls around assets with higher security requirements.
CCIP Now Secures More Than $84 Billion in Cross-Chain Token Value
Chainlink says CCIP currently supports more than $84 billion in total cross-chain token value.
More than $15 billion has migrated to the protocol during the past four months, including several major crypto assets and institutional products.
Examples cited by Chainlink include the following:
- More than $7.4 billion in BitGo’s WBTC
- More than $6.1 billion in Coinbase’s cbBTC
- Kraken’s kBTC
- Wyoming’s FRNT stable token
CCIP also recorded $4.9 billion in cross-chain volume during Q2 of 2026, a 353% year-over-year increase, according to Chainlink’s quarterly review.
The figures show that CCIP was already expanding before the 2.0 upgrade.
Major Institutions Are Supporting the Launch
CCIP 2.0 launches with a broad group of financial and technology companies either integrating the system or supporting the ecosystem.
Chainlink-named organizations include the following:
- Amazon Web Services (AWS)
- Google Cloud
- ANZ Bank
- Fidelity International
- Deutsche Börse Group’s Crypto Finance
- SBI Digital Markets
- Sygnum
- Taurus
- Infosys
- Archax
- xStocks
Chainlink has also previously worked with SWIFT, DTCC, Euroclear, UBS and Wellington Management on institutional blockchain and tokenization projects.
In one project, 24 major financial institutions and market infrastructure providers used CCIP to distribute validated corporate-actions data across DTCC’s blockchain environment and public and private chains.
CCIP 2.0 Targets Tokenized Assets Across Multiple Blockchains
Tokenized stocks, exchange-traded funds (ETFs), funds, commodities, stablecoins and other real-world assets (RWAs) increasingly exist across several public and private networks, creating a distribution problem.
An asset launched on one blockchain cannot automatically move to another without additional infrastructure.
CCIP is designed to let issuers establish security and compliance rules once and apply them across supported blockchains rather than building separate bridging infrastructure for every network.
For regulated issuers, that could reduce the engineering and compliance work required to make the same tokenized asset available across multiple markets.
CCIP 2.0 Also Overhauls Developer Tools
Chainlink also redesigned CCIP’s developer tooling, including its application programming interface (API), software development kit (SDK) and command-line interface (CLI).
Developers now have more control over the following:
- Transaction execution
- Token pool behavior
- Verification
- Fee structures
- Confirmation thresholds
The Router contract, which serves as the main interface for CCIP, remains unchanged across supported networks.
That should allow existing integrations to adopt the new architecture without replacing the core interface they already use.
What Comes Next
CCIP 2.0 is already live, so the next stage will be adoption. The key measure will be whether banks, asset managers and token issuers use the new verification and compliance controls to move more regulated assets across public and private blockchains.
Chainlink already reports more than $84 billion in cross-chain token value secured through CCIP, with major institutions and asset issuers joining the 2.0 launch.
The new CCV model also creates another area to watch. Institutions can now run their own verification infrastructure or rely on specialized third-party providers, potentially creating a broader market around cross-chain security services.
What this means for you: CCIP 2.0 is less about adding another crypto bridge and more about giving institutions control over how their assets cross blockchains. Issuers can now add their own verification, compliance rules and settlement speeds instead of relying on a one-size-fits-all bridge model.
