Исследование с проверкой источников: Stablecoins VS Tokenized Deposits

Verified source facts

1. BIS analysis distinguishes tokenized commercial-bank deposits from stablecoins by issuer liability, convertibility and monetary-system integration. 2. The BIS argues that singleness of money depends on payment instruments exchanging at par rather than fragmenting into issuer-specific prices. 3. Stablecoin usefulness depends on an issuer's reserve, redemption, governance and legal arrangements, not the token label alone. 4. Central-bank surveys treat tokenized deposits, wholesale CBDC and fast-payment infrastructure as separate design paths that may coexist.

Comparison at a glance

1. Rights analysis: Obligor

Tokenization analysis must follow the legal and operational chain, not the visual token. The obligor question asks about the entity legally owing the money claim. Identify the issuer, tokenization sponsor, recordkeeper, custodian, broker or platform, and every agreement connecting them. Then identify the issuer or deposit-taking bank. A wallet balance alone cannot answer which person or system has the enforceable obligation.

Test the arrangement under a disagreement. If the chain record and master securityholder file diverge, which one controls? If an intermediary fails, is the holder a customer, beneficial owner, secured claimant, or unsecured creditor? If a transfer is technically possible but legally restricted, what process reverses or freezes it? The available sources frame these questions, while treatment in an untested dispute remains outside the evidence set.

Turn the obligor finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Identify the issuer or deposit-taking bank before comparing yield, speed, or interface quality. Because treatment in an untested dispute is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

2. Rights analysis: Balance-sheet location

The balance-sheet location question asks about reserves versus a bank deposit liability. Then read the audited or regulated disclosure.

The available sources frame these questions, while undisclosed intraday exposures remains outside the evidence set.

Turn the balance-sheet location finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Read the audited or regulated disclosure before comparing yield, speed, or interface quality. Because undisclosed intraday exposures is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

3. Rights analysis: Par conversion

The par conversion question asks about whether one unit converts to sovereign money at par. Then verify direct redemption rights and fees.

The available sources frame these questions, while market price during stress remains outside the evidence set.

Turn the par conversion finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Verify direct redemption rights and fees before comparing yield, speed, or interface quality. Because market price during stress is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

4. Rights analysis: Eligible holder

The eligible holder question asks about who can hold or redeem directly. Then separate token transfer from issuer onboarding.

The available sources frame these questions, while eligibility for an unobserved user remains outside the evidence set.

Turn the eligible holder finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Separate token transfer from issuer onboarding before comparing yield, speed, or interface quality. Because eligibility for an unobserved user is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

5. Rights analysis: Settlement asset

The settlement asset question asks about commercial-bank, central-bank or issuer money. Then map the cash leg for the actual transaction.

The available sources frame these questions, while future infrastructure changes remains outside the evidence set.

Turn the settlement asset finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Map the cash leg for the actual transaction before comparing yield, speed, or interface quality. Because future infrastructure changes is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

6. Rights analysis: Transfer perimeter

The transfer perimeter question asks about networks, permissioning and intermediaries. Then identify every operator in the path.

The available sources frame these questions, while cross-network recovery outcomes remains outside the evidence set.

Turn the transfer perimeter finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Identify every operator in the path before comparing yield, speed, or interface quality. Because cross-network recovery outcomes is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

7. Rights analysis: Finality

The finality question asks about the legal and technical completion point. Then record the authoritative finality event.

The available sources frame these questions, while cross-system conflict treatment remains outside the evidence set.

Turn the finality finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Record the authoritative finality event before comparing yield, speed, or interface quality. Because cross-system conflict treatment is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

8. Rights analysis: Insolvency

The insolvency question asks about claim priority and asset segregation. Then read the governing legal documents.

The available sources frame these questions, while court outcome in a future failure remains outside the evidence set.

Turn the insolvency finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Read the governing legal documents before comparing yield, speed, or interface quality. Because court outcome in a future failure is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

9. Rights analysis: Operating continuity

The operating continuity question asks about hours, outages and fallback rails. Then test redemption and transfer contingencies.

The available sources frame these questions, while availability in systemic stress remains outside the evidence set.

Turn the operating continuity finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Test redemption and transfer contingencies before comparing yield, speed, or interface quality. Because availability in systemic stress is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

10. Rights analysis: Use case fit

The use case fit question asks about payments, settlement, treasury or on-chain trading. Then select by verified claim and workflow.

The available sources frame these questions, while future adoption or liquidity remains outside the evidence set.

Turn the use case fit finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Select by verified claim and workflow before comparing yield, speed, or interface quality. Because future adoption or liquidity is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

Decision scenarios

Scenario 1: when obligor becomes decisive

Consider a reader whose main constraint is the entity legally owing the money claim. The correct response is not to infer a universal platform or product winner. It is to identify the issuer or deposit-taking bank, 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 balance-sheet location becomes decisive

Consider a reader whose main constraint is reserves versus a bank deposit liability. It is to read the audited or regulated disclosure, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when par conversion becomes decisive

Consider a reader whose main constraint is whether one unit converts to sovereign money at par. It is to verify direct redemption rights and fees, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when eligible holder becomes decisive

Consider a reader whose main constraint is who can hold or redeem directly. It is to separate token transfer from issuer onboarding, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when settlement asset becomes decisive

Consider a reader whose main constraint is commercial-bank, central-bank or issuer money. It is to map the cash leg for the actual transaction, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when transfer perimeter becomes decisive

Consider a reader whose main constraint is networks, permissioning and intermediaries. It is to identify every operator in the path, retain the evidence, and define a stop condition before funds or permissions are committed.