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

# Tokenomics

####  Initial Market Data

* **Token Name:** ZkMindAI
* **Token Symbol:** $ZKAI
* **Total Supply:** 1,000,000,000 $ZKAI
* **Public Price (Listing/IDO):** $0.008
* **Fully Diluted Valuation (FDV):** **$8,000,000**
* **TGE Unlock (All Categories):** **100%**
* **Initial Circulating Supply at TGE:** 78.75M
* **Initial Market Cap (IMC):** **$630,000**
* **Chain:** zkSync
* **DEX Pair:** $ZKAI / $SOL \
  \
  Fundraising Summary

  | Round  | Raise    | Token Price | Tokens     | % of Supply | TGE Unlock |
  | ------ | -------- | ----------- | ---------- | ----------- | ---------- |
  | KOLs   | $200,000 | $0.0072     | 27,777,778 | 2.78%       | 100%       |
  | Public | $500,000 | $0.0080     | 62,500,000 | 6.25%       | 100%       |

  > **Total Raise:** $700,000\
  > **Total Sale Allocation:** 90,277,778 ZKAI (9.03%)

  ####           Token Distribution Overview

  | Category          | Allocation | Tokens      | TGE Unlock | Vesting               |
  | ----------------- | ---------- | ----------- | ---------- | --------------------- |
  | Public            | 6.25%      | 62,500,000  | 100%       | None                  |
  | KOLs              | 2.78%      | 27,777,778  | 100%       | None                  |
  | Liquidity         | 15.00%     | 150,000,000 | 100%       | None                  |
  | Team              | 10.00%     | 100,000,000 | 0%         | 6M Cliff → 36M Linear |
  | Development       | 8.00%      | 80,000,000  | 0%         | 3M Cliff → 24M Linear |
  | Marketing         | 8.00%      | 80,000,000  | 100%       | None                  |
  | Reserve           | 15.00%     | 150,000,000 | 0%         | 6M Cliff → 36M Linear |
  | Ecosystem / DAO   | 15.00%     | 150,000,000 | 0%         | 6M Cliff → 54M Linear |
  | Advisors          | 5.00%      | 50,000,000  | 0%         | 5M Cliff → 24M Linear |
  | Farming / Staking | 10.00%     | 100,000,000 | 100%       | None                  |

####        TGE Summary

| Component | TGE Unlock | Tokens at TGE | Value at TGE |
| --------- | ---------- | ------------- | ------------ |
| KOLs      | 100%       | 27,777,778    | $200,000     |
| Public    | 100%       | 62,500,000    | $500,000     |
| Liquidity | 100%       | 75,000,000\*  | $600,000     |
| Marketing | 100%       | 12,500,000    | $100,000     |
| Farming   | 100%       | 15,000,000    | $120,000     |

> **Total TGE Circulating Supply:** 78.75M\
> **Initial Market Cap (IMC):** $630,000\
> (\*Assumes half of liquidity allocated to TGE pool)

***

#### 📌 Notes

* **No vesting or cliff** for Public, KOLs, Marketing, or Farming allocations. These are **100% unlocked at TGE**.
* All other categories are **locked**, and vested gradually based on standard monthly vesting schedules.


---

# 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://zkmindai.gitbook.io/zkmindai-docs/tokenomics.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.