Chainlink Lets Banks Bring Their Own Bouncer to the Bridge Party 🏦

Months after North Korea's Lazarus Group drained roughly $292 million from Kelp DAO, Chainlink has rolled out a feature that lets institutions bolt their own security guard onto cross-chain transfers. CCIP 2.0, the latest version of Chainlink's cross-chain infrastructure used to move tokenized assets between blockchains, introduced the Cross-Chain Verifier, or CCV, which lets banks and crypto projects run a second verifier alongside Chainlink's default committee of 16 independent node operators that reach consensus on every transaction. Starter kits for running a CCV are available on Amazon Web Services and Google Cloud, with firms including Infosys and Nethermind positioned as providers. Chainlink still routes every transfer through the 16-node committee, but the Risk Management Network, a separate set of nodes that previously double-checked the committee's work, has been sidelined. "The Risk Management Network's automated offchain role is no longer active in current CCIP deployments, but is expected to be offered as an optional validation layer in future releases," Chainlink's documentation states, with the on-chain contract retained only as an emergency backstop. Institutions that add nothing extra now rely on one verification network rather than two, with optional CCVs positioned as a replacement for that second layer of independent checking.

The release lands against a backdrop of mounting losses tied to single-point-of-failure bridge designs. Bridges, the software that confirms a token really left one blockchain before appearing on another, have been among the most targeted pieces of crypto infrastructure, with attackers repeatedly exploiting lone verifiers to forge transfers. In April, Kelp DAO, a protocol that let users stake Ethereum and route the token across chains, lost about $292 million when hackers tied to North Korea's Lazarus Group compromised a bridge running on LayerZero configured with a single verifier. LayerZero later said the configuration was a mistake and stopped supporting it for new deployments. Kelp said LayerZero's team approved the setup and never flagged it as risky, while LayerZero disputed that account and said the configuration went against its own recommendations. Kelp subsequently moved to Chainlink, as did Kraken, which shifted its wrapped assets onto the network.

The use of that network has grown sharply. Chainlink said $15 billion in tokenized assets migrated onto its rails in the last four months, including portions of BitGo's wrapped Bitcoin and Coinbase's cbBTC, products increasingly held through ETFs and bank offerings by users who never interact with a crypto wallet directly. Tokenized money, including stablecoins, wrapped Bitcoin such as $BTC equivalents like WBTC and cbBTC, and tokenized funds, now moves across chains through the CCIP pipeline, with Ethereum and Solana among the ecosystems served. CCIP 2.0's CCV feature is positioned as a way for institutions to add a custom check without building a bridge from scratch or relying solely on a single network of verifiers. Chainlink's documentation frames optional CCVs as the new source of independent verification, replacing the now-dormant Risk Management Network for institutions that opt in to the additional layer.