> For the complete documentation index, see [llms.txt](https://dataipo.gitbook.io/dataipo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dataipo.gitbook.io/dataipo-docs/whitepaper-center/simplechain-whitepaper/appendix-e-references.md).

# Appendix E — References

Regulation and policy

\[R-SEC-01] U.S. Securities and Exchange Commission. Regulation Crypto Assets. Release Nos. 33-11434; 34-106150; File No. S7-2026-27; RIN 3235-AN38. ACTION: Proposed rule. <https://www.sec.gov/files/rules/proposed/2026/33-11434.pdf>

\[R-SEC-02] U.S. Securities and Exchange Commission. Regulation D (Rules 500–508), Regulation S (Rules 901–905), Regulation A (Rules 251–263), 17 CFR Part 230.

\[R-US-03] U.S. Congress. Guiding and Establishing National Innovation for U.S. Stablecoins Act (GENIUS Act); Digital Asset Market Clarity Act (CLARITY Act), 2025.

\[R-HK-04] Hong Kong Legislative Council. Stablecoins Ordinance, 2025. Hong Kong Monetary Authority, Project Ensemble sandbox documentation.

\[R-HK-05] Securities and Futures Commission (Hong Kong). Circulars on intermediaries engaging in tokenised securities-related activities, and on virtual asset trading platforms.

\[R-SG-06] Monetary Authority of Singapore. Project Guardian: Enabling Open and Interoperable Networks, and associated industry frameworks.

\[R-EU-07] European Parliament and Council. Regulation (EU) 2023/1114 on Markets in Crypto-Assets (MiCA); Regulation (EU) 2022/858 on a pilot regime for market infrastructures based on distributed ledger technology (DLT Pilot Regime).

\[R-FATF-08] Financial Action Task Force. Updated Guidance for a Risk-Based Approach to Virtual Assets and Virtual Asset Service Providers.

Technical standards

\[T-01] BNB Chain. BEP-126: Introduce Fast Finality Mechanism; BEP-131 / Parlia (PoSA) consensus specification.

\[T-02] Martin, J.-P., Alvisi, L. Fast Byzantine Consensus. IEEE TDSC 2006 (quorum bounds for single-round commit).

\[T-03] Gelashvili, R., Spiegelman, A., et al. Block-STM: Scaling Blockchain Execution by Turbo-Charging Parallelism. Aptos Labs, 2022.

\[T-04] Monad Labs. Monad Documentation: Deferred Execution, Parallel Execution, MonadDB, RaptorCast.

\[T-05] Solana Labs. Turbine: Block Propagation Protocol; Ethereum Foundation, Ethereum roadmap: delayed execution (EIP-7886).

\[T-06] Boneh, D., Lynn, B., Shacham, H. Short Signatures from the Weil Pairing; BLS signature aggregation, IETF draft-irtf-cfrg-bls-signature.

\[T-07] Gabizon, A., Williamson, Z. J., Ciobotaru, O. PLONK: Permutations over Lagrange-bases for Oecumenical Noninteractive arguments of Knowledge. 2019.

\[T-08] ERC-3643: T-REX Token for Regulated Exchanges (permissioned token standard). Ethereum Improvement Proposals.

\[T-09] EIP-712: Typed structured data hashing and signing. Ethereum Improvement Proposals.

\[T-10] ERC-7540: Asynchronous ERC-4626 Tokenized Vaults. Ethereum Improvement Proposals.

\[T-11] ISO 24165: Digital Token Identifier (DTI). International Organization for Standardization.

\[T-12] ISO/IEC 27001: Information security management systems. International Organization for Standardization.

\[T-13] W3C. Verifiable Credentials Data Model v2.0; Decentralized Identifiers (DIDs) v1.0.

\[T-14] Coinbase / Linux Foundation. x402: An open standard for internet-native payments.

\[T-15] State Cryptography Administration of China. GM/T 0002-2012 (SM4 block cipher); GM/T 0003-2012 (SM2 elliptic-curve cryptography).

\[T-16] People's Bank of China. JR/T 0197-2020, Financial data security: Guidelines for data security classification.

Market and research

\[M-01] rwa.xyz. Real-World Asset Tokenization Analytics (on-chain RWA excluding stablecoins), 2023–2026 time series, retrieved August 2026.

\[M-02] Boston Consulting Group & ADDX. Relevance of On-Chain Asset Tokenization in "Crypto Winter", 2022 ($16 trillion tokenized-asset projection for the 2030s).

\[M-03] McKinsey & Company. From ripples to waves: The transformational power of tokenizing assets, 2024.

\[M-04] RedStone. RWA Tokenization Report, 2025.

\[M-05] Chainalysis. Crypto Adoption Index and RWA market commentary, 2024–2025.

Project documents

\[P-01] SimpleChain Foundation. SimpleChain 2.0 Whitepaper v2.1 (historical version, reference only: earlier consensus direction, multi-L2 subchains, enterprise node network, economic model).

\[P-02] SimpleChain Foundation. SRW Tokenomics 2.0 (published separately: supply, allocation, unlocks, buyback and burn, stress tests).

\[P-03] SimpleChain Foundation. SimpleChain Protocol Specification v1.0 (planned: the field-level, machine-readable edition of the Appendix B object specifications).

\[P-04] DataIPO. TDS Trusted Data Space product introduction; TVA calculation standard; AI assessment metric calculation standard.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dataipo.gitbook.io/dataipo-docs/whitepaper-center/simplechain-whitepaper/appendix-e-references.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.