How do CBDCs (central bank digital currencies) interact with public blockchains?
Login Required
Please sign in with Google to answer this question.
2 Answers
0
From my experience with CBDC pilots, these digital currencies usually live on a central bank’s ledger or a permissioned network, not directly on public blockchains. When you want interaction with public rails, you use a gateway/bridge pattern: lock or settle CBDC on the central ledger and mint a tokenized representation on a public chain, or burn the public-chain token to release CBDC on the central ledger. This preserves control, compliance, and settlement finality while still enabling cross-chain liquidity. In a project I worked on, we connected a CBDC wrapper to Ethereum; CBDC finality was guaranteed by the issuer, but user-facing settlements depended on the public-chain throughput. Privacy and KYC were enforced at the bridge, not on-chain. Lesson: design for dual reconciliation, liquidity management, and secure relays; plan standards and risk controls upfront.
0
0
From my time working on CBDC pilots, I've learned that central banks prize control, privacy, and legal finality, so they issue CBDCs on permissioned ledgers rather than public blockchains. Public chains offer open settlement and programmable money, but they lack sovereign finality and the privacy controls a central bank needs. In practice, CBDCs stay on a central bank, or bank‑cooperative network (Hyperledger Fabric, Quorum, or a proprietary ledger) with wallets held by regulated institutions and retail users via regulated operators. Interactions with public blockchains happen at the edges: you can tokenize CBDC claims so developers can use DeFi or cross‑border rails, typically via a gateway or bridge that mints on a public chain when CBDC is locked on the central ledger, and burns when notes are released back. I've helped prototype a two‑way bridge: the CBDC ledger tracks actual cash claims; an authorized gateway issues ERC‑20 style CBDC tokens on Ethereum, burning/minting in lockstep with on‑chain settlements. The hard part is risk: privacy, regulatory oversight, and bridge security demand rigorous controls, audits, and clear governance.
0