Chainlink CCIP Powers Kelp DAO rsETH Migration After $292M Bridge Exploit

Kelp DAO is migrating its restaking token, rsETH, to Chainlink's Cross-Chain Interoperability Protocol (CCIP) after hackers drained 116,500 rsETH from its bridge on April 18, resulting in losses of approximately $292 million. 

What Happened In The Kelp DAO Exploit?

The attack has been one of the largest DeFi security incidents reported this year. Hackers exploited Kelp DAO's bridge, stealing 116,500 rsETH tokens before using them as collateral on Aave v3 to borrow wrapped Ether.

The stolen assets did not stay isolated. Because the rsETH entered Aave as collateral, the exploit triggered stress across lending markets before parts of the related funds were frozen. That kind of cross-protocol contagion is a known risk in DeFi, where assets move freely between interconnected protocols.

Why Did Kelp DAO Choose Chainlink CCIP?

Chainlink CCIP is a cross-chain infrastructure standard that routes transactions through a minimum of 16 independent, security-reviewed node operators via Chainlink's Decentralized Oracle Networks (DONs). This distributed verification model is central to why Kelp DAO selected it over other available options.

The migration moves rsETH away from LayerZero's OFT (Omnichain Fungible Token) standard and onto Chainlink's Cross-Chain Token standard. Kelp said the priority remains securing user funds and rebuilding trust following the exploit.

Kelp DAO is not alone in this shift. Just days earlier, Huma Finance selected Chainlink CCIP as the exclusive bridging infrastructure for its PST yield product and all future yield products, after an internal security review triggered by recent cross-chain hacks across the sector. That integration covers more than 100,000 Huma users.

Key security features that both protocols cited in their decisions include:

• Rate limits that cap how much value can move across a bridge lane within a set time window
• Issuer attestations that verify asset authenticity before cross-chain transfers are finalized
• Policy-based controls that allow protocols to define rules around how assets move between chains
• A minimum of 16 independent node operators securing every CCIP bridge lane

Is Chainlink Gaining Ground After Recent DeFi Bridge Attacks?

The back-to-back migrations from Kelp DAO and Huma Finance reflect a broader pattern. Cross-chain bridges are consistently among the most exploited components in decentralized finance. A compromised bridge does not just affect one protocol. It creates systemic risk across every asset and user connected to it.

Chainlink also expanded its institutional reach in late April, when Amazon Web Services added three Chainlink oracle services to the AWS Marketplace: Data Feeds, Data Streams, and Proof of Reserve. Enterprise developers can now access these tools directly through existing AWS procurement workflows.

Conclusion

Kelp DAO's migration to Chainlink CCIP is a direct response to a $292 million exploit that exposed the risks of insufficiently secured cross-chain bridges. The protocol is replacing LayerZero's OFT standard with Chainlink's Cross-Chain Token standard, backed by 16 independent node operators per bridge lane. With Huma Finance making the same switch days earlier, Chainlink is consolidating its position as the preferred cross-chain infrastructure for protocols prioritizing security over convenience.

Resources

1. KelpDAO on X: Post on April 5

2. Blog article by Huma Finance: Huma Finance Selects Chainlink CCIP, the Most Secure Cross-Chain Solution, To Power Cross-Chain Yield For 100K+ Users

3. Press release by AWS: Chainlink Data Standard now available on AWS Marketplace

4. Chainlink on X: Post on April 24