BitGo announced on August 4 that it selected Chainlink’s Cross-Chain Interoperability Protocol (CCIP) as the exclusive bridge for its Wrapped Bitcoin ecosystem, replacing LayerZero across roughly $7.4 billion in tokenized bitcoin. The move makes WBTC, the largest tokenized version of bitcoin by market capitalization, the biggest single asset yet to adopt Chainlink’s standard. BitGo also committed to routing all future BitGo-issued digital assets through CCIP by default, turning what began as a single product decision into a company-wide infrastructure policy.
An Exploit Triggered the Industry Shift
The migration follows a $292 million exploit of Kelp DAO’s LayerZero-powered bridge on April 18, in which attackers drained roughly 116,500 rsETH. Investigators traced the breach to compromised internal RPC nodes that fed false data to a single-verifier configuration, known as a 1-of-1 DVN setup, tricking the system into approving a fraudulent cross-chain transaction. LayerZero has since revised its security model to eliminate similar single-verifier configurations, but the incident accelerated a broader exodus. Mantle, Lombard, Aave, and Kraken had already announced plans to leave LayerZero for Chainlink CCIP before BitGo’s announcement, alongside Solv Protocol’s SolvBTC and xSolvBTC.
With BitGo’s WBTC deployment added to the total, publicly announced LayerZero-to-Chainlink migrations now approach $15 billion industry-wide, based on figures reported by CoinDesk and The Block. That figure reflects announced rather than completed transfers, and BitGo has not published a timeline for finishing the switch.
Institutional Security Standards Drive the Decision
BitGo CEO Mike Belshe framed the decision around risk management rather than new features, saying the company’s long-standing security focus led it to review interoperability providers before settling on Chainlink. Chainlink’s CCIP requires a minimum of 16 independent, security-reviewed node operators per bridge lane, distributed across regions and hosting environments to reduce single points of failure. The protocol also includes built-in transaction rate limits that function as automatic circuit breakers, capping outflows before an incident can spread across connected chains. BitGo noted Chainlink CCIP holds both SOC 2 Type II and ISO 27001 certifications, standards commonly required by institutional counterparties assessing infrastructure risk.
Under the new arrangement, BitGo retains direct control over WBTC’s token contracts, transfer rate limits, and cross-chain settings, using Chainlink’s Cross-Chain Token standard to unify WBTC deployments across supported blockchains rather than maintaining separate implementations per chain. WBTC currently accounts for roughly 45% of the global wrapped bitcoin market, with each token backed one-for-one by bitcoin held in custody.
The migration adds another chapter to WBTC’s governance history. BitGo’s 2024 partnership with Justin Sun-linked BiT Global in a multi-jurisdiction custody arrangement drew industry scrutiny and contributed to Coinbase delisting WBTC in favor of its own cbBTC token. BitGo maintains it retains full ownership and operational control of WBTC’s token contracts despite that earlier restructuring.
Conclusion
BitGo’s shift reflects a wider recalibration across crypto infrastructure, where a single bridge exploit exposed how concentrated verification risk had become across billions of dollars in wrapped assets. With nearly $15 billion in announced migrations now pointed toward Chainlink, cross-chain security architecture is emerging as a defining factor in how institutional capital selects infrastructure providers, rather than a background technical detail. Whether Chainlink’s model prevents a comparable failure remains untested at this scale, but BitGo’s decision signals that redundancy and independent verification have become non-negotiable requirements for assets moving between blockchains.
Sources & Methodology
AAFX.IO reports market information using primary data, official announcements and clearly attributed reporting wherever available. Source links are included within the article when referenced.
