Kraken migrates to Chainlink CCIP for kBTC
The post Kraken migrates to Chainlink CCIP for kBTC appeared on BitcoinEthereumNews.com. Kraken is deprecating its cross-chain provider and migrating to Chainlink CCIP as the exclusive infrastructure for its wrapped assets. Summary Kraken chose Chainlink CCIP for its ISO 27001 and SOC 2 compliance, 16 independent nodes, native rate limits, and enterprise-grade security standards. The migration covers Kraken Wrapped Bitcoin (kBTC) and all future Kraken wrapped assets deployed across DeFi protocols. The move follows similar migrations by Kelp, Solv, and Re after the $292 million KelpDAO exploit in April that hit a LayerZero-powered bridge. Kraken posted the announcement on X on May 14, confirming that Chainlink’s Cross-Chain Interoperability Protocol will become its exclusive bridge infrastructure going forward. The exchange did not specify a migration timeline but said the switch covers kBTC, its 1:1 Bitcoin-backed wrapped token, and all future Kraken wrapped assets that it plans to bri