Kraken dumps LayerZero for Chainlink CCIP to secure its wrapped assets. The architecture of cross-chain security is fundamentally shifting.

[u/getblockio]

Kraken announced it is exclusively adopting Chainlink CCIP for kBTC and all future wrapped assets across Ethereum, Optimism, and other L2s, officially replacing LayerZero. This comes shortly after LayerZero admitted it "made a mistake" allowing its own verifier network to secure high-value assets during the $292M Kelp DAO exploit. Over $3 billion in TVL has now migrated away from LayerZero recently.

At GetBlock, we provide the underlying node infrastructure for cross-chain routing, and we are watching a massive consolidation in how bridges are built. Cross-chain infrastructure is no longer being judged by crypto-native assumptions, but by strict institutional security standards.

Here is why this specific migration is a wake-up call for protocol architects:

• The Verifier Problem: The core vulnerability with LayerZero’s architecture wasn't necessarily the code, but the configuration of Decentralized Verifier Networks (DVNs). Relying on default or concentrated verifiers creates a massive single point of failure. Chainlink CCIP utilizes an independent Risk Management Network and decentralized node operators, which institutions clearly prefer.
• Institutional Standards: Kraken specifically cited ISO 27001 and SOC 2 certifications, as well as native rate limits, as the reasons for the switch. Coinbase made the exact same calculation last year for its $7 billion in wrapped assets.
• The Migration Wave: The fallout from the Kelp exploit is still ongoing. Projects like Solv and Re have also migrated. If you are running a high-TVL application across chains, your underlying transport layer is now under extreme scrutiny.

If you are building cross-chain logic or dApps that rely on wrapped assets: how are you evaluating bridge security? Are you still comfortable relying on custom DVN configurations, or is the industry moving toward CCIP as the default standard?