Chainlink released version 2.0 of its Cross-Chain Interoperability Protocol on Monday, a rebuild of the bridging system it says now secures more than $84 billion in token value moving between blockchains.
The headline feature is Cross-Chain Verifiers. Banks and crypto platforms can now require an extra verification step before a transfer executes, run on their own cloud accounts or hired from providers such as Infosys and Nethermind. That step can carry know-your-customer, anti-money-laundering and sanctions checks on top of Chainlink’s default network of 16 node operators, and starter kits are available for Amazon Web Services and Google Cloud.
The timing is not subtle. In April, attackers took $292 million from Kelp DAO through a LayerZero bridge configuration that relied on a single verifier, and Kelp has since moved its rsETH token to Chainlink. Johann Eid, Chainlink Labs’ chief business officer, told CoinDesk that legacy bridges have lost billions to insecure infrastructure.
Existing integrations keep working without changes, and Aave and Maple have begun adopting some of the upgrade’s features.
The less advertised change is in the architecture. Chainlink’s Risk Management Network, which used to run as a separate and independent safeguard, no longer plays that role, CoinDesk reported. A protocol that does not add its own verifier now depends on the 16-operator network alone, rather than on two distinct systems.
The custom verifiers that are meant to justify that trade have no publicly named institutional users yet. Until one arrives, CCIP 2.0 has swapped a default second check for an optional one.
