Bitgo has selected Chainlink as the exclusive cross-chain infrastructure provider for wrapped bitcoin (WBTC), replacing LayerZero in a move that will redefine how the $7.7 billion token operates across blockchain networks. The company said on Tuesday that all future Bitgo-issued digital assets will also integrate Chainlink’s Cross-Chain Interoperability Protocol (CCIP).
Bitgo Standardizes on Chainlink CCIP
The decision makes Chainlink CCIP the sole cross-chain messaging and token transfer layer for WBTC, one of the largest tokenized bitcoin assets. By standardizing on CCIP, Bitgo aims to streamline cross-chain functionality for WBTC and future assets it issues, consolidating interoperability under a single infrastructure provider.
Why It Matters for WBTC
- Scale: WBTC is a widely used tokenized representation of bitcoin on Ethereum and other networks, with a market value of roughly $7.7 billion.
- Interoperability: Cross-chain infrastructure determines how tokens like WBTC move between blockchains and layer-2 networks, affecting settlement reliability, developer integrations, and user experience.
- Standardization: Migrating to a single provider can reduce fragmentation and align security and governance across supported chains.
About the Players
- Bitgo: A digital asset custody and infrastructure firm that serves institutions and acts as the issuer and custodian for WBTC.
- WBTC: A tokenized version of bitcoin designed to bring BTC liquidity to smart contract ecosystems such as Ethereum, enabling trading, lending, and other on-chain applications.
- Chainlink CCIP: Chainlink’s cross-chain protocol for secure messaging and token transfers across heterogeneous blockchains.
- LayerZero: A cross-chain messaging protocol previously used in WBTC’s interoperability stack.
What Changes for Developers and Users
Bitgo’s shift means future WBTC cross-chain operations and upcoming Bitgo-issued tokens will rely on CCIP for messaging and transfers. Developers integrating WBTC liquidity across chains may need to align with CCIP-supported paths and tooling, while users could see a more uniform bridging experience as ecosystems consolidate around the new standard.