Chainlink launched CCIP 2.0 on Monday, letting institutions add their own bridge verifiers five months after Kelp DAO lost $292 million to North Korea-linked hackers.

The upgrade introduces the Cross-Chain Verifier (CCV), an opt-in module banks and crypto firms can configure themselves or commission from external providers including Infosys and Nethermind. Reference deployments are published on Amazon Web Services and Google Cloud, per Chainlink's launch announcement.

What does CCIP 2.0 actually change?

CCIP 2.0 retains Chainlink's default verification: a 16-node committee of independent operators that reaches consensus on every cross-chain transfer. The shift lies in a quieter structural adjustment. Chainlink's documentation now states that "the Risk Management Network's automated offchain role is no longer active in current CCIP deployments." The same passage says it "is expected to be offered as an optional validation layer in future releases."

The Risk Management Network's on-chain contract remains in place as an emergency backstop. For institutions that adopt no additional verifier, the practical result is reliance on a single verification path where they previously had two.

How does this connect to the Kelp hack?

Kelp's bridge ran on LayerZero with a single verifier, a configuration LayerZero later said it no longer supports for new deployments. Kelp claimed LayerZero's team had approved the setup; LayerZero disputed that account. In April, hackers tied to North Korea's Lazarus Group exploited that single point of failure and drained approximately $292 million from the protocol.

Kraken shifted its wrapped Bitcoin token to CCIP. Lombard Finance moved more than $1 billion in Bitcoin-linked assets to the same infrastructure after the exploit. The migration reframed CCIP as the bridge institutions chose after the alternative failed.

"Historically, legacy bridges have lost billions due to insecure infrastructure, while in-house builds are slow and expensive and institutions' proprietary networks can't earn the trust of their peers," Chainlink Labs Chief Business Officer Johann Eid said in the launch announcement.

What is the scale of Chainlink's footprint?

Chainlink says CCIP now secures more than $84 billion in cross-chain token value, a self-reported figure. The company disclosed that $15 billion in tokenized assets migrated onto its rails over the past four months, including portions of BitGo's wrapped Bitcoin and Coinbase's cbBTC. Those wrappers back exchange-traded funds and bank products that retail holders access without ever touching a crypto wallet.

Eighteen firms appear as launch partners on the announcement. Several quotes in the partner list stop short of confirmed integration. Fidelity said CCIP 2.0 "has the potential to support" broader distribution. Further Asset Management said it "intends to partner." Confirmed live deployments on the new verifier framework remain scarce hours into launch day.

What should institutions watch next?

The operational question is whether the new CCV layer sees broad adoption or functions as a compliance formality. Chainlink has framed the Risk Management Network's deactivation as a transitional step toward the optional validation layer described in its documentation, though no release date has been published. The CCIP 2.0 launch leaves default users on a 16-operator consensus without the independent second check that previously ran in parallel, while institutions configuring custom CCVs gain flexibility at the cost of new integration work and a wider audit surface.