Kraken Switches to Chainlink CCIP Amid LayerZero Scrutiny

Kraken announced it is deprecating LayerZero and adopting Chainlink’s Cross‑Chain Interoperability Protocol (CCIP) as its exclusive cross‑chain infrastructure for Kraken Wrapped Bitcoin (kBTC) and future wrapped tokens [2]. The move follows a broader exodus from LayerZero after a high‑profile exploit that raised security concerns across the ecosystem.

Key takeaways

• Kraken will use Chainlink CCIP to secure kBTC and all future wrapped tokens [2].
• The switch is motivated by CCIP’s “enterprise‑grade infrastructure” with strict security and risk management features [2].
• Other protocols, including Kelp DAO, Solv Protocol, and Re, have also migrated to CCIP after the April Kelp DAO exploit [2].
• More than $3 billion in total value locked has shifted to CCIP since the hack, while LayerZero’s native token ZRO has fallen over 30% [2].
• Chainlink’s CCIP advertises built‑in compliance, privacy, and a modular security framework powered by decentralized oracle networks [1].

Kraken’s Migration to Chainlink CCIP

Kraken’s announcement on Thursday detailed that the exchange is retiring its existing cross‑chain provider and will rely solely on Chainlink CCIP for its wrapped Bitcoin product and any subsequent wrapped assets [2]. The exchange cited CCIP’s “enterprise‑grade infrastructure with strict security and risk management requirements,” highlighting certifications, a secure‑by‑default design, 16 independent nodes, and native rate limits as key factors [2]. This migration aligns Kraken with other high‑profile projects that have recently shifted to CCIP, seeking to avoid the vulnerabilities exposed by the Kelp DAO exploit on LayerZero.

Industry Shift After the Kelp DAO Exploit

The Kelp DAO incident in April, which resulted in the theft of roughly $292 million in liquid restaking tokens, prompted a wave of protocol migrations away from LayerZero [2]. In addition to Kraken, Kelp DAO itself is moving to CCIP and has burned the hacker’s 117,132 rsETH as part of its recovery [2]. Solv Protocol announced a migration of $700 million in tokenized Bitcoin, and the reinsurance protocol Re shifted $475 million in total value locked to CCIP [2]. Collectively, more than $3 billion in TVL has been transferred to Chainlink’s protocol since the hack, while LayerZero’s native token ZRO has declined over 30% in the same period [2].

Why it matters

The migration underscores a growing preference for Chainlink’s CCIP, which markets itself as a secure, privacy‑preserving interoperability layer capable of connecting assets across 60+ public and private blockchains [1]. By leveraging Chainlink’s decentralized oracle networks, CCIP aims to eliminate the need for custom bridges and reduce reliance on single points of failure, a claim that resonates with protocols seeking to mitigate cross‑chain risk after recent exploits [1]. As more high‑profile projects adopt CCIP, the competitive landscape for cross‑chain solutions may shift further toward providers that can demonstrate robust security and compliance frameworks. Future developments will likely hinge on how effectively CCIP can deliver on its promises of unified asset oversight and risk mitigation while maintaining performance across diverse blockchain ecosystems.