Months After the $292M Kelp Hack, Chainlink Lets Institutions Add Their Own Bridge Checks

What happened

Chainlink released CCIP 2.0, which lets banks add their own security checks to cross-chain transfers. This comes five months after a rival setup lost $292 million to hackers.

Confirmed

Global impact / market context

Banks using cross-chain transfers, which move assets between blockchains, can now apply their own safety checks instead of relying only on Chainlink's. That could make institutions more willing to move money across chains after a $292 million hack shook confidence.

Analyst inference

The $292 million hack showed cross-chain bridges are risky. Chainlink's move lets institutions control security, which may help its LINK token if more banks adopt CCIP 2.0, though rival bridge providers could lose business.

Analyst inference

What to watch

1. Watch whether banks adopt Chainlink's CCIP 2.0 for cross-chain transfers, since the article says it lets them add their own security checks five months after a rival's $292 million hack. Confirmed
2. Chainlink could attract more institutional users by offering customizable bridge security, but only if banks trust that their own checks reduce hack risk enough to justify using the new system. Proposed
3. If banks adopt CCIP 2.0, demand for LINK may rise, but rivals could improve security too, so Chainlink's advantage depends on whether it keeps winning institutional trust. Analyst inference

Affected assets

• LINK — Chainlink

Evidence

• decrypt.co