CBDC interoperability challenges

CBDC interoperability challenges—particularly in hybrid setups like the Société Générale–Forge/Banque de France (BdF) 2024 repo pilot and ongoing Les Gardiennes/UBS collaborations—stem from bridging public Ethereum (permissionless, for tokenized collateral like bonds or uMINT funds) with proprietary/permissioned CBDC ledgers (e.g., BdF’s DL3S on Hyperledger Fabric). These pilots use mechanisms like Hashed Timelock Contracts (HTLCs), APIs, and platform-level orchestration (e.g., SG-Forge as registrar) for atomic or near-atomic settlement of repo transactions in wCBDC tokens. While proving feasibility, they highlight systemic barriers to scaling tokenized repo markets (tied to the ~$16T government bond-backed repo space per FSB 2026 data).

Reports from BIS, FSB/CPMI, OECD, IOSCO, and Cambridge CCAF (2025–2026) consistently rank interoperability as the top barrier to tokenized money adoption, often scoring 8.9–10/10 in priority. Key challenges fall into technical, regulatory/legal, operational/governance, and economic categories.

1. Technical Challenges

• Ledger Heterogeneity and Cross-Platform Connectivity: Public Ethereum (EVM, smart-contract native) vs. permissioned systems like DL3S (Hyperledger Fabric) or other DLTs creates mismatches in consensus (PoS vs. permissioned), finality (probabilistic vs. immediate), and data formats. Pilots rely on HTLCs, REST APIs, or bridges for interoperability, but these introduce latency, complexity, and single points of failure (e.g., oracle or bridge risks). Scaling to multi-chain or cross-border (e.g., Les Gardiennes with MAS) risks “walled gardens” or bespoke integrations.
• Settlement Finality and Atomicity: On-chain repo requires synchronized DvP (delivery-vs-payment) across ledgers. Mismatched finality can lead to one-sided exposures or failed atomic swaps. Ethereum’s 24/7 nature clashes with CBDC business-hour constraints or legacy RTGS links (e.g., Eurosystem’s Trigger/TIPS Hash-Link solutions).
• Scalability and Integration with Legacy Systems: High-volume repo demands low-latency, high-throughput. Ethereum congestion (even post-Merge) and gas fees persist; permissioned CBDCs face node/custody limits. Integrating with core banking, T2/TARGET, or SWIFT remains complex and costly.

2. Regulatory and Legal Challenges

• Fragmentation and Harmonization: Differing national frameworks for legal finality of on-chain transfers, insolvency treatment of tokens, KYC/AML/CFT, sanctions screening, and transfer restrictions (e.g., whitelisting in SG-Forge CAST). Cross-border repo (e.g., UBS/SBI/DBS or Les Gardiennes) requires aligned compliance across jurisdictions; pilots often use off-chain legal wrappers.
• Privacy vs. Transparency: Public Ethereum exposes transaction data; CBDCs demand privacy/confidentiality for institutions. Selective disclosure or zero-knowledge proofs add complexity without proven scalability in regulated pilots.
• Access and Governance Models: Who can access wCBDC (foreign PSPs, non-residents)? BIS notes risks in decision-making, liability allocation, and risk-sharing for multi-actor setups.

3. Operational and Governance Challenges

• Data Privacy, Security, and Custody: Cyber risks (node attacks, smart contract bugs), key management, and custody models (self-custody vs. regulated). DL3S pilots emphasize role-based controls, but bridges/oracles create new vulnerabilities.
• Multi-Actor Coordination: Pilots involve central banks (BdF), banks (SG, UBS), and platforms. Governance for upgrades, disputes, or failures is non-trivial; Eurosystem projects (Pontes by end-2026 for DLT-TARGET links; Appia for full DLT ecosystem) aim to standardize this.
• Standards Gaps: No universal protocols for messaging, identity (verifiable credentials), or compliance automation across CBDC/tokenized deposits/stablecoins.

4. Economic and Systemic Challenges

• Liquidity Fragmentation and Singleness of Money: Multiple incompatible networks/tokens risk trapping value, eroding fungibility, and creating “million flavours” of money. Cross-asset connectivity (CBDC + tokenized deposits + stablecoins like EURCV) is critical but underdeveloped.
• Adoption and Cost Barriers: High transition costs, first-mover disadvantages, and legacy inertia limit scale beyond pilots. Even 1% repo migration (~$125–160B) requires seamless interoperability to avoid fragmentation.

Ongoing Mitigation Efforts (relevant to pilots):

• Eurosystem: Pontes (short-term wCBDC pilot linking DLT platforms to TARGET by end-2026) and Appia (longer-term unified DLT ecosystem). DL3S already connected 40+ entities across 9 jurisdictions in 2024 trials.
• BIS/International: Project Agora (tokenized commercial bank money + wCBDC on programmable platforms); mBridge (multi-CBDC for cross-border); unified ledger concepts to minimize bridges.
• Industry: Standards like ISO 20022 harmonization, Fireblocks-style smart contract uniformity, and public-private forums (e.g., FSB cross-border payments implementation phase).

These challenges explain why current repo pilots remain exploratory despite technical success: they demonstrate feasibility (e.g., Ethereum collateral + DL3S CBDC settlement) but require coordinated public-private standards, regulatory alignment, and infrastructure investment for production-scale adoption. Progress is accelerating in 2026 via Eurosystem and BIS work, but full interoperability remains a multi-year horizon. For deeper dives, see the CCAF Tokenised Money report or BIS/CPMI analyses.