# BitGo selects Chainlink CCIP for a planned WBTC cross-chain migration

> CCIP became BitGo's selected interoperability standard for the planned WBTC migration, materially expanding the prospective use of this watched dependency and introducing a unified CCT model with issuer-managed risk parameters.

- URL: https://riadefi.com/on-chain/2026-08-04-ccip-wbtc-migration-selection/
- Type: Upgrade or migration
- Stage: Proposed
- Evidence: confirmed
- Materiality: material
- Event date: 2026-08-04
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Follow-up: 2026-08-31
- Advisor-relevant: no
- Affects: Chainlink CCIP (other)

## What happened

BitGo selected Chainlink CCIP as the exclusive cross-chain infrastructure provider for WBTC and stated that it plans to migrate WBTC away from its legacy solution. BitGo also plans to default future issued assets to CCIP.

## What changed

CCIP became BitGo's selected interoperability standard for the planned WBTC migration, materially expanding the prospective use of this watched dependency and introducing a unified CCT model with issuer-managed risk parameters.

## What did not change

The announcement did not confirm that WBTC routes had migrated, that CCIP-backed WBTC transfers were live, or that the legacy solution had been retired. BitGo retains ownership and issuer control over token deployments, and this event does not approve WBTC as a Ketju asset.

## Confirmed

- BitGo selected Chainlink CCIP as its exclusive cross-chain infrastructure provider.
- The announced scope includes WBTC and future BitGo-issued assets.
- BitGo stated that it plans to migrate WBTC away from its legacy cross-chain solution.
- The planned design uses Chainlink's Cross-Chain Token standard with issuer-managed risk parameters and security controls.
- BitGo stated that it retains ownership of token deployments and can add security controls.

## Still open

- No deployed WBTC CCIP lane, contract registry, supported-chain list, or first successful transfer was established.
- The migration schedule and retirement date for the legacy solution were not stated.
- The live CCIP Risk Management Network configuration and issuer-controlled rate limits for each WBTC route remain unresolved.
- The source's WBTC value figure was issuer-supplied and was not independently reconciled.

## What it means for an advisor

- Review the ccip dependency memo for the substantially larger prospective WBTC integration and its issuer-controlled configuration.
- Do not treat the WBTC migration as executed until deployed addresses, supported routes, configuration, and live transfer evidence are available.
- A CCIP dependency approval does not approve WBTC or remove the need to review BitGo custody, redemption, token-control, and per-chain route risks.

## Sources

1. [BitGo Selects Chainlink CCIP as Exclusive Cross-Chain Infrastructure Provider for WBTC, Migrating Away From Legacy Solution](https://www.bitgo.com/resources/blog/bitgo-selects-chainlink-ccip-for-wbtc/) · BitGo · 2026-08-04


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.