> For the complete documentation index, see [llms.txt](https://crezanetwork.gitbook.io/crezanetwork-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crezanetwork.gitbook.io/crezanetwork-whitepaper/8.-smart-contract-map.md).

# 8. Smart Contract Map

CREZA uses four modular contracts—each with a single responsibility on BSC.

```mermaid
flowchart TB
    R["CREZAFactoryRouter.sol<br/>Gateway & user entry"]
    R --> T["CREZAToken.sol<br/>BEP-20 mint / burn"]
    R --> V["CREZAReservePool.sol<br/>USDT vault"]
    R --> E["CREZARewardsEngine.sol<br/>Levels & DAO pool"]
```

## Contract roles

### CREZAFactoryRouter

* User-facing deposits, claims, redemptions, referrals
* Enforces $10–$1,000 deposit and $3,000 daily withdrawal limits
* Routes capital between mint, vault, and rewards

### CREZAToken

* Standard BEP-20 transfers and balances
* `mint()` and `burn()` callable **only by Router**

### CREZAReservePool

* Holds 100% deposited USDT
* **No admin sweep** — releases USDT only via router-triggered payouts

### CREZARewardsEngine

* 20-generation referral map
* 2× passive and 3× active caps
* Sunday DAO Sovereign Pool settlement

## Security pattern

```mermaid
flowchart LR
    A[External call] --> B{onlyRouter?}
    B -->|Yes| C[Execute mint/burn]
    B -->|No| D[Revert]
```

## Design principle

Monolithic contracts increase attack surface and gas. CREZA separates **token logic**, **vault custody**, and **reward math** for auditability and clarity.


---

# 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://crezanetwork.gitbook.io/crezanetwork-whitepaper/8.-smart-contract-map.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.