Recherche vérifiée par sources: BIS Central BANK Money

Verified source facts

1. The BIS tokenisation report says token arrangements can change market structures through platform-based intermediation across the end-to-end lifecycle of financial assets. 2. The BIS tokenisation report says safety and efficiency gains require sound governance and risk management, and FMI risks may apply differently. 3. The BIS 2026 speech says policy recommendations focus on tightening stablecoin safeguards and integrating tokenisation into the two-tier system anchored in central bank money. 4. The FSB says crypto-asset markets, stablecoins and DeFi are closely interrelated and should be assessed holistically for financial stability risks. 5. SEC staff says a tokenized security is still a security-format financial instrument with record-of-ownership implications rather than a separate magic asset class.

Comparison at a glance

1. Usage and measurement test: Settlement asset

Stablecoin adoption cannot be inferred from a single gross counter. The settlement asset dimension concerns central bank money, bank deposit, stablecoin or tokenized fund. Define the economic job, unit of observation, time window and entities included before counting, then name the liability before comparing rails. Otherwise one routed transaction, exchange rebalance or contract hop may be mistaken for several independent users or payments.

Separate ledger events from economic outcomes. A transfer can be real on-chain yet still represent internal treasury movement, automated arbitrage, bridge routing, collateral management or redemption rather than a purchase. Official sources can frame the categories, but they do not resolve future policy treatment. The dataset and classification method therefore belong beside every headline number.

For settlement asset, publish the numerator, denominator and exclusions that support the claim. Make the analyst name the liability before comparing rails, and compare at least one activity metric with one outcome metric relevant to central bank money, bank deposit, stablecoin or tokenized fund. Because future policy treatment remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

2. Usage and measurement test: Issuer liability

The issuer liability dimension concerns who owes redemption or payment. Define the economic job, unit of observation, time window and entities included before counting, then read the issuer and reserve documents.

Official sources can frame the categories, but they do not resolve support under stress.

For issuer liability, publish the numerator, denominator and exclusions that support the claim. Make the analyst read the issuer and reserve documents, and compare at least one activity metric with one outcome metric relevant to who owes redemption or payment. Because support under stress remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

3. Usage and measurement test: Governance

The governance dimension concerns rule updates, validator controls and platform operators. Define the economic job, unit of observation, time window and entities included before counting, then map authority before relying on speed.

Official sources can frame the categories, but they do not resolve emergency governance decisions.

For governance, publish the numerator, denominator and exclusions that support the claim. Make the analyst map authority before relying on speed, and compare at least one activity metric with one outcome metric relevant to rule updates, validator controls and platform operators. Because emergency governance decisions remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

4. Usage and measurement test: Risk management

The risk management dimension concerns operational, cyber, liquidity and legal controls. Define the economic job, unit of observation, time window and entities included before counting, then require a documented control owner.

Official sources can frame the categories, but they do not resolve undisclosed internal procedures.

For risk management, publish the numerator, denominator and exclusions that support the claim. Make the analyst require a documented control owner, and compare at least one activity metric with one outcome metric relevant to operational, cyber, liquidity and legal controls. Because undisclosed internal procedures remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

5. Usage and measurement test: Interoperability

The interoperability dimension concerns movement across ledgers and payment systems. Define the economic job, unit of observation, time window and entities included before counting, then treat bridges and messaging layers as dependencies.

Official sources can frame the categories, but they do not resolve future standards convergence.

For interoperability, publish the numerator, denominator and exclusions that support the claim. Make the analyst treat bridges and messaging layers as dependencies, and compare at least one activity metric with one outcome metric relevant to movement across ledgers and payment systems. Because future standards convergence remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

6. Usage and measurement test: Redemption

The redemption dimension concerns cash, deposit, security or other claim. Define the economic job, unit of observation, time window and entities included before counting, then test the route and timing before scale.

Official sources can frame the categories, but they do not resolve redemption under market stress.

For redemption, publish the numerator, denominator and exclusions that support the claim. Make the analyst test the route and timing before scale, and compare at least one activity metric with one outcome metric relevant to cash, deposit, security or other claim. Because redemption under market stress remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

7. Usage and measurement test: User protection

The user protection dimension concerns disclosures, complaint routes and legal perimeter. Define the economic job, unit of observation, time window and entities included before counting, then separate regulated rights from interface claims.

Official sources can frame the categories, but they do not resolve cross-border conflicts.

For user protection, publish the numerator, denominator and exclusions that support the claim. Make the analyst separate regulated rights from interface claims, and compare at least one activity metric with one outcome metric relevant to disclosures, complaint routes and legal perimeter. Because cross-border conflicts remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

8. Usage and measurement test: Financial stability

The financial stability dimension concerns interlinkages with DeFi, exchanges and reserves. Define the economic job, unit of observation, time window and entities included before counting, then avoid isolating one token from the wider system.

Official sources can frame the categories, but they do not resolve contagion behavior.

For financial stability, publish the numerator, denominator and exclusions that support the claim. Make the analyst avoid isolating one token from the wider system, and compare at least one activity metric with one outcome metric relevant to interlinkages with DeFi, exchanges and reserves. Because contagion behavior remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

9. Usage and measurement test: Evidence age

The evidence age dimension concerns policy paper, speech or binding rule. Define the economic job, unit of observation, time window and entities included before counting, then label whether evidence is analysis or enforceable text.

Official sources can frame the categories, but they do not resolve future rulemaking.

For evidence age, publish the numerator, denominator and exclusions that support the claim. Make the analyst label whether evidence is analysis or enforceable text, and compare at least one activity metric with one outcome metric relevant to policy paper, speech or binding rule. Because future rulemaking remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

10. Usage and measurement test: Decision boundary

The decision boundary dimension concerns payment convenience versus money trust. Define the economic job, unit of observation, time window and entities included before counting, then prefer explicit obligations over marketing speed.

Official sources can frame the categories, but they do not resolve macroeconomic outcomes.

For decision boundary, publish the numerator, denominator and exclusions that support the claim. Make the analyst prefer explicit obligations over marketing speed, and compare at least one activity metric with one outcome metric relevant to payment convenience versus money trust. Because macroeconomic outcomes remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

Decision scenarios

Scenario 1: when settlement asset becomes decisive

Consider a reader whose main constraint is central bank money, bank deposit, stablecoin or tokenized fund. The correct response is not to infer a universal platform or product winner. It is to name the liability before comparing rails, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when issuer liability becomes decisive

Consider a reader whose main constraint is who owes redemption or payment. It is to read the issuer and reserve documents, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when governance becomes decisive

Consider a reader whose main constraint is rule updates, validator controls and platform operators. It is to map authority before relying on speed, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when risk management becomes decisive

Consider a reader whose main constraint is operational, cyber, liquidity and legal controls. It is to require a documented control owner, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when interoperability becomes decisive

Consider a reader whose main constraint is movement across ledgers and payment systems. It is to treat bridges and messaging layers as dependencies, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when redemption becomes decisive

Consider a reader whose main constraint is cash, deposit, security or other claim. It is to test the route and timing before scale, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Tokenisation in the context of money and other assets — Bank for International Settlements
• Anchoring trust in money: innovation beyond stablecoins — Bank for International Settlements
• Crypto-assets and Global Stablecoins — Financial Stability Board
• Statement on Tokenized Securities — U.S. SEC Staff