> 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/smart-contract-architecture.md).

# Smart Contract Architecture

The smart contract architecture is entirely duplicated across both chains. Each chain has its own complete set of contracts with no interaction between them. The table below compares the equivalent contracts on each chain.

<br>

![](/files/SiHJkoTn86r1hxq7EkxC)

\
&#x20;Contract Comparison: Canton EVM vs Cardano

| Canton EVM                 | Cardano                          |
| -------------------------- | -------------------------------- |
| ERC-3643 Token Contract    | CNT Token Contract               |
| Property Registry Contract | Property Registry (Cardano)      |
| Compliance Module          | Compliance Module (UTXO model)   |
| KYC Registry (Whitelist)   | KYC Whitelist (Cardano On-chain) |
| Primary Sale Escrow        | Primary Sale Escrow (ADA)        |
| Marketplace Contract       | Marketplace Contract (Cardano)   |
| Yield Distributor Contract | Yield Distributor (ADA)          |
| Access Control Module      | Access Control (Cardano)         |
| Price Oracle               | Price Oracle (Cardano)           |
| Fiat + Stablecoin Gateway  | ADA + Fiat Gateway               |

<br>

### Key Contract Interactions (Per Chain)

These interactions apply identically on both chains (using chain-appropriate mechanisms):

* Frontend calls Property Registry to initiate tokenization after chain is selected
* Property Registry triggers Token Contract deployment (ERC-3643 on Canton; CNT on Cardano)
* Token Contract checks Compliance Module on every transfer attempt
* Compliance Module queries KYC Registry/Whitelist to validate both parties
* Marketplace Contract locks tokens in Escrow during secondary market trade
* Atomic swap releases tokens to buyer and funds to seller simultaneously
* Yield Distributor queries Token Contract for current holder balances before each distribution

<br>

| <p>No Cross-Chain Interactions</p><p>No contract on Canton EVM calls any contract on Cardano, and vice versa. The backend routes requests to the correct chain based on which chain a property is listed on. There are no bridge contracts, relay services, or shared state between the two chains.</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/smart-contract-architecture.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.