> 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/6.-minting-engine-80-20.md).

# 6. Minting Engine (80/20)

When a user deposits **$10–$1,000 USDT**, 100% enters the vault. CRZ is minted only on the **80%** allocation; **20%** stays unminted to raise the price floor.

```mermaid
flowchart TB
    D["User Deposit<br/>$10 – $1,000 USDT"] --> V["CREZAReservePool<br/>100% USDT locked"]
    V --> M["80% Dynamic Mint<br/>CRZ → user wallet"]
    V --> S["20% Unminted Support<br/>No CRZ issued"]
    M --> F["Price floor ↑"]
    S --> F
```

## Step-by-step

| Step | Action                                         |
| ---- | ---------------------------------------------- |
| 1    | User approves & deposits USDT                  |
| 2    | Router validates min/max limits                |
| 3    | Full deposit amount credited to vault          |
| 4    | 80% triggers bonding-curve mint to user        |
| 5    | 20% remains as collateral surplus (no new CRZ) |

## Asset-to-token surplus

Because **100% USDT enters** but only **\~80% becomes token liability**, every deposit increases backing per circulating CRZ. This is the **price floor gap**—a structural uplift on each deposit.

## Formula (conceptual)

**CRZ minted = f(deposit × 80%, current spot price P(t))**

Where **P(t)** comes from the on-chain bonding curve tied to vault reserves and circulating supply.

## Effect on holders

Each new deposit benefits existing holders by increasing vault backing relative to minted supply—without requiring secondary market buying.


---

# 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/6.-minting-engine-80-20.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.