> For the complete documentation index, see [llms.txt](https://docs.matrix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.matrix.io/hong-kong-stablecoin-25-26/real-world-asset/reports/matrix-ai-network-driving-hong-kongs-stablecoin-infrastructure-and-real-world-asset-tokenization/chapter-2-permissioned-vs.-public-chains-in-rwa/2.1-roles-and-use-cases-of-two-chain-architectures-in-rwa-projects.md).

# 2.1 Roles and Use Cases of Two Chain Architectures in RWA Projects

In Real-World Asset (RWA) tokenization projects, blockchain plays a pivotal role in digitalizing asset rights and establishing a programmable financial framework. However, due to varying regulatory environments and asset types, permissioned chains and public chains fulfill different roles. A clear understanding of both is essential when designing a legally sound and scalable RWA structure.

#### 1) Permissioned Chains

Permissioned (or consortium) chains are widely adopted for the on-chain anchoring of Chinese onshore assets, especially where business or financial data cannot be publicly disclosed. For instance:

In collaboration with AntChain, solar energy production data is securely logged to confirm yield entitlement;

Other examples include Spark Chain and enterprise-built permissioned chains, used to confirm business profits, receivables, or franchise rights.

**Advantages:**

* Confidential data is protected and access-controlled;
* Regulator-friendly architecture for compliant data anchoring;
* Enables institutional-grade onboarding of sensitive operational records.

**Limitations:**

* High operational costs, often exceeding RMB 4 million for initial setup;
* Lack of openness — only consortium members can access core data;
* Not suitable for token issuance — it enables anchoring, not asset issuance or

  open trading.

#### 2) Public Chains

Public chains serve as the issuance layer and market infrastructure for RWA tokens. In jurisdictions like the United States, Hong Kong, and Singapore, major RWA offerings are executed directly on Ethereum, Polygon, or similar networks:

* BlackRock issues tokenized U.S. Treasuries on Ethereum via a Singapore- regulated structure;
* In Hong Kong, SPVs are commonly used to issue RWA tokens on public chains, linked to onshore data via audit and cross-chain mechanisms.

**Advantages:**

* Globally accessible — no permission required;
* Smart contracts enable programmable yield distribution, automated

  settlement, and decentralized governance;
* Integrated with DeFi ecosystems for improved secondary market liquidity.

**Challenges:**

* High gas fees and slower settlement times (especially on Ethereum mainnet);
* Tokenization requires reliable off-chain data sources and strong KYC

  mechanisms.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.matrix.io/hong-kong-stablecoin-25-26/real-world-asset/reports/matrix-ai-network-driving-hong-kongs-stablecoin-infrastructure-and-real-world-asset-tokenization/chapter-2-permissioned-vs.-public-chains-in-rwa/2.1-roles-and-use-cases-of-two-chain-architectures-in-rwa-projects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.