# Tokenomics

**Total Supply** : 1,000,000,000 (1 billion) tokens

**Token Name**: KING

**Total Raise**: 6.2m USD

**Listing Price**: 4 cents

**Initial Market Cap**: 400k USD excluding liquidity - 640k including liquidity (10m IDO tokens + 6m Liquidity tokens at 4 cents)

## Token allocation breakdown

* **27%** Fundraising  (vesting and locks According to the numbers above
  * **20%** VC Private Sale (200m tokens) 4m raise 2 cents (3 month lock, then 10% unlock each month)
  * **3%** (30m tokens) 600k raise Seedify.fund Private Sale 2 cents (3 month lock, then 10% unlock each month)
  * **4%** (40m tokens) 1m raise Seedify.fund IDO 4 cents (25% unlock at listing, 25% each proceeding month)
* **15%** Team & Advisors (3 month lock, then 5% unlock each month for 20 months)
* **3%** Exchange Liquidity (20% unlock for initial liquidity, then 5% unlock every month)
* **15%** Community & Marketing (locked initially, then 10% unlock every month for 5 months, then 5% unlock for 10 more months)
* **15%** Development of New Game Features (6 month lock, and then unlocked at 5% unlock each month for 20 months)
* **2%** Partnerships & Exchanges (locked initially, unlocked each month starting from 2nd month, 5% unlock each month for 20 months)
* **3%** Seedify Incubation (6 month lock, and then 10% each month for 10 months)
* **20%** In-game Rewards (locked initially, will be unlocked according to the launch day of the game - the emissions will be 2.5% each month, for 40 months)


---

# 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://cryptoblades.gitbook.io/cryptoblades-kingdoms/the-token/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.