Chainlink CCIP 2.0 Launches Custom Verifiers as Risk Management Network Goes Inactive

Chainlink deactivated the automated offchain monitoring layer of its Risk Management Network in its latest cross-chain infrastructure upgrade, shifting the burden of secondary transaction verification directly to institutional users.

The change arrived Monday with the rollout of CCIP 2.0, introducing a feature called the Cross-Chain Verifier (CCV). Banks, asset managers, and crypto firms can now deploy proprietary validation nodes or contract third-party developers such as Infosys and Nethermind to independently confirm token transfers between blockchains. Deployment templates are hosted on Amazon Web Services and Google Cloud.

For institutions that do not configure an external verifier, the default security architecture now relies exclusively on Chainlink’s primary committee of 16 independent node operators. The Risk Management Network, which previously functioned as an automated secondary audit mechanism scanning for anomalies across chains, remains only as an on-chain smart contract emergency backstop. Chainlink’s documentation states the network’s automated role “is no longer active in current CCIP deployments,” though it may return as an optional layer in future releases.

This architectural shift alters the security baseline for more than $84 billion in cross-chain token value that Chainlink reports currently moves over its rails. Over the past four months alone, $15 billion in tokenized assets migrated to the network, including BitGo’s wrapped Bitcoin and Coinbase’s cbBTC. These assets increasingly serve as underlying collateral for exchange-traded funds and traditional banking products held by retail investors who never interact directly with blockchain wallets.

cross-chain bridges remain one of the most targeted attack vectors in digital finance. Because blockchains operate in isolated environments, moving capital from Ethereum to Solana or Bitcoin requires intermediary software to verify that funds were locked on the source chain before minting them on the destination chain. Compromising that verification step has historically allowed attackers to drain entire protocols.

The urgency around bridge security intensified five months ago when hackers linked to North Korea’s Lazarus Group exploited Kelp DAO, draining approximately $292 million. Kelp used LayerZero’s interoperability protocol configured with a single verifier. LayerZero later stated it stopped supporting that specific configuration for new deployments, calling it a mistake, while Kelp maintained that LayerZero engineers approved the setup without raising risk warnings.

The breach triggered immediate migration among major financial players. Kraken shifted its wrapped Bitcoin operations to Chainlink. Lombard Finance moved over $1 billion in Bitcoin-linked assets to the platform. Kelp DAO itself transitioned away from LayerZero.

CCIP 2.0 effectively offers institutions the same configurability that contributed to the Kelp exploit, but maintains the 16-node consensus requirement as a mandatory floor rather than an optional setting. Chainlink Labs Chief Business Officer Johann Eid framed the release as a solution to the limitations of both legacy bridges and costly proprietary networks built internally by banks.

Eighteen firms are listed as launch partners for the CCV system. However, early partner statements indicate preliminary engagement rather than live integration. Fidelity noted the upgrade “has the potential to support” broader distribution, while Further Asset Management stated it “intends to partner.” Confirmed production deployments utilizing the new custom verifiers had not been publicly documented as of Monday’s launch.