> 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/whitepaper/chapter-9-token-parameters-and-genesis-allocation.md).

# Chapter 9 · Token Parameters and Genesis Allocation

From here, principle becomes executable rule

The first eight chapters answered how the tower stands. This chapter and the two that follow set out the protocol's foundation of value — total issuance, method of minting and the bonding to Bitcoin — every figure written into the contracts and verifiable on chain. The total supply of VITA is fixed at <mark style="color:$warning;">**210,000,000**</mark>, with no minting interface retained. The number is a tenfold mirror of Bitcoin's 21 million cap, and genesis allocation is locked once and for all:

| Module                                                           | Share | Amount           | Function                                                                                 |
| ---------------------------------------------------------------- | ----- | ---------------- | ---------------------------------------------------------------------------------------- |
| <mark style="color:$primary;">Genesis Stacking</mark>            | 25%   | 52,500,000 VITA  | Genesis issuance along a hundred-tier bonding curve                                      |
| <mark style="color:$primary;">Genesis Nodes</mark>               | 5%    | 10,500,000 VITA  | Genesis nodes release holdings not with the passage of time but with the growth of value |
| <mark style="color:$primary;">Crystal activation rights</mark>   | 10%   | 21,000,000 VITA  | Sealed within 2,100,000 crystals and released on activation                              |
| <mark style="color:$primary;">Network Rewards</mark>             | 2%    | 4,200,000 VITA   | A long-term reserve of entitlements for contributors to the Tower Network                |
| <mark style="color:$primary;">DEX LP liquidity</mark>            | 8%    | 16,800,000 VITA  | Builds the depth base of the trading market                                              |
| <mark style="color:$primary;">Long-term ecosystem release</mark> | 50%   | 105,000,000 VITA | A long-term release reserve for ecosystem building, deflating alongside on-chain burning |

<figure><img src="https://3424572652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoLHhg79LiL5zNwP5HryG%2Fuploads%2F5bHJhJSReJHSvZG7rK1D%2Fimage.png?alt=media&amp;token=b10c14b9-ea8d-442f-a506-70dd83eec1dc" alt=""><figcaption></figcaption></figure>

* <mark style="color:$warning;">**All addresses public**</mark>: every token, LP, burn and core contract address is published at launch.
* <mark style="color:$warning;">**All by contract**</mark>: release, rewards, burning and phase transitions are all executed automatically by contracts.
* <mark style="color:$warning;">**Supply wholly fixed**</mark>: 210,000,000 is a mathematical ceiling that no governance proposal may touch.


---

# 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/whitepaper/chapter-9-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.