출처 검증 리서치: Institutional Tokenization Demand VS

Verified source facts

1. The 2026 Coinbase and EY-Parthenon survey covers 351 institutional investors. 2. The survey reports 64% of asset managers are interested in tokenizing assets and 63% are interested in allocating to tokenized assets. 3. Coinbase's tokenization analysis identifies market depth, oracle design and regulatory fragmentation as continuing constraints. 4. SEC staff distinguishes issuer-sponsored, custodial third-party and synthetic tokenization structures because rights and intermediary risks differ.

Comparison at a glance

1. Rights analysis: Demand signal

Tokenization analysis must follow the legal and operational chain, not the visual token. The demand signal question asks about survey interest. Identify the issuer, tokenization sponsor, recordkeeper, custodian, broker or platform, and every agreement connecting them. Then separate intent from allocation. 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 sampling limits remains outside the evidence set.

Turn the demand signal finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Separate intent from allocation before comparing yield, speed, or interface quality. Because sampling limits is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

2. Rights analysis: Legal claim

The legal claim question asks about holder's enforceable right. Then review instrument terms.

The available sources frame these questions, while classification remains outside the evidence set.

Turn the legal claim finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Review instrument terms before comparing yield, speed, or interface quality. Because classification is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

3. Rights analysis: Ownership record

The ownership record question asks about authoritative register. Then identify the master record.

The available sources frame these questions, while record conflict remains outside the evidence set.

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

4. Rights analysis: Custody

The custody question asks about underlying asset chain. Then map every intermediary.

The available sources frame these questions, while insolvency remains outside the evidence set.

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

5. Rights analysis: Liquidity

The liquidity question asks about executable market depth. Then stress exit size.

The available sources frame these questions, while fragmentation remains outside the evidence set.

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

6. Rights analysis: Oracle

The oracle question asks about valuation and fallback. Then audit methodology.

The available sources frame these questions, while market closure remains outside the evidence set.

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

7. Rights analysis: Transfers

The transfers question asks about eligibility and restrictions. Then test permitted wallets.

The available sources frame these questions, while failed transfer remains outside the evidence set.

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

8. Rights analysis: Corporate actions

The corporate actions question asks about dividends, voting and splits. Then map procedures.

The available sources frame these questions, while timing gap remains outside the evidence set.

Turn the corporate actions finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Map procedures before comparing yield, speed, or interface quality. Because timing gap is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

9. Rights analysis: Settlement

The settlement question asks about asset and finality. Then reconcile delivery versus payment.

The available sources frame these questions, while operational failure remains outside the evidence set.

Turn the settlement finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Reconcile delivery versus payment before comparing yield, speed, or interface quality. Because operational failure is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

10. Rights analysis: Governance gate

The governance gate question asks about approval before allocation. Then require evidence owners.

The available sources frame these questions, while enthusiasm bias remains outside the evidence set.

Turn the governance gate finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Require evidence owners before comparing yield, speed, or interface quality. Because enthusiasm bias 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 demand signal becomes decisive

Consider a reader whose main constraint is survey interest. The correct response is not to infer a universal platform or product winner. It is to separate intent from allocation, 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 legal claim becomes decisive

Consider a reader whose main constraint is holder's enforceable right. It is to review instrument terms, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when ownership record becomes decisive

Consider a reader whose main constraint is authoritative register. It is to identify the master record, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when custody becomes decisive

Consider a reader whose main constraint is underlying asset chain. It is to map every intermediary, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when liquidity becomes decisive

Consider a reader whose main constraint is executable market depth. It is to stress exit size, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when oracle becomes decisive

Consider a reader whose main constraint is valuation and fallback. It is to audit methodology, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• 2026 Institutional Investor Survey with EY-Parthenon — Coinbase Institutional
• Major trends in tokenization — Coinbase Institutional
• Statement on Tokenized Securities — U.S. SEC