> 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/system-architecture.md).
# System Architecture
The system has three shared layers (Frontend, Backend, Storage/External) and two independent blockchain stacks. There is no bridge or cross-chain interaction between Canton EVM and Cardano.
### Shared Layers
| Layer | Component | Technology / Notes |
| -------- | -------------------- | ------------------------------------------------------------------------------------- |
| Frontend | Web Application | React.js - single UI for both Canton and Cardano property listings |
| Frontend | Mobile Application | React Native - iOS and Android, full feature parity |
| Frontend | Admin Dashboard | Internal portal for KYC review, property approval across both chains |
| Backend | API Gateway | Central entry - routes requests to chain-appropriate services |
| Backend | Auth Service | User registration, login, wallet linking (supports both EVM and Cardano wallets) |
| Backend | KYC Service | Orchestrates Sumsub; pushes approved status to both chain whitelists |
| Backend | Property Service | Listing CRUD, document upload, chain selection routing |
| Backend | Payment Service | Multi-rail - fiat gateway (both chains), stablecoin (Canton only), ADA (Cardano only) |
| Backend | Notification Service | Email, SMS, push for all platform events across both chains |
| Storage | AWS S3 (Encrypted) | Government certs, title deeds, KYC docs - AES-256 encrypted |
| Storage | PostgreSQL | App data - users, properties, transactions, balances for both chains |
| External | Sumsub | Identity verification, AML screening, accredited investor check (USA) |
| External | Price Oracle | Property valuations and token price feeds for both marketplaces |
### Canton EVM Stack
| Layer | Component | Technology / Notes |
| ---------- | ----------------------- | ----------------------------------------------------------- |
| Canton EVM | ERC-3643 Token Contract | Security token with built-in compliance hooks |
| Canton EVM | Property Registry | Property metadata and S3 document hash stored on Canton |
| Canton EVM | Compliance Module | ERC-3643 transfer rules - jurisdiction, KYC, holding period |
| Canton EVM | KYC Registry | On-chain whitelist of KYC-approved investor addresses |
| Canton EVM | Primary Sale Escrow | Holds investor funds; releases on goal met or refunds |
| Canton EVM | Marketplace Contract | Canton-only secondary market - order book, atomic swap |
| Canton EVM | Yield Distributor | Distributes rental income proportionally to token holders |
| Canton EVM | Access Control | Role-based admin functions - mint, pause, update rules |
| Canton EVM | Payments | USDC, USDT, ETH on-chain + fiat gateway integration |
### Cardano Stack
| Layer | Component | Technology / Notes |
| ------- | -------------------- | ------------------------------------------------------------------ |
| Cardano | CNT Token Contract | Cardano Native Token representing fractional property ownership |
| Cardano | Property Registry | Property metadata and S3 document hash stored on Cardano |
| Cardano | Compliance Module | On-chain transfer rules specific to Cardano's UTXO model |
| Cardano | KYC Whitelist | On-chain whitelist of approved investor addresses (Cardano format) |
| Cardano | Primary Sale Escrow | ADA-based escrow; releases on goal met or refunds |
| Cardano | Marketplace Contract | Cardano-only secondary market - separate from Canton marketplace |
| Cardano | Yield Distributor | Distributes rental income in ADA proportionally |
| Cardano | Access Control | Admin functions for Cardano contracts |
| Cardano | Payments | ADA on-chain + fiat gateway integration |
| No Bridge Between Chains
Canton EVM tokens cannot be traded on the Cardano marketplace and vice versa. There is no cross-chain token transfer mechanism. This is an intentional design decision - each chain is a fully self-contained ecosystem on the platform.
|
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
---
# 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/system-architecture.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.