Tool 58 · Compliance

CBDC Interop
Scenario Modeler

Template-driven interoperability scenario analysis for cross-CBDC and CBDC-to-DLT settlement. Model atomic settlement, payment-versus-payment (PvP), failure modes, and regulatory reporting obligations between mBridge, Digital Euro, Project Dunbar, SAMA/CBUAE CBDCs and Corda, Canton, Besu DLT platforms. All scenarios generated client-side from embedded reference data.

Zero PII · Client-Side Only📋 Template-Driven ScenariosmBridge · Digital Euro · DunbarAP2 JSON Export
Scenario Parameters
Side A — CBDC
CBDC Platform Asset Leg
Side B — DLT
Settlement Platform Cash Leg
Settlement Condition
Failure Scenario to Model
📋 Client-Side · No API Required Scenarios are generated from embedded platform reference data and structured narrative templates. All computation runs in your browser — zero server calls, zero PII.
CBDC Interop Scenario Report
🌐
No Scenario Generated
Configure the CBDC and DLT platforms, select a settlement condition and failure scenario, then click Generate AI Scenario.
About This Tool▾

Scenario engine: Scenarios are assembled from structured platform reference data embedded in the tool. Each combination of CBDC, DLT platform, settlement condition, and failure scenario maps to specific narrative templates drawn from Post Oak Labs A2A architecture documentation, BIS Innovation Hub publications, and vendor technical specifications.

PvP engine reference: For Besu scenarios, the narrative includes the Adhara SILVER PvP engine design (Besu A2A doc §3.2). For Canton scenarios, the two-phase commit via the Global Synchronizer (Canton doc §4) is referenced.

All client-side: No API calls are made. Scenario text is deterministic and generated entirely in your browser from the embedded reference corpus.