> For the complete documentation index, see [llms.txt](https://maxtronize.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://maxtronize.gitbook.io/docs/executive-summary.md).

# Executive Summary

This document provides the complete architecture, system design, and user journey documentation for the RWA (Real World Asset) Tokenization Platform. The platform enables real estate owners to tokenize their properties and allows retail investors to purchase fractional ownership via security tokens. A secondary marketplace provides liquidity for token holders.

<br>

| <p>Dual-Chain Architecture Principle</p><p>The platform runs Canton EVM and Cardano as two completely independent blockchain stacks with no bridge between them. A property owner selects which chain to list on at the time of tokenization. All subsequent activity for that property - primary sale, secondary trading, and yield distribution - happens exclusively on the chosen chain. Canton users and Cardano users operate in separate ecosystems within the same platform UI.</p> |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

<br>

### Platform Overview

The platform operates across three core functions on each chain:

* Primary Market - Property owners list and tokenize real estate; investors purchase fractional tokens on their chosen chain
* Secondary Market - Token holders trade within their chain's marketplace (Canton users with Canton users; Cardano users with Cardano users)
* Yield Distribution - Rental income is distributed automatically to token holders via the same chain's smart contracts

<br>

### Key Technology Decisions

| Layer      | Component             | Technology / Notes                                                       |
| ---------- | --------------------- | ------------------------------------------------------------------------ |
| Canton EVM | ERC-3643 Token        | Security token with compliance module, whitelist, transfer restrictions  |
| Canton EVM | Primary Sale + Escrow | Funding escrow, investor whitelist, token release on goal met            |
| Canton EVM | Secondary Marketplace | Canton-only order book, atomic swap, fee deduction                       |
| Canton EVM | Yield Distributor     | Distributes rental income in USDC/USDT/ETH proportionally                |
| Canton EVM | Payments              | USDC, USDT, ETH, Fiat (bank transfer, credit/debit card)                 |
| Cardano    | CNT Token             | Cardano Native Token with on-chain compliance rules                      |
| Cardano    | Primary Sale + Escrow | ADA-based escrow, on-chain whitelist, token release                      |
| Cardano    | Secondary Marketplace | Cardano-only order book, atomic swap, fee deduction                      |
| Cardano    | Yield Distributor     | Distributes rental income in ADA/Fiat proportionally                     |
| Cardano    | Payments              | ADA, Fiat (bank transfer)                                                |
| Shared     | KYC Provider          | Sumsub - covers India, UAE, USA; results pushed to both chain whitelists |
| Shared     | Document Storage      | AWS S3 (encrypted) + on-chain hash on the owner's chosen chain           |
| Shared     | Backend               | API Gateway, Auth, Property, KYC, Payment, Notification services         |

<br>


---

# 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://maxtronize.gitbook.io/docs/executive-summary.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.