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

# Tokenization Flow

The tokenization flow begins with shared steps common to both chains, then forks at the point where the property owner selects their preferred blockchain. From that point, all steps are chain-specific.

\
![](/files/KBjE66acNI59gRpUIoSx)

### Shared Steps (Both Chains)

| Step | Actor          | Action / Description                                                               |
| ---- | -------------- | ---------------------------------------------------------------------------------- |
| 01   | Property Owner | Registers on platform and completes KYC verification via Sumsub                    |
| 02   | Property Owner | Submits property listing with government certificate, title deed, valuation report |
| 03   | Admin          | Reviews submitted documents for completeness and legal validity                    |
| 04   | System         | Documents encrypted and stored on AWS S3; SHA-256 hash ready for on-chain storage  |
| 05   | Legal / Admin  | SPV (Special Purpose Vehicle) or legal wrapper created for the property            |
| 06   | Property Owner | Selects which blockchain to tokenize on: Canton EVM or Cardano                     |

<br>

### Canton EVM Path

| Step | Actor             | Action / Description                                                         |
| ---- | ----------------- | ---------------------------------------------------------------------------- |
| 07   | Smart Contract    | SHA-256 hash stored on Canton EVM Property Registry                          |
| 08   | Smart Contract    | ERC-3643 Token Contract deployed on Canton EVM                               |
| 09   | Smart Contract    | Tokens minted (e.g. 1,000,000 tokens = 100% ownership)                       |
| 10   | Compliance Module | Transfer rules configured: jurisdiction, holding period, investor caps       |
| 11   | KYC Registry      | Approved Canton investors added to on-chain whitelist                        |
| 12   | Platform          | Token sale goes live on Canton primary market                                |
| 13   | Investor          | Pays via USDC, USDT, ETH, or Fiat (bank/card)                                |
| 14   | Escrow Contract   | Funds held in Canton escrow until funding goal is reached                    |
| 15   | Smart Contract    | On goal met: escrow releases to owner. On failure: investors refunded        |
| 16   | Yield Distributor | Rental income collected and distributed in USDC/USDT to Canton token holders |

<br>

### Cardano Path

| Step | Actor             | Action / Description                                                    |
| ---- | ----------------- | ----------------------------------------------------------------------- |
| 07   | Smart Contract    | SHA-256 hash stored on Cardano Property Registry                        |
| 08   | Smart Contract    | CNT (Cardano Native Token) contract deployed on Cardano                 |
| 09   | Smart Contract    | Tokens minted as Cardano native assets                                  |
| 10   | Compliance Module | On-chain transfer rules configured for Cardano UTXO model               |
| 11   | KYC Whitelist     | Approved Cardano investors added to on-chain whitelist                  |
| 12   | Platform          | Token sale goes live on Cardano primary market                          |
| 13   | Investor          | Pays via ADA or Fiat (bank transfer)                                    |
| 14   | Escrow Contract   | Funds held in Cardano escrow until funding goal is reached              |
| 15   | Smart Contract    | On goal met: escrow releases to owner. On failure: investors refunded   |
| 16   | Yield Distributor | Rental income collected and distributed in ADA to Cardano token holders |

<br>

| <p>Funding Model</p><p>If the funding goal is not met by the deadline, the escrow contract on whichever chain was chosen automatically refunds all investors. This is handled atomically by the smart contract with no manual intervention.</p> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |


---

# 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/tokenization-flow.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.