# Tokenomics

$OZARUS is a fixed-supply token — with no minting after launch 🔒. This ensures scarcity and transparency from day one.

<figure><img src="https://ozarus.gitbook.io/ozarus-anglais/~gitbook/image?url=https%3A%2F%2F2145166822-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fezvr3xpf6PiXtQHgFhUQ%252Fuploads%252FmGIO00QOgvkNKdA3U1pJ%252FTokenimics.png%3Falt%3Dmedia%26token%3Db779f32d-ac0a-417a-950a-06e46b1d4211&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=c0f8bcb2&#x26;sv=2" alt=""><figcaption></figcaption></figure>

Liquidity will be locked via **Streamflow** 🔐 to prevent any risk of rugs. Unsold tokens will be burned � � to protect early backers and avoid inflation. A percentage of tokens are allocated for:

📢 Strategic marketing and growth

🤝 Partnership rewards

🛠️ Ecosystem development

👨💻 Team (with vesting schedules)

Every smart contract will be fully audited and made public prior to launch. 📄

**Name:** OZARUS **Symbol:** $OZARUS **Total Supply:** Fixed after launch (no future minting)

**Distribution:**

* 10% — Treasury & Reserve (future development & security)
* 15% — Strategic Partnerships
* 20% — Ecosystem Growth & Rewards (staking, incentives)
* 15% — Liquidity (locked)
* 10% — Marketing & Communication
* 15% — Team & Advisors (vesting)
* 15% — Public Sale & Launch

**Key Features:**

* No minting after launch
* Unsold tokens burned
* Locked liquidity
* Audited and verified smart contract


---

# Agent Instructions: 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:

```
GET https://ozarus-ai.gitbook.io/whitepaper/getting-started/tokenomics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.