Overview
- Kraken, which disclosed the change Thursday, will use Chainlink’s CCIP as the exclusive cross‑chain system for kBTC today and all future Kraken Wrapped Assets.
- The backend migration spans Ink, Ethereum, Optimism, and Unichain, kBTC holders do not need to take any action, and Kraken continues to custody the Bitcoin that backs the token 1:1.
- Kraken points to CCIP controls such as ISO 27001 and SOC 2 Type 2 compliance, 16 independent node operators validating messages, and native rate limits to curb large unauthorized transfers.
- The move follows the April 18 exploit that drained 116,500 rsETH from Kelp DAO after attackers poisoned LayerZero’s internal RPCs in a single‑verifier setup attributed to the Lazarus Group.
- Protocols including Kelp, Solv, Re, and Lombard say more than $3 billion to over $4 billion in assets are shifting to CCIP, while LayerZero ends support for 1‑of‑1 verifier configurations and rolls out stricter defaults.