Chainlink Unveils CCIP 2.0 With Optional Speed and Compliance Upgrades

Chainlink rolls out major protocol update

Chainlink has officially launched version 2.0 of its Cross-Chain Interoperability Protocol (CCIP) on September 28. This update adds optional features for custom transaction verification, configurable settlement speeds, and compliance checks to help move tokens and messages between different blockchains.

The new version is live on the mainnet, but availability varies by route. While connections to Arbitrum One, Avalanche, and Base have been updated to version 2.0.0, the route to Aptos remains at version 1.6.0. The overall system currently supports 78 mainnet networks running various protocol versions.

Key changes in the new protocol

• Existing token pools and users can continue operating without changes, using the default setting of waiting for full confirmation on the source blockchain.
• New features like custom verifiers and faster transfers require an explicit opt-in and a contract upgrade for token issuers.
• The architecture now separates verification from message delivery, allowing any party to submit a message once required signatures are collected.
• A default committee of 16 node operators handles verification, though issuers can add extra verifiers for security.
• Optional compliance tools allow issuers to enforce identity or policy rules before tokens cross chains.

How the new architecture works

In the previous version, Chainlink's oracle network handled both verifying transactions and delivering messages. Version 2.0 splits these tasks. Once a transaction is verified, any participant can execute the message on the destination chain. The default verification group consists of 16 independent node operators, but projects can require additional signatures from custom verifiers known as Cross-Chain Verifiers (CCVs).

Speed improvements are also optional. The system defaults to waiting for full finality on the source chain to ensure safety. Users who choose fewer confirmations accept the risk that the source blockchain could reorganize, potentially leading to duplicate executions or unbacked tokens. Legacy pools cannot access these faster settings.

Requirements for token issuers

Token issuers who want to use the new verifier, fee, or finality settings must upgrade to version 2 pools. Existing major pools, such as those for WBTC, Lido's wstETH, and Coinbase's cbBTC, remain on version 1.6.x and will continue working under the new defaults.

Migrating to the new standard involves deploying new pool contracts and updating token mappings. For "lock-and-mint" systems, locked tokens must be moved to a new custody contract. Chainlink provides guides for standard upgrades but notes that customized pools may face different challenges.

Risks and trade-offs

The documentation highlights that opting for faster transfers carries significant risks. If a user chooses to skip waiting for full finality, there is a chance the source chain could reorganize after funds have been released elsewhere. This scenario could result in lost funds or unbacked tokens. Additionally, while compliance checks are available, they are not mandatory for all transfers.

Next steps for integration

Issuers wishing to adopt the new features must follow specific migration guides provided by Chainlink. These guides detail how to deploy new pools, grant necessary permissions, and configure counterpart pools. Old pool addresses must remain active until all pending messages have settled to prevent disruption.

Sources

• The Defiant

Read also: Chainlink Unveils CCIP 2.0 with Custom Security Layers Following Major Bridge Hack

Read also: Months After $292M Kelp Hack, Chainlink Gives Institutions Custom Bridge Safety Checks