Исследование с проверкой источников: Nasdaq Tokenized Securities Approval
Текст статьи показан в проверенном английском оригинале. Перевод будет добавлен после проверки источников.
Direct answer
The SEC approved Nasdaq's modified tokenized-securities rule change on March 18, 2026, but approval is not the same as immediate retail availability. Under the approved design, eligible tokenized and traditional shares use the same order book and execution priority only when they are fungible, share the same CUSIP and symbol, and confer equivalent rights. DTC eligibility, participant status, registered wallets, supported networks and operational launch infrastructure remain separate gates, and ineligible tokenization instructions fall back to traditional settlement.
Свернуть
Verified source facts
1. The SEC order dated March 18, 2026 approves Nasdaq's rule change as modified by Amendment No. 2. 2. Eligible tokenized shares must be fungible with traditional shares, use the same CUSIP and symbol, and provide equivalent shareholder rights to trade on the same order book with the same priority. 3. The design communicates a tokenization preference to DTC after execution; if participant, asset, network or wallet requirements fail, DTC settles the trade in traditional form. 4. The order says implementation depends on DTC infrastructure and post-trade services, with Nasdaq required to provide at least 30 days' notice before trading begins.
Comparison at a glance
Таблица статьи: прокрутите по горизонтали или установите фокус на области таблицы и используйте клавиши со стрелками.
| Decision layer | What to inspect | Minimum safe action |
|---|---|---|
| Approval status | approved rule versus operational launch | separate legal approval from live availability |
| Eligible asset | Russell 1000 and specified index ETFs under the pilot | check the current trader alert list |
| Participant | DTC Eligible Participant status | verify the intermediary's pilot eligibility |
| Fungibility | interchangeability with the traditional share | confirm the same class and entitlement |
| Identifier | same CUSIP and trading symbol | match authoritative security identifiers |
| Rights | equity, dividend, voting and liquidation entitlements | read the governing holder record |
| Order book | same execution priority and market data | do not infer separate token liquidity |
| Settlement | DTC token or traditional post-trade form | verify wallet and network eligibility |
| Corporate actions | possible de-tokenization for distributions | map conversion and notification procedures |
| User boundary | institutional pilot mechanics versus retail product | require an actual broker offering before claiming access |
1. Rights analysis: Approval status
Tokenization analysis must follow the legal and operational chain, not the visual token. The approval status question asks about approved rule versus operational launch. Identify the issuer, tokenization sponsor, recordkeeper, custodian, broker or platform, and every agreement connecting them. Then separate legal approval from live availability. 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 first trading date remains outside the evidence set.
Turn the approval status finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Separate legal approval from live availability before comparing yield, speed, or interface quality. Because first trading date is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
2. Rights analysis: Eligible asset
The eligible asset question asks about Russell 1000 and specified index ETFs under the pilot. Then check the current trader alert list.
The available sources frame these questions, while later additions remains outside the evidence set.
Turn the eligible asset finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Check the current trader alert list before comparing yield, speed, or interface quality. Because later additions is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
3. Rights analysis: Participant
The participant question asks about DTC Eligible Participant status. Then verify the intermediary's pilot eligibility.
The available sources frame these questions, while retail access path remains outside the evidence set.
Turn the participant finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Verify the intermediary's pilot eligibility before comparing yield, speed, or interface quality. Because retail access path is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
4. Rights analysis: Fungibility
The fungibility question asks about interchangeability with the traditional share. Then confirm the same class and entitlement.
The available sources frame these questions, while edge-case restrictions remains outside the evidence set.
Turn the fungibility finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Confirm the same class and entitlement before comparing yield, speed, or interface quality. Because edge-case restrictions is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
5. Rights analysis: Identifier
The identifier question asks about same CUSIP and trading symbol. Then match authoritative security identifiers.
The available sources frame these questions, while corporate-action changes remains outside the evidence set.
Turn the identifier finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Match authoritative security identifiers before comparing yield, speed, or interface quality. Because corporate-action changes is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
6. Rights analysis: Rights
The rights question asks about equity, dividend, voting and liquidation entitlements. Then read the governing holder record.
The available sources frame these questions, while dispute treatment remains outside the evidence set.
Turn the rights 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 holder record before comparing yield, speed, or interface quality. Because dispute treatment is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
7. Rights analysis: Order book
The order book question asks about same execution priority and market data. Then do not infer separate token liquidity.
The available sources frame these questions, while launch-day depth remains outside the evidence set.
Turn the order book finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Do not infer separate token liquidity before comparing yield, speed, or interface quality. Because launch-day depth is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
8. Rights analysis: Settlement
The settlement question asks about DTC token or traditional post-trade form. Then verify wallet and network eligibility.
The available sources frame these questions, while processing exceptions 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. Verify wallet and network eligibility before comparing yield, speed, or interface quality. Because processing exceptions is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
9. Rights analysis: Corporate actions
The corporate actions question asks about possible de-tokenization for distributions. Then map conversion and notification procedures.
The available sources frame these questions, while operational timing 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 conversion and notification procedures before comparing yield, speed, or interface quality. Because operational timing is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
10. Rights analysis: User boundary
The user boundary question asks about institutional pilot mechanics versus retail product. Then require an actual broker offering before claiming access.
The available sources frame these questions, while broker availability remains outside the evidence set.
Turn the user boundary finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Require an actual broker offering before claiming access before comparing yield, speed, or interface quality. Because broker availability 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 approval status becomes decisive
Consider a reader whose main constraint is approved rule versus operational launch. The correct response is not to infer a universal platform or product winner. It is to separate legal approval from live availability, 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 eligible asset becomes decisive
Consider a reader whose main constraint is Russell 1000 and specified index ETFs under the pilot. It is to check the current trader alert list, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 3: when participant becomes decisive
Consider a reader whose main constraint is DTC Eligible Participant status. It is to verify the intermediary's pilot eligibility, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 4: when fungibility becomes decisive
Consider a reader whose main constraint is interchangeability with the traditional share. It is to confirm the same class and entitlement, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 5: when identifier becomes decisive
Consider a reader whose main constraint is same CUSIP and trading symbol. It is to match authoritative security identifiers, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 6: when rights becomes decisive
Consider a reader whose main constraint is equity, dividend, voting and liquidation entitlements. It is to read the governing holder record, retain the evidence, and define a stop condition before funds or permissions are committed.