Kraken has switched its cross-chain infrastructure provider from LayerZero to Chainlink CCIP, the exchange confirmed on Friday. The move comes weeks after LayerZero suffered an exploit in April that rattled confidence in the protocol and prompted a wave of security reviews by crypto projects using its technology.
Why Kraken made the move
The April breach exposed a vulnerability in LayerZero's message-passing system, though the exact impact on Kraken's operations was never disclosed. For a major exchange handling billions in daily volume, the risk was too high to ignore. Kraken's engineering team had been evaluating alternatives since the incident, sources familiar with the decision told GFdaily. Chainlink's Cross-Chain Interoperability Protocol — CCIP — won out largely because of its track record in securing high-value DeFi transactions and its formal verification processes.
What CCIP brings
Chainlink CCIP uses multiple independent oracle networks to validate cross-chain messages, a design meant to prevent the single-point-of-failure issues that attackers exploited on LayerZero. The protocol also includes a built-in rate limit and emergency pause mechanism — features Kraken's risk team specifically asked for during the due diligence phase. The transition has been in the works for about two weeks, with Kraken's internal teams working through the weekend to migrate liquidity pools and smart contract integrations.
Timing matters
This isn't the first time an exchange has switched cross-chain providers after an incident, but it's happening faster than usual. Industry observers note that Kraken's move could put pressure on other exchanges and protocols still using LayerZero to either accelerate their own audits or face similar defections. LayerZero has since patched the exploited vulnerability and released a post-mortem, but the reputational damage lingers.
What happens next
Kraken users shouldn't see any changes to their normal cross-chain transfers — the switch is entirely backend. The exchange plans to publish a technical breakdown of the migration on its developer blog next week, including specific security benchmarks CCIP passed during testing. For now, the message from Kraken is clear: after April, trust in cross-chain bridges has to be earned, not assumed.
