Cross-Border CBDC and Interoperability

CROSS-BORDER PAYMENT PROBLEMS

THE CORRESPONDENT BANKING MODEL:
┌────────────────────────────────────────────────┐
│ Alice (USA) sends $1,000 to Bob (Kenya) │
│ │
│ Alice's bank (USA) │
│ ↓ │
│ Correspondent bank A (USA) │
│ ↓ │
│ Correspondent bank B (UK) │
│ ↓ │
│ Bob's bank (Kenya) │
│ ↓ │
│ Bob receives ~$940 (after fees) │
│ │
│ Time: 3-5 days │
│ Cost: ~6% (remittances) │
│ Transparency: Limited │
└────────────────────────────────────────────────┘

PAIN POINTS:

• Multiple intermediaries

• Batch processing

• Time zone delays

• 3-5 business days typical

• Each intermediary takes fees

• FX spreads

• Compliance costs

• Average 6.3% for remittances

• Fees not always clear upfront

• FX rates opaque

• Status tracking difficult

• Requires bank accounts

• Excludes unbanked

• Developing country limitations

FUNDAMENTAL CHALLENGES

These challenges don't disappear with CBDC
They must be designed for
```

---

CROSS-BORDER CBDC APPROACHES

MODEL 1: COMPATIBLE DOMESTIC CBDCs
┌────────────────────────────────────────────────┐
│ Each country has own CBDC │
│ Standards enable cross-border exchange │
│ FX happens at boundaries │
│ Each CB controls own currency │
│ │
│ Complexity: Lower │
│ Integration: Loose │
│ Adoption: Easier │
└────────────────────────────────────────────────┘

MODEL 2: LINKED CBDC SYSTEMS
┌────────────────────────────────────────────────┐
│ Bilateral links between CBDCs │
│ Dedicated corridors │
│ Automated FX and settlement │
│ Shared protocols │
│ │
│ Complexity: Medium │
│ Integration: Moderate │
│ Example: Project Jura │
└────────────────────────────────────────────────┘

MODEL 3: MULTI-CBDC PLATFORM
┌────────────────────────────────────────────────┐
│ Shared platform for multiple CBDCs │
│ Single technical infrastructure │
│ Multiple currencies on one system │
│ Coordinated governance │
│ │
│ Complexity: High │
│ Integration: Deep │
│ Example: mBridge │
└────────────────────────────────────────────────┘

MODEL 4: SINGLE GLOBAL CBDC
┌────────────────────────────────────────────────┐
│ One currency for international use │
│ Single issuing authority │
│ Universal acceptance │
│ │
│ Complexity: Extreme │
│ Political feasibility: Near zero │
│ Status: Theoretical only │
└────────────────────────────────────────────────┘
```

MAJOR CROSS-BORDER CBDC PROJECTS

PROJECT mBRIDGE:
┌────────────────────────────────────────────────┐
│ Participants: │
│ - Hong Kong │
│ - Thailand │
│ - China │
│ - UAE │
│ - Saudi Arabia (joined 2024) │
│ - (BIS withdrew 2024) │
│ │
│ Status: Most advanced multi-CBDC platform │
│ Technology: Custom DLT │
│ Use case: Wholesale cross-border │
│ │
│ Results: Real transactions completed │
│ Challenge: Governance, geopolitics │
└────────────────────────────────────────────────┘

PROJECT JURA:
┌────────────────────────────────────────────────┐
│ Participants: │
│ - France (Banque de France) │
│ - Switzerland (SNB) │
│ - BIS Innovation Hub │
│ │
│ Focus: Euro/Swiss franc cross-border │
│ Technology: DLT-based │
│ Status: Completed pilot │
│ │
│ Result: Proved concept │
└────────────────────────────────────────────────┘

PROJECT DUNBAR:
┌────────────────────────────────────────────────┐
│ Participants: │
│ - Australia │
│ - Malaysia │
│ - Singapore │
│ - South Africa │
│ │
│ Focus: Multi-CBDC for Asia-Pacific │
│ Status: Completed exploration │
└────────────────────────────────────────────────┘

PROJECT AGORÁ:
┌────────────────────────────────────────────────┐
│ Participants: │
│ - BIS + multiple central banks │
│ - US Federal Reserve participating │
│ │
│ Focus: Tokenized deposits + wholesale CBDC │
│ Status: Recently announced │
└────────────────────────────────────────────────┘
```

mBRIDGE ARCHITECTURE

PLATFORM DESIGN:
┌─────────────────────────────────────────────────┐
│ mBRIDGE PLATFORM │
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Hong Kong│ │ Thailand │ │ China │ │
│ │ Node │ │ Node │ │ Node │ │
│ │ (HKD) │ │ (THB) │ │ (CNY) │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ │
│ ┌──────────┐ ┌──────────┐ │
│ │ UAE │ │ Saudi │ │
│ │ Node │ │ Node │ │
│ │ (AED) │ │ (SAR) │ │
│ └──────────┘ └──────────┘ │
│ │
│ Shared DLT infrastructure │
│ Each CB operates node │
│ Each CB issues own CBDC on platform │
└─────────────────────────────────────────────────┘

---

INTEROPERABILITY REQUIREMENTS

TECHNICAL INTEROPERABILITY:
┌────────────────────────────────────────────────┐
│ Data formats: │
│ - Common message standards │
│ - Transaction formatting │
│ - ISO 20022 adoption │
│ │
│ Protocol compatibility: │
│ - API standards │
│ - Authentication │
│ - Communication protocols │
│ │
│ Network connectivity: │
│ - Cross-border network links │
│ - Security requirements │
│ - Latency considerations │
└────────────────────────────────────────────────┘

SEMANTIC INTEROPERABILITY:
┌────────────────────────────────────────────────┐
│ Same data means same thing │
│ │
│ Challenges: │
│ - Different account structures │
│ - Different identifier systems │
│ - Different compliance data │
│ - Different time representations │
└────────────────────────────────────────────────┘

PROCESS INTEROPERABILITY:
┌────────────────────────────────────────────────┐
│ Business processes align │
│ │
│ Challenges: │
│ - Different settlement times │
│ - Different business hours │
│ - Different dispute processes │
│ - Different regulatory requirements │
└────────────────────────────────────────────────┘
```

FOREIGN EXCHANGE CHALLENGES

FX MECHANISM OPTIONS:

Option 1: Central FX Facility
┌────────────────────────────────────────────────┐
│ Platform provides FX │
│ Central liquidity pool │
│ Automated rate determination │
│ │
│ Pro: Simple for users │
│ Con: Who provides liquidity? Who profits? │
└────────────────────────────────────────────────┘

Option 2: Bilateral FX
┌────────────────────────────────────────────────┐
│ Each central bank pair has arrangement │
│ Bilateral liquidity │
│ Negotiated rates │
│ │
│ Pro: Central bank control │
│ Con: N² arrangements needed │
└────────────────────────────────────────────────┘

Option 3: Market-Based FX
┌────────────────────────────────────────────────┐
│ Private market makers on platform │
│ Competitive FX │
│ Market-determined rates │
│ │
│ Pro: Efficient pricing │
│ Con: Private profit from sovereign money │
└────────────────────────────────────────────────┘

• Someone must hold both currencies
• 24/7 operation requires 24/7 liquidity
• Small currency pairs = thin liquidity
• Cost of liquidity provision

CROSS-BORDER SETTLEMENT

THE CHALLENGE:
Different legal systems define finality differently
When is a cross-border transaction truly final?

SCENARIOS:

• Transaction executes

• Both sides settled

• Finality clear

• No problem

• Currency A debited

• Currency B not credited

• What happens?

• Who's responsible?

• Transaction settled

• Later: "This was fraud"

• Can it be reversed?

• Which law applies?

APPROACHES:

• Both sides settle or neither does

• All-or-nothing

• No intermediate state

• Technical solution

• Agreed rules for finality

• Dispute resolution process

• Jurisdictional clarity

• Governance solution

---

CROSS-BORDER CBDC GOVERNANCE

WHO DECIDES?

GOVERNANCE MODELS:

• Central banks take turns

• Shared responsibility

• Complex coordination

• BIS or similar

• Independence

• But: BIS withdrew from mBridge

• Equal partnership

• Consensus required

• Potentially slow

• One CB leads

• Others follow

• Faster but imbalanced

NO EASY ANSWER:
Sovereign central banks don't like
ceding control to others
Governance is THE hard problem
```

GEOPOLITICAL DIMENSIONS

SANCTIONS CONCERN:
┌────────────────────────────────────────────────┐
│ Cross-border CBDC could enable: │
│ │
│ - Sanction evasion │
│ - Bypassing SWIFT │
│ - Alternative to dollar │
│ │
│ US perspective: Threat to sanction power │
│ Others: Reducing US leverage │
└────────────────────────────────────────────────┘

Not unified global improvement
But fragmented alternative systems
```

CROSS-BORDER CBDC REALITY CHECK

WHAT'S LIKELY:

• Continued pilots

• Bilateral links

• Limited production use

• Wholesale focus

• Regional networks

• More bilateral links

• Gradual retail extension

• Standards development

• Unclear

• Depends on geopolitics

• Depends on technology maturity

• Depends on adoption

WHAT'S UNLIKELY:

• Global unified CBDC platform
• Full replacement of correspondent banking
• Immediate retail cross-border
• Politically neutral governance

THE HONEST ASSESSMENT:
Cross-border CBDC is 5-10 years from
material impact on global payments
Pilots prove technology
Politics slows adoption

---

XRP AND CROSS-BORDER CBDC

THE QUESTION:
Will CBDCs use XRP as bridge currency?

REALISTIC ASSESSMENT:
┌────────────────────────────────────────────────┐
│ Unlikely that CBDCs use XRP as bridge │
│ │
│ Reasons: │
│ │
│ 1. Central banks want control │
│ - XRP is not their currency │
│ - Can't control supply │
│ - Can't control price │
│ │
│ 2. Political considerations │
│ - Private asset in sovereign system? │
│ - Who owns XRP matters │
│ - Regulatory uncertainty │
│ │
│ 3. Technical alternatives │
│ - mBridge doesn't need bridge currency │
│ - Bilateral arrangements possible │
│ - Atomic swaps work without XRP │
│ │
│ 4. Pilot evidence │
│ - No major CBDC project uses XRP │
│ - mBridge, Jura, Dunbar: No XRP │
└────────────────────────────────────────────────┘

CBDC IMPACT ON CRYPTO/DIGITAL ASSETS

NET ASSESSMENT:
┌────────────────────────────────────────────────┐
│ CBDCs are neither entirely positive │
│ nor entirely negative for crypto │
│ │
│ Different use cases: │
│ - CBDC: Government digital money │
│ - Crypto: Decentralized alternatives │
│ │
│ Coexistence likely │
│ But: Narratives about "CBDC killing crypto" │
│ or "crypto benefiting from CBDC" │
│ are oversimplified │
└────────────────────────────────────────────────┘
```

---

✅ Cross-border CBDC is technically feasible—pilots have moved real value.

✅ Governance is the hardest problem—technology is easier than politics.

✅ Geopolitics shapes development—US/China dynamics affect everything.

⚠️ Whether multi-CBDC platforms will scale—pilots ≠ production.

⚠️ How governance will be resolved—sovereign central banks resist giving up control.

⚠️ Timeline to meaningful impact—likely longer than proponents suggest.

📌 Assuming cross-border CBDC is imminent—it's years away from scale.

📌 Ignoring geopolitical dimensions—technology alone won't determine outcomes.

📌 Expecting XRP to benefit—central banks are building their own solutions.

Cross-border CBDC is promising but far from reality. Technical challenges are solvable; governance and politics are harder. Projects like mBridge show what's possible, but also reveal the tensions that slow progress. Meaningful impact on global payments is 5-10 years away. XRP holders should not expect CBDCs to drive XRP adoption—central banks are building alternatives that don't need bridge currencies.

---

Assignment: Analyze the cross-border CBDC landscape and its implications for a specific use case (remittances, trade finance, or wholesale settlement).

Time Investment: 3-4 hours

---

End of Lesson 18

Course 58: CBDC Architecture & Design
Lesson 18 of 20