Central bank digital currencies, stablecoins, and decentralised crypto are all “digital money”, but they sit at very different points on risk, privacy, and control. This tool lays them side by side across twelve dimensions so you can see exactly where they diverge.
How it works
The tool uses a structured reference matrix built from the defining properties of each asset class. The key axis is who stands behind the money:
- A CBDC is a direct liability of the central bank — lowest counterparty risk, immediate legal finality, but designed for traceability and issuer control.
- A stablecoin is a private issuer’s promise to hold a fiat peg using reserves — strong global rails, but exposed to de-peg and reserve risk and issuer freeze powers.
- Decentralised crypto has no issuer — no counterparty risk and strong censorship resistance, but full market volatility.
Each of the twelve rows compares the assets on a single dimension, so you can focus on whatever matters for your use case.
Notes and caveats
These are generalisations. A specific instrument can break the pattern: some CBDC designs offer more privacy, some stablecoins share reserve yield, and some chains finalise far faster than the proof-of-work norm. Use the matrix to frame the trade-offs, then confirm the details of any specific CBDC, stablecoin, or network against its primary documentation. This is not financial advice.
Why the differences matter in practice
The twelve dimensions in the comparison tool are not abstract — each one has concrete real-world consequences for users and businesses:
Counterparty risk determines what happens if the issuer fails. CBDC holders face no issuer credit risk because the central bank is the money itself. Stablecoin holders depend on the issuer holding adequate, unencumbered reserves — a risk that has materialised in historical de-peg events. Decentralised crypto has no issuer to fail, but protocol or smart-contract bugs create a different failure mode.
Privacy shapes who can see your transactions. Most CBDC designs include anti-money-laundering traceability, meaning the issuing authority has full visibility of all payments. Some designs propose tiered privacy — small everyday transactions shielded, larger ones transparent — but no major retail CBDC has deployed this in practice at scale. Privacy coins and some Layer 2 protocols offer cryptographic shielding, but regulatory acceptance is limited.
Censorship resistance is the flip side of control. A CBDC can freeze addresses or reverse transactions by design. Stablecoin issuers can blacklist wallet addresses. Decentralised crypto on mature proof-of-stake or proof-of-work networks is significantly harder to censor at the protocol level, though on-ramps and exchanges remain regulated choke points.
Cross-border usability is currently where CBDCs are weakest relative to crypto. Each CBDC is a national liability; moving value across borders requires interoperability agreements between central banks. Stablecoins and decentralised crypto settle cross-border in minutes through any internet connection, which is why remittance use cases have gravitated toward them.
Practical use cases by type
| Use case | Best fit |
|---|---|
| Everyday domestic payments | CBDC (low risk, no volatility) |
| Cross-border remittance | Stablecoin or crypto (fast, cheap rails) |
| DeFi lending and yield | Decentralised crypto (composable, permissionless) |
| Institutional settlement | CBDC wholesale variants (legal finality) |
| Inflation hedge | Decentralised crypto (fixed supply assets) |