FSB DeFi, Tokenisation and Data-Gap Financial Stability Risk Map
Verified Fact Boundary
1. FSB describes crypto-assets, stablecoins and DeFi as closely interrelated segments that should be assessed holistically. 2. FSB's DeFi risk release says DeFi can replicate traditional finance functions while exposing operational, liquidity, maturity, leverage and interconnectedness vulnerabilities. 3. FSB's DeFi risk release identifies tokenisation growth and DeFi data gaps as areas for additional work. 4. FSB's 2022 crypto risk assessment discusses vulnerabilities across unbacked crypto-assets, stablecoins and DeFi. 5. BIS Basel SCO60 sets out prudential treatment for banks' cryptoasset exposures and includes tokenised traditional assets within defined scope conditions. 6. Institutional readiness for DeFi or tokenisation depends on data, exposure, liquidity, governance, custody and interconnection evidence.
Show less
Decision Matrix
Article table: scroll horizontally, or focus the table area and use the arrow keys.
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Exposure | DeFi and tokenisation risks depend on who is exposed and how | identify direct, indirect and off-balance-sheet exposure | hidden leverage through intermediaries |
| Liquidity | liquidity and maturity mismatch can make exits fragile | map redemption, withdrawal and settlement timing | stress-period depth |
| Governance | decentralisation claims do not remove governance risk | identify upgrade, admin, oracle and emergency powers | informal governance influence |
| Data gap | public chain data does not automatically reveal all obligations | separate observable transfers from private exposures | offchain collateral records |
| TradFi linkage | tokenisation can increase links between crypto markets and traditional finance | map regulated entities and settlement dependencies | future institutional adoption |
| Prudential boundary | bank exposure treatment depends on classification and activity | check SCO60-style classification before capital claims | jurisdictional implementation |
| Stop rule | stop when exposure, liquidity, governance or data evidence is missing | publish a risk map rather than an institutional-readiness claim | future standard-setting updates |
Source Map
- Financial Stability Board: Crypto-assets and Global Stablecoins (fsb-crypto-hub)
- Financial Stability Board: FSB assesses financial stability risks of decentralised finance (fsb-defi-risk)
- Financial Stability Board: Assessment of Risks to Financial Stability from Crypto-assets (fsb-crypto-risk-assessment)
- Bank for International Settlements: Cryptoasset exposures (bis-sco60)
Control Notes
1. Exposure
Exposure is the part of the decision where a public source has to become an operating rule. In this package, it means DeFi and tokenisation risks depend on who is exposed and how. The useful action is to identify direct, indirect and off-balance-sheet exposure. The unresolved edge is hidden leverage through intermediaries, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.
For an operator, exposure should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material. The record can stay simple: the official source URL, the date checked, the product or network under review, and a non-secret note describing why the next step is acceptable. Screenshots should avoid balances, identity documents, tax identifiers, API keys, recovery phrases, private keys, passphrases, verification codes and support-ticket private data.
2. Liquidity
Liquidity is the part of the decision where a public source has to become an operating rule. In this package, it means liquidity and maturity mismatch can make exits fragile. The useful action is to map redemption, withdrawal and settlement timing. The unresolved edge is stress-period depth, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.
For an operator, liquidity should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.
3. Governance
Governance is the part of the decision where a public source has to become an operating rule. In this package, it means decentralisation claims do not remove governance risk. The useful action is to identify upgrade, admin, oracle and emergency powers. The unresolved edge is informal governance influence, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.
For an operator, governance should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.
4. Data gap
Data gap is the part of the decision where a public source has to become an operating rule. In this package, it means public chain data does not automatically reveal all obligations. The useful action is to separate observable transfers from private exposures. The unresolved edge is offchain collateral records, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.
For an operator, data gap should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.
5. TradFi linkage
TradFi linkage is the part of the decision where a public source has to become an operating rule. In this package, it means tokenisation can increase links between crypto markets and traditional finance. The useful action is to map regulated entities and settlement dependencies. The unresolved edge is future institutional adoption, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.
For an operator, tradfi linkage should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.
6. Prudential boundary
Prudential boundary is the part of the decision where a public source has to become an operating rule. In this package, it means bank exposure treatment depends on classification and activity. The useful action is to check SCO60-style classification before capital claims. The unresolved edge is jurisdictional implementation, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.
For an operator, prudential boundary should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.
7. Stop rule
Stop rule is the part of the decision where a public source has to become an operating rule. In this package, it means stop when exposure, liquidity, governance or data evidence is missing. The useful action is to publish a risk map rather than an institutional-readiness claim. The unresolved edge is future standard-setting updates, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.
Known Unknowns
- hidden leverage through intermediaries
- stress-period depth
- informal governance influence
- offchain collateral records
- future institutional adoption
- jurisdictional implementation
- future standard-setting updates
Practical Takeaway
The safest version of this article is the one that stays boring and exact. FSB materials treat DeFi, stablecoins and tokenisation as connected financial-stability questions, not as isolated product slogans. The FSB crypto-assets hub says unbacked crypto-assets, stablecoins and DeFi should be considered holistically; its DeFi risk release says DeFi can replicate traditional finance functions while exposing operational fragility, liquidity and maturity mismatch, leverage and interconnectedness; and the same release identifies tokenisation and data gaps as follow-up work. The decision outcome is to map exposure, leverage, liquidity, governance, oracle, bridge, custody, data availability and TradFi linkage before treating a tokenised or DeFi route as institutionally ready. The user outcome is a clearer next inspection step, not a promise that a platform, API, transfer route, report, market contract or tokenized asset will work under every future condition.
Topic hubs & tools:Crypto regulation news