Chainlink Released CCIP 2.0 Update

The upgraded platform introduces optional verifiers to enhance cross-chain token transfer security protocols.

Updated on Sept. 29, 2026 in Artificial Intelligence

Isometric editorial illustration of three interlocking monolithic geometric blocks in a stable, balanced configuration representing a secure technical system.
Chainlink has launched CCIP 2.0, an updated platform allowing token issuers to implement optional verifier approvals for enhanced security in cross-chain transactions. AI Illustration. Upload story photo >

Live Poll

Do you trust decentralized finance protocols that allow third parties to delay your asset transfers?

Chainlink launched CCIP 2.0, allowing issuers to require additional verifier approval for cross-chain token delivery. This update gives developers greater control over the transfer process across supported blockchain networks.

Why it matters

The introduction of optional Cross-Chain Verifiers allows token issuers to implement specific approval conditions, adding a layer of security and customization for cross-chain transactions that was not previously available.

The CCIP 2.0 architecture utilizes 16 independent node operators for its default Committee Verifier. The system allows for an eight-hour window where the default executor will automatically retry failed destination delivery attempts.

The players

Chainlink

Chainlink is a decentralized oracle network that provides real-world data to smart contracts on various blockchain platforms.

The details

The update works by having an OnRamp record messages for offchain services, which then publish attestations that the OffRamp checks before releasing tokens. On EVM chains, users can configure hooks to reject transfers either before or after tokens are locked or burned in the source pool.

Timeline

  1. Chainlink announced the CCIP 2.0 feature update on September 28, 2026.

The Tech Race

The launch of CCIP 2.0 represents a shift toward more modular security architectures in blockchain interoperability. This update positions the protocol to better compete against other cross-chain communication standards by prioritizing developer-defined verification logic.

Users and developers should note that required verifiers may introduce delays in token delivery times compared to previous versions. Additionally, developers must account for the lack of an automatic refund process when designing transaction flows on EVM-compatible chains.

The takeaway

Developers should prioritize testing new hook configurations to ensure tokens do not remain locked if verification fails. Implementing these verifiers adds security but requires careful management of the full cross-chain lifecycle.

Further reading

Learn more about the latest innovations in Artificial Intelligence.

Source note: This article includes information reported by CryptoSlate.

Live Poll

Do you trust decentralized finance protocols that allow third parties to delay your asset transfers?