`rwa tokenization platform` 通常同时包含“马上做决策”和“深度核验”的需求。本页先给实施路径，再给证据、边界和风险控制。
发布时间 2026-04-23 · 复核时间 2026-04-23 · 下次复核 2026-10-23
输出综合目标匹配、访问约束、公开证据强度与边界惩罚项。
来源检查时间 2026-04-23
RWA.xyz platform index indicates the market is large enough that one flat vendor list under-serves most search intent.
来源 S1
Represented and distributed frameworks are materially different in scale and operating model; route decisions should not treat them as interchangeable.
来源 S1
Complementary reviews cover over 40 jurisdictions and show uneven implementation, which keeps regulatory-arbitrage risk live.
来源 S22 · S23
EU-linked routes should treat ICT governance, incident response, testing, and third-party risk controls as procurement-time checks.
来源 S24
FATF reports broad legal adoption progress, but implementation quality still varies by jurisdiction and institution.
来源 S13
Pilot-regime access in the EU has hard scaling thresholds; venue eligibility can change as issuance grows.
来源 S14
首屏工具先判断你更适合发行栈、分销栈、交易耦合栈或分析优先路径；后面的报告层再补方法、证据、风险边界与场景动作。
工具层给出实施路径与动作建议，报告层补充置信度、边界和取舍，帮助你做出可执行决策。
For `rwa tokenization platform`, the first decision is implementation lane fit: issuance stack, distribution stack, secondary venue coupling, or analytics-only discovery.
来源 S1 · S10
Tokenization format alone does not standardize legal treatment. MiCA excludes qualifying financial instruments, and U.S. staff guidance distinguishes issuer-sponsored, custodial, and synthetic structures.
来源 S12 · S17
Public permissions improve trust but do not prove product-level eligibility, tradability, or rights. Product terms and investor class still decide practical access.
来源 S4 · S6 · S8 · S9
2025 implementation reviews across FSB and IOSCO scopes show progress, yet notable jurisdiction-level gaps remain, especially where cross-border coordination and stablecoin controls lag.
来源 S21 · S22 · S23
Segregation, reconciliation with independent assurance, and operational-resilience controls should be validated before contract or onboarding decisions.
来源 S20 · S21 · S24
This report marks unresolved comparability fields as “待确认 / no reliable public data” rather than synthesizing false precision.
来源 S1 · S4 · S7 · S9 · S13 · S18 · S21 · S23
该工具是确定性逻辑：按目标、访问边界、地区与采购优先级路由，再输出候选列表。
这些快照级数字用于证明为何要先拆分实施路径，但不能替代产品级尽调。除非来源备注另有说明，所有数据均复核于 2026-04-23。
| 指标 | 数值 | 解读 |
|---|---|---|
| Platforms tracked (RWA.xyz) | 171 | Platform supply is broad; users need routing by objective rather than one “top 10” list. 来源 S1 |
| Distributed asset value (RWA.xyz) | $15.23B | High-level market size supports discovery, but does not determine which platform lane matches your constraints. 来源 S1 |
| Represented asset value (RWA.xyz) | $332.13B | Represented routes currently dominate aggregate value; transparency-layer records and onchain distribution are not equivalent execution paths. 来源 S1 |
| Holders tracked (RWA.xyz) | 732,344 | Growing holder counts increase platform noise and category overlap, reinforcing tool-first filtering. 来源 S1 |
| Distributed vs represented asset value | $15.23B distributed / $332.13B represented | The split reflects different operational frameworks; using one pooled leaderboard can hide material implementation differences. 来源 S1 |
| FSB implementation review scope (2025-10-16) | 37 jurisdictions reviewed (including 13 non-FSB), using data as of 2025-08 | Progress exists, but implementation remains incomplete and inconsistent across jurisdictions. 来源 S22 · S23 |
| IOSCO pilot implementation scope (2025-10-16) | 20 jurisdictions; 10 of 18 recommendations assessed | The assessment is a maturity checkpoint, not proof that full framework outcomes are uniformly achieved. 来源 S21 · S23 |
| IOSCO custody-control implementation signal (2025) | Recommendation 13 final in 14 jurisdictions; Recommendation 15 final in 14 jurisdictions | Custody segregation and reconciliation controls are advancing, but not yet universal. 来源 S21 |
| FATF Travel Rule implementation progress (2025-06-26) | 99 jurisdictions; materially important jurisdictions ~98% of VA market | Legislative progress is substantial but does not imply uniform supervisory enforcement or operational interoperability. 来源 S13 |
| EU DLT infrastructures listed by ESMA (2026-01) | 6 authorised infrastructures; start dates from 2024-10-11 to 2025-11-26 | Pilot infrastructure availability is real, but exemptions and thresholds still constrain production design. 来源 S16 |
| EU DLT Pilot hard thresholds | Shares < EUR 500M issuer cap; debt < EUR 1B issue size; aggregate cap EUR 6B (transition at EUR 9B) | Pilot eligibility can change as issuance scales, so venue strategy should include threshold monitoring from day one. 来源 S14 · S15 |
| DORA operational-resilience baseline | Applies since 2025-01-17; threat-led testing at least every 3 years for in-scope non-micro entities | EU-linked routes should assign ownership for ICT incidents, testing, and third-party dependencies before launch. 来源 S24 |
| MiCA application window and perimeter | Titles III/IV from 2024-06-30; broader application from 2024-12-30; financial instruments out-of-scope | EU routes must classify whether an instrument falls inside MiCA or under financial-instrument regimes before choosing platform lanes. 来源 S17 |
| Cross-platform fee comparability | 待确认 / no reliable public matrix | Public disclosures use inconsistent fee structures across issuer, broker, venue, and custody layers, so this page avoids a synthetic total-cost leaderboard. 来源 S4 · S7 · S9 · S18 |
| Cross-platform real-time secondary depth by asset | 待确认 / no reliable public matrix | No standardized, continuously comparable public dataset was found across all covered lanes as of 2026-04-23. 来源 S4 · S5 · S6 · S7 · S9 |
适合人群
不适合人群
本节先明确范围，避免用户强行把低置信度结果当作可执行结论。
当目标明确、访问边界现实、且有来源支撑的实施路径证据时，结果可信度更高。
若目标不清，工具会有意偏向 monitor 或 boundary 输出。
若缺少产品条款、地区不明确或默认零售可达，不应过度信任结果。
应使用兜底 CTA、回看来源文档，并在更严格约束下重跑。
1. 目标检查
确认未来 30 天核心目标是发行、分销、交易还是分析。
2. 访问检查
先核对投资者类型与地区要求，再把结果视为可执行。
3. 来源检查
使用最新时间戳逐项核验披露页面和权限引用。
该选择器为确定性规则模型，不按联盟分成、投放预算或叙事热度进行排序。
| 维度 | 规则 | 为什么重要 |
|---|---|---|
| Intent routing first | Map query intent to objective (`issue`, `distribute`, `trade`, `monitor`) before scoring vendors. | Prevents incomparable shortlist construction and duplicate-intent page overlap. |
| Public evidence weighting | Score dated dashboard values, regulator references, and disclosure artifacts higher than narrative copy. | Improves reproducibility and reduces hype-driven ranking errors. |
| Regulatory hierarchy check | Separate staff guidance, statute-level thresholds, and entity-directory status before deriving execution confidence. | Prevents treating non-binding or entity-level signals as product-level permissions. |
| Implementation-maturity gate | Check jurisdiction-level implementation progress and cross-border cooperation readiness before assuming route portability. | Reduces regulatory-arbitrage and sequencing risk in multi-jurisdiction rollouts. |
| Custody and resilience gate | Require segregation, reconciliation/assurance, and ICT-resilience evidence before procurement finalization. | Prevents late-stage rework from insolvency-priority and outage-ownership surprises. |
| Boundary labeling | Expose access, eligibility, and liquidity limits in the result panel next to recommendations. | Users can act safely without confusing category signal with investability. |
| Unknowns policy | Mark unavailable comparable fields as `待确认 / no reliable public data` and explain why. | Avoids fabricated precision when public data is incomplete. |
边界态是主动的安全输出，不是失败状态。它用于阻止在约束冲突时形成虚假确定性。
该矩阵把监管/标准引用转为可执行检查项。快照更新于 2026-04-23。
| 概念 | 适用场景 | 不代表 | 行动建议 |
|---|---|---|---|
| U.S. tokenized-securities taxonomy (SEC staff statement) | You compare issuer-sponsored, custodial, or synthetic tokenized structures in U.S. routes. | A staff statement is not a Commission rule, regulation, or safe harbor. | Classify legal structure first; do not assume equivalent rights across wrappers. 来源 S12 |
| MiCA perimeter boundary | You evaluate EU crypto-asset services and want to know whether MiCA is the right starting framework. | If the token qualifies as a financial instrument, MiCA does not govern that instrument path. | Run MiCA-vs-financial-instrument classification before vendor shortlisting. 来源 S17 |
| EU DLT Pilot scaling limits | You plan venue strategy under the EU pilot regime for shares or debt instruments. | Pilot authorization does not remove instrument and aggregate value thresholds. | Track the EUR 500M / EUR 1B / EUR 6B and EUR 9B transition boundaries as issuance grows. 来源 S14 · S15 |
| Travel Rule implementation progress | Your distribution/trading lane relies on cross-border virtual-asset transfers across VASPs. | Legislation coverage does not guarantee uniform enforcement quality or interoperability. | Treat Travel Rule operations as a pre-go-live checklist with counterparty testing. 来源 S13 |
| ATS market-access controls | A route relies on broker-dealer market access to an exchange or ATS in U.S. workflows. | Connectivity does not remove the need for pre-trade controls and sponsored-access guardrails. | Confirm who owns Rule 15c3-5 controls, monitoring, and incident escalation. 来源 S18 |
| FSB 2025 implementation snapshot | You interpret global recommendation sets as if every target jurisdiction has already reached full implementation. | Point-in-time progress snapshots do not imply uniform or complete implementation, especially for stablecoin and cross-border controls. | Add jurisdiction-by-jurisdiction implementation checks before finalizing cross-border rollout assumptions. 来源 S22 · S23 |
| IOSCO custody and operational baseline | A platform claims strong investor protection through custody, wallet handling, and technology-risk controls. | Framework-level recommendations do not prove one provider has implemented segregation, reconciliation, and assurance controls for your instrument. | Request provider-level evidence aligned to recommendation themes 13-17 before selecting execution partners. 来源 S20 · S21 |
| EU DORA operational-resilience boundary | Your route includes EU-regulated entities or critical ICT dependencies in EU-linked operations. | Entity authorization or listing status does not by itself satisfy ongoing ICT governance, incident reporting, testing, and third-party oversight requirements. | Map contractual ownership for ICT incidents, resilience testing cadence, and critical provider dependencies before go-live. 来源 S24 |
| 字段 | 状态 | 未解决原因 |
|---|---|---|
| All-in fee stack comparability | 待确认 / no reliable public matrix | Issuer, broker, venue, and custody fees are disclosed with inconsistent structures and granularity. 来源 S4 · S7 · S9 · S18 |
| Real-time venue depth comparability by security token | 待确认 / no reliable public matrix | Public pages generally do not provide continuously standardized depth/impact datasets across lanes. 来源 S4 · S5 · S6 · S7 · S9 |
| Retail eligibility per instrument across jurisdictions | 待确认 / no reliable unified feed | Eligibility often depends on instrument terms and jurisdiction-specific rules that are published in fragmented formats. 来源 S4 · S8 · S9 · S12 · S17 |
| Provider-level custody segregation and assurance matrix | 待确认 / no reliable public matrix | Public disclosures rarely provide standardized, comparable proof for segregation model, reconciliation frequency, and independent assurance scope. 来源 S3 · S7 · S20 · S21 |
| Cross-platform outage and recovery-performance comparability | 待确认 / no reliable public matrix | No harmonized public dataset was found for incident history, recovery performance, and critical ICT third-party concentration by platform. 来源 S21 · S24 |
每条核心结论都对应至少一个公开来源和一个实际限制条件。
| 论点 | 证据 | 边界 |
|---|---|---|
| Category-first routing is necessary for this keyword | RWA.xyz shows 171 tracked platforms and a distributed-vs-represented split, while Tokeny role mapping confirms that “platform” can mean different operational lanes. | Role segmentation clarifies architecture, not execution certainty or legal access. 来源 S1 · S10 |
| Legal wrapper determines perimeter and rights assumptions | SEC staff statement separates issuer-sponsored, custodial, and synthetic tokenized-security structures, and MiCA summary states financial instruments are outside MiCA scope. | Staff statements are non-binding views; final legal analysis still depends on statute, rules, and instrument facts. 来源 S12 · S17 |
| EU pilot-route choices have hard scaling ceilings | Regulation (EU) 2022/858 sets share/debt and aggregate value limits, and ESMA tracks authorized pilot infrastructures and exemptions. | Pilot authorization does not imply unrestricted scaling for every issuance path. 来源 S14 · S15 · S16 |
| Cross-border transfer readiness remains a live execution risk | FATF reports broad Travel Rule legislative adoption, but implementation depth still requires institution-level controls and testing. | Legislative adoption percentage is not a substitute for operational readiness in specific corridors. 来源 S13 |
| Entity directories improve trust but cannot replace product checks | MAS directory confirms DigiFT entity status and update date, while RMO disclosure and Form CRS language still preserve scope and liquidity caveats. | Entity-level status does not auto-approve every product for every investor class. 来源 S4 · S8 · S9 |
| Implementation maturity is still uneven across jurisdictions | FSB thematic review and joint note report progress but still identify significant gaps and inconsistencies as of 2025-08, with stablecoin controls lagging in multiple jurisdictions. | These are point-in-time implementation snapshots and cannot certify product-level compliance in your exact route. 来源 S22 · S23 |
| Custody and operational controls are now core procurement filters | IOSCO recommendation framework and its 2025 thematic review keep segregation, reconciliation/independent assurance, and operational/technology controls as central investor-protection checks. | Recommendation adoption does not replace provider-level control evidence for the exact instrument and onboarding model. 来源 S20 · S21 |
| EU-linked routes need explicit operational-resilience ownership | DORA applies since 2025-01-17 and requires ICT risk governance, incident reporting, resilience testing, and third-party risk management for in-scope entities. | DORA applicability and obligations still depend on legal role and entity scope mapping. 来源 S24 |
未知可比字段继续标记为 `N/A`，避免用不完整披露面强行拟合决策。
本页负责 tokenization-platform 采购路由；`/best/rwa-platforms` 保持更广口径，邻近页面承接更深层比较。
| 选项 | 最适合 | 不适合 | 反例 / 限制 | 证据强度 | 下一步 |
|---|---|---|---|---|---|
| This `/best/rwa-tokenization-platforms` hybrid page | Implementation-first routing when teams need platform procurement direction with evidence boundaries and fallback actions. | Final venue-only ranking or contract negotiation. | If your instrument structure and jurisdiction are already fixed, this page may be an unnecessary intermediate step. | High for implementation-lane routing, medium for platform-level execution detail. 来源 S1 · S12 · S17 | Use the result CTA to switch to the correct specialized page. |
| RWAMK `/best/rwa-platforms` | Broader category-intent disambiguation when the query is generic and users have not yet decided procurement scope. | Detailed tokenization-platform procurement decisions with migration and control-depth tradeoffs. | Can remain too broad for teams already choosing tokenization-platform vendors. | High for broad category routing, lower for tokenization-platform implementation specifics. 来源 S1 · S10 | Use this page first for tokenization-platform procurement, then use `/best/rwa-platforms` only when broader category expansion is needed. |
| RWAMK `/best/rwa-exchanges` | Users already sure they need secondary market venues and liquidity-aware exchange comparison. | Issuer-stack procurement or analytics-dashboard routing. | Fails early when legal perimeter is still unclear or when issuance controls are the primary blocker. | High for venue-focused decision depth. 来源 S14 · S18 | Open once selector confirms trading rails are primary. |
| RWAMK `/best/rwa-companies` | Company-lane market mapping across analytics, issuance, distribution, and access roles. | Objective-driven platform action when user needs immediate next-step CTA. | Can be too broad for teams that need immediate venue execution checks within one quarter. | High for lane-level market structure. 来源 S1 · S10 | Use when procurement starts from company role instead of platform function. |
| RWAMK `/best/rwa-apps` | Workflow-level app selection across discovery, access, issuance, and verification jobs. | Platform-category strategy with explicit source matrix focus. | Workflow fit can look strong even when legal eligibility and market-access controls are unresolved. | High for app-workflow selection, medium for cross-platform coverage. 来源 S13 · S18 | Use if your team asks “which workflow app do we need first?” |
这里关注的是决策风险：路径错、证据错、预期错、时序错。
| 风险 | 影响 | 概率 | 缓释 |
|---|---|---|---|
| False equivalence risk | High | High | Use category selector first; do not compare issuance stacks and trading venues in one ranking bucket. 来源 S1 · S10 |
| Legal-force confusion risk | High | Medium | Distinguish staff views, statute-level rules, and entity-directory records before treating a route as legally executable. 来源 S12 · S17 |
| Regulatory-perimeter mismatch risk | High | Medium | Classify whether your target instrument sits in MiCA scope and monitor DLT Pilot thresholds if an EU pilot venue is part of the path. 来源 S14 · S15 · S17 |
| Implementation-gap and regulatory-arbitrage risk | High | Medium | Verify jurisdiction-level implementation maturity and cross-border cooperation path before assuming one policy template is portable. 来源 S22 · S23 |
| Liquidity and access-control assumption risk | High | Medium | Treat venue presence as necessary but not sufficient; verify ATS market-access controls and instrument-level liquidity evidence. 来源 S4 · S5 · S6 · S18 |
| Custody commingling and insolvency-waterfall risk | High | Medium | Require explicit segregation model, custody-disclosure package, and reconciliation/independent-assurance evidence before onboarding. 来源 S20 · S21 |
| Operational-resilience and ICT concentration risk | High | Medium | Map ICT governance ownership, incident reporting path, testing cadence, and critical third-party dependencies contractually before launch. 来源 S21 · S24 |
| Cross-border transfer-ops gap risk | Medium | High | Use Travel Rule and AML process checks before launch; do not infer operations readiness from legislation counts alone. 来源 S13 |
| Data-gap risk | Medium | Medium | Keep unknowns explicit (`待确认 / no reliable public data`) and route to scanner or direct source checks for unresolved fields. 来源 S1 · S4 · S7 · S9 · S16 · S18 |
本表强调速度与确定性的取舍及失败条件，而非仅展示理想路径。
| 决策模式 | 收益 | 隐性成本 | 适用条件 | 失败条件 |
|---|---|---|---|---|
| Go directly to secondary-trading venues | Fast route to execution discussions and venue-level onboarding checks. | Can skip instrument-structure and perimeter classification, creating rework risk. | Instrument type, investor class, and jurisdiction boundaries are already confirmed. | Fails when legal wrapper or investor eligibility is still ambiguous. 来源 S12 · S17 · S18 |
| Start with issuance-stack selection | Strong for lifecycle control, transfer restrictions, and compliance-by-design setup. | May delay distribution/venue work if market-access planning is deferred too long. | Issuer-side control and compliance architecture are immediate blockers. | Fails when liquidity route is urgent and issuance controls are already settled. 来源 S3 · S10 · S11 |
| Run perimeter-first regulatory checks | Reduces false confidence and legal rework before vendor negotiation. | Adds early analysis time and may slow short-term shortlist velocity. | Cross-jurisdiction strategy or mixed instrument structures are in scope. | Fails when teams confuse non-binding guidance with executable permissions. 来源 S12 · S14 · S15 · S17 |
| Keep analytics-first monitor mode | Low-regret way to benchmark market structure while clarifying constraints. | Execution can stall if monitor mode is not converted to dated action checkpoints. | Objective or eligibility constraints are still evolving. | Fails if teams treat discovery dashboards as direct investability signals. 来源 S1 · S2 · S16 |
| Accelerate shortlist without custody-control evidence | Speeds early vendor conversations and reduces initial research overhead. | Can create expensive legal and operational rework when segregation or assurance controls fail diligence later. | Only when engagement is strictly exploratory and no onboarding decision is imminent. | Fails when client-asset protection responsibilities are unclear across issuer, custodian, and venue layers. 来源 S20 · S21 |
| Treat EU authorization as complete operational readiness | Simplifies planning by assuming resilience obligations are already embedded. | Can miss ICT incident ownership and third-party concentration duties that still need explicit control design. | Only when compliance and engineering teams already mapped DORA scope and contractual controls. | Fails when critical ICT provider dependencies are undocumented or operational testing is not evidenced. 来源 S24 |
提供真实语境示例，包含前提、工具输出与可执行下一步。
前提： Needs issuance controls first, can accept institutional-only distribution at first phase.
输出： Tool typically routes to issuance with Securitize/Tokeny high in shortlist, then pushes distribution checks as second step.
动作： Open `/best/rwa-companies` for lane-depth and `/scanner` for disclosure completeness before selecting providers.
前提： Primary concern is tradability and permissions, not issuer-stack tooling.
输出： Tool routes to secondary/distribution and elevates Archax or DigiFT depending on geography and access constraints.
动作： Move to `/best/rwa-exchanges` for venue-level comparison after routing is confirmed.
前提： Needs broad public numbers and category concentration context, no immediate onboarding intent.
输出： Tool routes to analytics-first path (RWA.xyz + RWAMK Scanner fallback).
动作： Use `/projects` to inspect representative listings and evidence patterns after category benchmarking.
前提： Unknown investor class, unknown jurisdiction, expectation of immediate access.
输出： Tool often returns boundary or monitor status and asks for clearer eligibility inputs.
动作： Use fallback CTA and source-check rows before treating any platform as universally accessible.
前提： Needs launch speed but depends on third-party ICT services and multi-jurisdiction onboarding.
输出： Tool may route to issuance/distribution, but confidence should remain monitor until custody evidence and DORA ownership checks are complete.
动作： Add segregation/reconciliation proof and ICT incident/testing ownership to procurement gates before contract signature.
用户看到工具结果后最常出现的决策问题。
本页使用的公开来源及其上下文说明。任何标记为 `待确认 / no reliable public data` 的条目截至 2026-04-23 仍刻意保持未决。
| ID | 来源 | 使用说明 |
|---|---|---|
| S1 | RWA.xyz tokenization platforms dashboard | Used for tracked platform count and split metrics (distributed asset value $15.23B, represented asset value $332.13B, holders 732,344, total platforms 171). Snapshot checked on 2026-04-23. |
| S2 | RWA.xyz tokenized U.S. Treasuries dashboard | Used for treasury concentration context when testing category-overlap assumptions. Snapshot checked on 2026-04-23. |
| S3 | Securitize disclosure library | Used for investor-facing disclosure/document access surface. Snapshot checked on 2026-04-23. |
| S4 | FINRA Form CRS for Securitize Markets, LLC | Used for broker-dealer/ATS scope limits, liquidity and eligibility caveats, and fee disclosure framing. Document updated 2023-11-08, checked on 2026-04-23. |
| S5 | Archax regulated exchange page | Used for exchange/broker/custodian role and institutional trading posture. Snapshot checked on 2026-04-23. |
| S6 | Archax regulatory permissions page | Used for FRN 838656 and liquidity-risk disclosure references. Snapshot checked on 2026-04-23. |
| S7 | DigiFT invest page | Used as product-layer route reference; quantitative comparability remains limited due non-standardized disclosure format. Snapshot checked on 2026-04-23. |
| S8 | MAS Financial Institutions Directory for DigiFT | Used to verify Capital Markets Services Licensee + Recognised Market Operator status for DigiFT. Page last updated 2026-03-05; checked on 2026-04-23. |
| S9 | DigiFT RMO regulatory disclosure PDF | Used for scope boundaries around organised-market recognition. Snapshot checked on 2026-04-23. |
| S10 | Tokeny RWA tokenization ecosystem map | Used for platform-role segmentation (issuer stack, distribution, custody, data, transfer rails). The visible map asset is dated September 2025; checked on 2026-04-23. |
| S11 | ERC-3643 identity registry documentation | Used for issuer-side transfer controls and identity-gated compliance logic. Snapshot checked on 2026-04-23. |
| S12 | SEC staff statement on tokenized securities | Used for U.S. structure taxonomy (issuer-sponsored vs third-party custodial/synthetic tokenized securities). Statement date 2026-01-28; staff views are not Commission rules. |
| S13 | FATF sixth targeted update on VA/VASP implementation | Used for cross-border AML transfer context: 99 jurisdictions passed or are passing Travel Rule legislation, and materially important jurisdictions represent ~98% of global VA market. Publication date 2025-06-26. |
| S14 | Regulation (EU) 2022/858 (DLT Pilot Regime) | Used for hard thresholds in Article 3: shares under EUR 500M issuer cap, debt under EUR 1B issuance size, aggregate DLT instrument value cap at EUR 6B, and transition trigger at EUR 9B. |
| S15 | ESMA DLT Pilot Regime page | Used for start date (2023-03-23), in-scope instrument summary, and ESMA publication obligations for authorised infrastructures and exemptions. |
| S16 | ESMA list of authorised DLT market infrastructures | Used for evidence that multiple named infrastructures are already authorised under the pilot (e.g., CSD Prague, 21X, 360X, Axiology, LISE, Securitize Europe) with dated permission start points. |
| S17 | EU MiCA summary (Regulation (EU) 2023/1114) | Used for scope and timing boundaries: MiCA applies from 2024-12-30 (Titles III/IV from 2024-06-30), and does not apply to crypto-assets covered by other EU financial-services acts (including qualifying financial instruments). |
| S18 | FINRA market access topic (SEC Rule 15c3-5 context) | Used for U.S. market-access control boundary: broker-dealers providing exchange/ATS access must maintain pre-trade risk controls; unfiltered/naked sponsored access is effectively prohibited. |
| S20 | IOSCO FR11/2023 final report on crypto and digital asset markets | Used for baseline policy architecture: 18 recommendations across six key risk areas, including custody segregation, independent assurance, and operational/technology risk controls. Publication date 2023-11-16; checked on 2026-04-23. |
| S21 | IOSCO FR13/2025 thematic implementation review | Used for implementation-maturity evidence across 20 jurisdictions and recommendation-level progress counts (for example, custody recommendations 13 and 15 each reporting 14 jurisdictions with final measures in force). Publication date 2025-10-16; checked on 2026-04-23. |
| S22 | FSB thematic review on crypto-asset framework implementation | Used for point-in-time implementation findings (progress plus significant gaps/inconsistencies as of 2025-08) and the note that eight recommendations were issued to improve implementation consistency. Publication date 2025-10-16; checked on 2026-04-23. |
| S23 | FSB-IOSCO joint information note on implementation progress | Used for cross-report scope counts: complementary reviews span over 40 jurisdictions, including FSB progress review across 37 jurisdictions and IOSCO review across 20 jurisdictions. Publication date 2025-10-16; checked on 2026-04-23. |
| S24 | EU DORA summary (Regulation (EU) 2022/2554) | Used for operational-resilience control boundaries: regulation applies since 2025-01-17 and covers ICT risk governance, major-incident reporting, resilience testing, and third-party risk management in scope entities. |
| S19 | RWAMK scanner route and disclosure-check workflow | Used to disclose the internal fallback path referenced by tool outputs. Checked on 2026-04-23 for route availability and intended use (informational routing, not advice). |
保持流程连续：先路由，再核验，再比较，最后执行。