Overview
- Chainlink announced CCIP 2.0 on Sept. 28, rolling out new Cross‑Chain Verifiers that issuers or third parties can operate on top of Chainlink’s existing verifier committee.
- The release preserves Chainlink’s default Committee Verifier of 16 independent node operators while adding issuer-run verifiers, an Automated Compliance Engine for KYC/AML/sanctions checks, and configurable finality including faster-than-finality options.
- Chainlink’s documentation says the Risk Management Network’s automated off‑chain role is not active in current deployments, which means optional CCVs now replace that second check unless an issuer adds one.
- Technical analysis and Chainlink’s own notes warn issuer-required verifiers can delay or stall deliveries if an attestation is not produced and that recovery depends on issuer-specific route settings rather than an automatic refund.
- Chainlink cites roughly $84 billion secured on CCIP with about $15 billion migrated recently, several banks and providers preparing pilots including Swift integrations, and the launch follows April’s $292 million Kelp DAO bridge hack that drove migration demand.