> 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/abstract.md).

# Abstract

When a real asset enters a digital capital network, it must cross six boundaries at once: fact, rights, regulation, accounts, technology, and operations. A failure at any one of them lets an on-chain token drift away from real rights, research systems drift away from execution systems, rule decisions drift away from signing actions, and settlement results drift away from lifecycle records. SimpleChain frames the task as building a verifiable capital object: a referencable Asset ID, a nine-dimensional Asset State, state evidence, applicable policies, authorization boundaries, lifecycle events, and settlement receipts. Off-chain authorities confirm facts and rights; the on-chain ledger organizes the sources, proofs, state changes, and chains of responsibility into machine-readable records that cannot be silently rewritten.

The core loop of SimpleChain is Evidence → Proof → State → Policy → Authorization → Execution → Settlement → Audit → New State. Every material capital action can answer: what evidence it relied on, which policy version applied, who authorized it, what state it changed, which account or settlement rail carried it, which receipt proves the result, and how a dispute or revocation produces the next version. Five native components implement the loop: TDS (Trusted Data Space) for evidence, TASM (Trusted Asset State Machine) for state, CaaS and SLC for rules and contracts, PCT (Proof-Carrying Transaction) for execution, and SettlementReceipt for receipts.

SimpleChain forms a three-layer stack with DataIPO and AICOS, all sharing one asset state machine. DataIPO is the capital formation network: asset onboarding, issuance, allocation, and institutional coordination. AICOS is the AI Capital OS: data orchestration, due diligence, pricing, rule checks, and post-investment monitoring; it turns RWA into AWA. SimpleChain sits underneath as the place where proof and settlement run. The network uses PoSA rotating block production, shortens finality with optimistic single-round confirmation, decouples consensus from execution with a parallel execution layer, stays EVM-compatible, and separates the powers of validators, institutional nodes, and regulatory nodes.

Chapters 1 to 3 give the thesis, the asset class, and the positioning. Chapter 4 gives the network architecture. Chapters 5 to 9 give the five core protocol components. Chapters 10 to 14 cover security and governance, ecosystem roles, the regulatory map, network economics, and risk. Field-level object specifications appear in Appendix B and will also be released as the SimpleChain Protocol Specification.


---

# 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/abstract.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.