> For the complete documentation index, see [llms.txt](https://vitaprotocol.gitbook.io/vita/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitaprotocol.gitbook.io/vita/vita-protocol/tokenomics/chapter-2-token-parameters-and-genesis-allocation.md).

# Chapter 2 · Token Parameters and Genesis Allocation

A tenfold mirror: homage to twenty-one million

The total supply of VITA is fixed at <mark style="color:$warning;">**210,000,000**</mark> — a tenfold mirror of Bitcoin's 21,000,000 hard cap. The contracts retain no minting function; the supply is a mathematical ceiling that no governance proposal may touch. Genesis allocation is locked once and for all:

| Module                                                       | Share | Amount           | Function                                                          |
| ------------------------------------------------------------ | ----- | ---------------- | ----------------------------------------------------------------- |
| <mark style="color:blue;">Genesis Stacking</mark>            | 25%   | 52,500,000 VITA  | Genesis issuance along the hundred-tier bonding curve             |
| <mark style="color:blue;">Genesis Nodes</mark>               | 5%    | 10,500,000 VITA  | Unlocked not by the passage of time but by the growth of value    |
| <mark style="color:blue;">Crystal activation rights</mark>   | 10%   | 21,000,000 VITA  | Sealed inside 2,100,000 crystals                                  |
| <mark style="color:blue;">Network Rewards</mark>             | 2%    | 4,200,000 VITA   | Distributed by weight once stacking ends                          |
| <mark style="color:blue;">DEX LP liquidity</mark>            | 8%    | 16,800,000 VITA  | The depth base of the trading market                              |
| <mark style="color:blue;">Long-term ecosystem release</mark> | 50%   | 105,000,000 VITA | Long-term release to the ecosystem pool · 50% burned in real time |

<figure><img src="https://3424572652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoLHhg79LiL5zNwP5HryG%2Fuploads%2FM2v2llTodv3hSJKn4HFW%2Fimage.png?alt=media&amp;token=98a0672a-5279-471f-9642-50c1f8f3717e" alt=""><figcaption></figcaption></figure>

* <mark style="color:$warning;">**Disclosure commitment**</mark>: all token, LP, burn and core contract addresses are published at launch.
* <mark style="color:$warning;">**Execution commitment**</mark>: release, rewards, burning and phase transitions are executed automatically by contracts.
* <mark style="color:$warning;">**Float ceiling**</mark>: maximum lifetime float ≤ the genesis modules combined, <mark style="color:$warning;">**105,000,000**</mark>(25 + 5 + 10 + 2 + 8); actual float runs far below this ceiling as multi-path burning proceeds.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vitaprotocol.gitbook.io/vita/vita-protocol/tokenomics/chapter-2-token-parameters-and-genesis-allocation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.