> 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/simplechain-in-60-seconds.md).

# SimpleChain in 60 Seconds

What it is. SimpleChain is a Layer 1 blockchain built for real-world assets. On a general-purpose chain, the first-class object is an account balance. On SimpleChain, the first-class object is an asset state that carries its own evidence: nine dimensions of one asset, covering identity, evidence, rights, compliance, operations, cashflow, risk, settlement, and lifecycle, all versioned, signed, disputable, and updated as the business runs.

What it solves. On-chain RWA grew from $6 billion to $31 billion in four years, yet the stock sits overwhelmingly in treasuries and funds. The first generation of RWA moved financial products onto a new carrier; the assets themselves did not change. Industrial assets stay out because the evidence fails: self-reported PDFs cannot be recomputed, compliance stops at the document level, disclosure ends on issuance day, and secondary markets have nothing to price. Tokenization itself matured long ago. SimpleChain closes those four gaps: evidence goes on-chain in recomputable form, rules become versioned policies checked before execution, every transaction carries its own compliance proof, and settlement receipts write back into the asset state.

Why this design. We defined AWA (AI World Assets) as an asset class: assets produced by AI-native businesses, metered continuously by machines, and readable, priceable, financeable, and manageable by humans and agents together. In the architecture, evidence, state, policy, authorization, execution, and receipts are native objects of the chain, checked in stages by the consensus and execution layers; a transaction that fails these checks either never enters a block or never changes asset state. Asset state is a nine-dimensional versioned vector. Agents hold provable, revocable, limited authorizations at the protocol layer.

How to take part. Chapter 11 and Chapter 13 describe the entry points for validators and institutional nodes, attestation and oracle nodes, developers (API/SDK), asset originators, investors, and agents. Token economics is published separately in the SRW Tokenomics document; Chapter 13 of this paper gives only a network-economy overview.

> **One-sentence claim**
>
> Capital activity moves from "trusting the result a platform shows" to "verifying the evidence, rules, authorization, execution, and settlement behind the result." SimpleChain is the native execution environment for that semantics.


---

# 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/simplechain-in-60-seconds.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.