BitGo selects Chainlink for WBTC cross-chain infrastructure.
Crypto custodian BitGo has announced its selection of Chainlink as the exclusive cross-chain infrastructure provider for wrapped Bitcoin (WBTC), replacing LayerZero.
Security comes first. Always has.
BitGo is migrating away from our legacy solution and selecting @chainlink CCIP as our exclusive cross-chain infrastructure provider, standardizing WBTC and all future BitGo-issued assets on a single, institutional-grade interoperability… pic.twitter.com/7x90nQQlDm
— BitGo (@BitGo) August 4, 2026
All future company assets will also be supported by CCIP by default.
Under the Chainlink Cross-Chain Token standard, each blockchain will have a single BitGo version of WBTC, eliminating derivative copies previously created by bridges. Token contracts, transfer limits, and cross-network parameters will remain under the company’s control.
“BitGo has long been built around a simple principle: security first,” said the company’s CEO, Mike Belshe.
The company cited the protocol’s security architecture, compliance with institutional client standards, and built-in control mechanisms as reasons for the transition. Each transfer route is serviced by at least 16 independent node operators distributed across different organizations, regions, and hosting providers. Additionally, the protocol allows the issuer to set transfer speed limits.
The timeline for completing the transition across all supported networks has not been disclosed by BitGo or Chainlink. Chainlink’s catalog already lists WBTC pools with CCIP support for Ethereum and Ronin.
LayerZero Outflows Near $15 Billion
Including WBTC, the total value of assets whose issuers have announced a switch from LayerZero to Chainlink has reached nearly $15 billion. Prior to this announcement, the figure was around $7.2 billion.
Similar decisions were previously made by Kraken for the kBTC token, the Bitcoin platform Solv Protocol, as well as Mantle, Lombard, Aave, and Kelp.
The impetus was the hack of the rsETH bridge on the LayerZero-based Kelp protocol. The platform used a single verifier (1/1 DVN), which was LayerZero Labs itself. Hackers compromised external RPC servers, submitted false data, and withdrew $292 million.
In response, LayerZero restructured its security and abandoned the single verifier scheme.
This did not apply to the WBTC bridge: BitGo integrated LayerZero in 2024 for operations with Avalanche and BNB Chain, but each transaction required dual verification—BitGo’s own validator and one of two external ones (LayerZero or Polyhedra).
In May, the project team acknowledged that using a single verifier configuration for securing large transactions was a mistake.
Found a mistake in the text? Select it and press CTRL+ENTER