> 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/2.-zero-supply-architecture.md).

# 2. Zero-Supply Architecture

At deployment, **exactly 0.00 $CRZ** exist. Tokens appear only when users deposit USDT through the smart contract.

```mermaid
flowchart TB
    GEN["Genesis: 0 CRZ"] --> DEP["User deposits USDT"]
    DEP --> VAULT["100% → Reserve Vault"]
    VAULT --> M80["80% → Mint CRZ to user"]
    VAULT --> R20["20% → Unminted floor support"]
```

## Why zero-supply matters

| Pre-minted model                | CREZA zero-supply            |
| ------------------------------- | ---------------------------- |
| Team/VC tokens unlock over time | **No insider allocation**    |
| Supply exists before liquidity  | **Supply follows deposits**  |
| Price driven by narratives      | **Price tied to vault math** |

## Genesis rule

**Genesis Token Supply = 0.00 $CRZ**

There are no founder tokens, advisor pools, marketing reserves, or hidden team wallets. Circulating supply equals what users have minted through deposits.

## Four autonomous mechanics

1. **80/20 minting** — 80% of deposit value mints CRZ; 20% enters vault without minting
2. **85/15 redemption** — 85% paid out; 15% retained; 100% tokens burned
3. **Renounced ownership** — admin sent to null address; code is immutable
4. **Product velocity** — seven pillars drive usage, fees, and burns

## Backing guarantee

100% of deposited USDT stays in **CREZAReservePool** until paid out through verified redemptions or reward flows governed by contract logic.


---

# 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/2.-zero-supply-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.