> 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/user-journeys.md).
# User Journeys
All three user journeys are chain-aware. The platform UI is unified, but the underlying blockchain interactions happen on whichever chain the property is listed on.
### User Journey - Property Owner
Diagram : User Journey - Property Owner
| Step | Actor | Action / Description |
| ---- | ----------------- | ------------------------------------------------------------ |
| 01 | Property Owner | Registers and completes KYC via Sumsub |
| 02 | Property Owner | Uploads government certificate, title deed, valuation report |
| 03 | Property Owner | Pays listing fee |
| 04 | Admin | Reviews and approves property submission |
| 05 | System | Docs stored on AWS S3; hash ready for on-chain anchoring |
| 06 | Property Owner | Selects Canton EVM or Cardano as their preferred chain |
| 07 | System | Deploys chain-specific token contract (ERC-3643 or CNT) |
| 08 | Platform | Token sale goes live on the chosen chain's primary market |
| 09 | System | Monitors sale - escrow releases on goal met |
| 10 | Property Owner | Receives funds from escrow (in chain-appropriate currency) |
| 11 | Property Owner | Provides rental income to platform for yield distribution |
| 12 | Yield Distributor | Distributes yield to token holders on the same chain |
### User Journey - Retail Investor
Diagram 4: User Journey - Retail Investor
| Step | Actor | Action / Description |
| ---- | ----------------- | ------------------------------------------------------------------------------ |
| 01 | Investor | Registers on platform; links EVM wallet (Canton) and/or Cardano wallet |
| 02 | Investor | Completes KYC via Sumsub; AML screening performed |
| 03 | System | KYC approved; investor added to Canton and/or Cardano whitelist as appropriate |
| 04 | Investor | Browses properties - can filter by chain, location, yield, price |
| 05 | Investor | Selects a property (sees which chain it is on: Canton EVM or Cardano) |
| 06 | Investor | Reviews certificate, valuation, token price, yield history |
| 07 | Investor | Selects token quantity; proceeds to checkout |
| 08 | Payment | Canton: pays USDC/USDT/ETH/Fiat \| Cardano: pays ADA/Fiat |
| 09 | Escrow | Funds held in chain-specific escrow until goal is met |
| 10 | System | Tokens released to investor's appropriate chain wallet |
| 11 | Investor | Views portfolio - can hold Canton and Cardano tokens simultaneously |
| 12 | Yield Distributor | Receives yield on each chain separately based on holdings |
| 13 | Investor | To exit: lists tokens on same-chain secondary marketplace only |
### User Journey - Secondary Market Trader
All secondary market activity is chain-isolated. Canton tokens trade only on the Canton marketplace; Cardano tokens trade only on the Cardano marketplace.
Diagram 5: Secondary Marketplace Flow
| Step | Actor | Action / Description |
| ---- | ----------------- | ------------------------------------------------------------------- |
| 01 | Seller | Navigates to portfolio; selects tokens to list for sale |
| 02 | System | Identifies which chain the tokens are on (Canton EVM or Cardano) |
| 03 | Seller | Listing created on the appropriate chain's marketplace |
| 04 | Smart Contract | Tokens locked in chain-specific escrow - seller cannot double-spend |
| 05 | Platform | Listing visible only to KYC-verified buyers on the same chain |
| 06 | Buyer | Discovers listing on their chain's marketplace |
| 07 | System | Validates buyer's KYC status on the same-chain whitelist |
| 08 | Compliance Module | Checks transfer rules (jurisdiction, holding period, investor caps) |
| 09 | Smart Contract | Atomic swap executed on-chain: tokens to buyer, funds to seller |
| 10 | System | Platform transaction fee deducted from seller proceeds |
| 11 | System | Trade recorded on-chain; both parties notified |
---
# 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/user-journeys.md?ask=&goal=
```
`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.