$7.4 billion of WBTC market value is moving to Chainlink CCIP as of 4 August 2026, according to the announced BitGo migration. The practical answer to “why is WBTC moving from LayerZero to Chainlink?” is security architecture: this is a response to a bridge-verification failure, not a reason to abandon every cross-chain transfer.
What happened to the KelpDAO bridge?
$292 million, representing 116,500 rsETH, was lost on 18 April 2026 when the KelpDAO route accepted a forged cross-chain message. The crucial denominator was one required verifier out of one configured verifier: compromising that verification path was enough to release assets. LayerZero’s incident report describes an off-chain infrastructure compromise and the forced reliance on compromised nodes.
That is a configuration and operational-security failure, not evidence that “bridges are broken.” The signal worth acting on is whether a route has independent verification, credible monitoring, and a recovery model—not whether its marketing calls it decentralized.
Why did BitGo move WBTC to Chainlink?
About $15 billion in assets was reported as moving away from LayerZero toward CCIP, with WBTC accounting for $7.4 billion of that total. BitGo’s choice makes the change real: its issued assets are adopting one cross-chain standard rather than leaving users to assess each application route themselves. For WBTC holders, that means the official issuer path matters more than finding the cheapest generic bridge quote.
Should I move WBTC after the LayerZero migration?
- 1. Check the asset and destination. Confirm that you hold actual WBTC, identify the chain you need, and verify the receiving address on that chain.
- 2. Use the issuer’s official process for an issuer migration.BitGo is the relevant service for WBTC lifecycle information; Chainlink is relevant to the CCIP standard behind the announced migration.
- 3. Most often done wrong: do not substitute a generic bridge for an official asset migration. A bridge transfer may move a token, but it does not necessarily place you on the canonical, issuer-recognized version.
Which cross-chain service should I use instead?
| Need | Service worth reaching for |
|---|---|
| Move or swap ordinary EVM assets and arrive ready to use them | Across is useful for intent-based routes: state the asset and destination outcome rather than manually choosing bridge steps. |
| Move native USDC where the route supports it | Circle is the relevant issuer ecosystem for CCTP-based USDC movement. |
| Migrate or verify canonical WBTC | Use the issuer’s published route, not a convenience route. |
The takeaway is narrow: the WBTC move reflects a durable preference for stronger, independently verifiable cross-chain design. Treat a migration as an asset-canonicality task; treat an everyday bridge as a routing task; and never let a low fee decide either one alone.