# 8. Compliance and Transparency

## 8.1 Structural Duality

To ensure stability, the CHREMA ecosystem is designed with a structural separation between its RWA asset (GOLDX) and its utility token (CHREMA).

<table><thead><tr><th width="158">Item</th><th width="264">GOLDX</th><th>CHREMA</th></tr></thead><tbody><tr><td>Type</td><td>Real-World Asset token backed by physical gold</td><td>Blockchain utility and reward token</td></tr><tr><td>Regulatory Risk Potential</td><td>Asset-backed security (potential)</td><td>General utility token(non-security)</td></tr><tr><td>Regulatory Mitigation Strategy</td><td>Utilization of domestic and international gold association registrations and custodial trusts</td><td>Transition to DAO structure and decentralized ecosystem governance</td></tr></tbody></table>

***

## 8.2 External Audit and Physical Asset Verification System

**Regular Financial Audits**

* A third-party accounting firm conducts monthly audits to verify that physical gold reserves reconcile with GOLDX circulation under the 0.1g peg (circulating supply × 0.1g).
* Audit reports are transparently disclosed through the platform, GitBook, IPFS, and other public channels.

**Verification of Physical Gold Storage**

* The physical gold is securely stored in third-party vaults under certified gold associations or trust agreements.
* The condition and presence of the stored gold are regularly verified by accredited appraisal institutions.

**Submitted Documents and Supporting Evidence**

* Mining license and mine registration certificate
* Goldmine revenue and distribution contracts
* Shareholder registry and corporate registration certificate
* Proof of gold custody (certificates, photos, appraisal reports, etc.)

***

## 8.3 On-chain Audit and Transparency

* GOLDX issuance, burning records, holdings, and circulation → **publicly accessible in real-time on the blockchain**
* CHREMA distribution records and DAO governance voting → **automatically recorded within smart contracts**
* Summary reports of audits and appraisals are planned to be linked with IPFS or integrated with on-chain verification mechanisms


---

# Agent Instructions: 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:

```
GET https://doc.chrema.net/8.-compliance-and-transparency.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.