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

# Tokenomics

VOID is the protocol token of **VOID Protocol**.

The mainnet VOID token has **not launched yet**. The information below reflects the current planned mainnet structure.

{% hint style="warning" %}
Tokenomics remain subject to final production deployment, security review and launch-readiness checks.
{% endhint %}

### Token Overview

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Total Supply</strong></td><td>1,000,000,000 VOID</td></tr><tr><td><strong>Decimals</strong></td><td>6</td></tr><tr><td><strong>Standard</strong></td><td>ERC-20</td></tr><tr><td><strong>Additional Minting</strong></td><td>None planned after deployment</td></tr><tr><td><strong>Token-Level Transfer Tax</strong></td><td>None</td></tr></tbody></table>

### Planned Allocation

| Allocation                  |    Share |                 Tokens |
| --------------------------- | -------: | ---------------------: |
| **Ecosystem & App Rewards** |  **30%** |       300,000,000 VOID |
| **Treasury & Operations**   |  **23%** |       230,000,000 VOID |
| **Launch Liquidity**        |  **20%** |       200,000,000 VOID |
| **Team**                    |  **15%** |       150,000,000 VOID |
| **Community & Marketing**   |  **10%** |       100,000,000 VOID |
| **Strategic Contributor**   |   **2%** |        20,000,000 VOID |
| **Total**                   | **100%** | **1,000,000,000 VOID** |

#### VOID Supply Allocation

{% hint style="info" %}
The allocation above represents the full fixed supply of VOID. No additional allocation exists outside the 1,000,000,000 token supply.
{% endhint %}

### Allocation Breakdown

#### Ecosystem & App Rewards — 30%

Allocated to support long-term growth and participation across the VOID ecosystem.

This may include:

* application rewards
* user participation programs
* ecosystem incentives
* supported asset expansion
* integration incentives
* future protocol initiatives

This allocation is intended to be released gradually through disclosed ecosystem programs rather than becoming fully liquid at launch.

#### Treasury & Operations — 23%

Allocated to support the ongoing development and operation of VOID, including:

* protocol development
* infrastructure
* security and audits
* operations
* integrations
* ecosystem support

Treasury-controlled funds will be managed through a **multisig Safe**.

#### Launch Liquidity — 20%

Allocated to the initial VOID liquidity pool on Robinhood Chain.

The VOID allocation will be paired with **team-provided ETH**.

{% hint style="info" %}
The current plan is for the main VOID / ETH liquidity position to be locked for **12 months**.
{% endhint %}

#### Team — 15%

Allocated to the VOID team.

The current planned vesting structure is:

* **12-month cliff**
* followed by **36-month linear vesting**

Final vesting contracts and unlock schedules will be published before mainnet launch.

#### Community & Marketing — 10%

Allocated to:

* community growth
* ecosystem awareness
* marketing initiatives
* adoption programs

This allocation is intended to be released through a **controlled schedule** rather than becoming fully liquid at launch.

#### Strategic Contributor — 2%

Allocated under an existing strategic contributor agreement.

The planned vesting structure is:

* **linear vesting over 12 months**

The relevant vesting wallet or contract will be publicly identifiable once the production structure is finalized.

### Launch Supply Status

The current plan is for the majority of project-controlled supply to remain **locked, vesting or subject to controlled release schedules** at launch.

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Launch Liquidity</strong></td><td>20% of total supply</td></tr><tr><td><strong>Locked / Vesting / Controlled Release</strong></td><td>75% of total supply</td></tr><tr><td><strong>Market Management / Recovery</strong></td><td>5% of total supply</td></tr></tbody></table>

In total, **80% of VOID supply sits outside the launch liquidity pool**.

Of that:

* **75%** is planned to be locked, vesting or released through controlled programs
* **5%** is planned to remain liquid for defined market-management and recovery purposes

{% hint style="info" %}
The 5% market-management and recovery supply is part of the existing project-controlled allocations.

It is **not an additional allocation above the 100% total supply**.
{% endhint %}

All team, treasury and market-management wallets are planned to be publicly labeled before trading begins.

### Vesting & Controlled Releases

Different allocations serve different purposes and therefore do not use one identical vesting schedule.

| Allocation                       | Planned Structure                                        |
| -------------------------------- | -------------------------------------------------------- |
| **Team**                         | 12-month cliff + 36-month linear vesting                 |
| **Strategic Contributor**        | 12-month linear vesting                                  |
| **Treasury & Operations**        | Controlled through multisig Safe                         |
| **Ecosystem & App Rewards**      | Gradual release through disclosed programs               |
| **Community & Marketing**        | Controlled release programs                              |
| **Market Management / Recovery** | Liquid, publicly labeled and governed by published rules |

Where applicable, VOID plans to publish:

* vesting contract addresses
* lock contract addresses
* beneficiary wallets
* unlock schedules
* treasury wallets
* market-management wallets

{% hint style="success" %}
The goal is to make project-controlled supply **visible and independently verifiable on-chain**.
{% endhint %}

### Wallet Transparency

After mainnet deployment, VOID will publish the official wallet and contract addresses associated with the major token allocations.

This will include, where applicable:

* launch liquidity and LP locker
* treasury Safe
* ecosystem wallets or contracts
* team vesting contracts
* community and marketing wallets
* strategic contributor vesting
* market-management and recovery wallet

{% hint style="warning" %}
Final addresses will only be published once the production deployment has been completed and verified.

Users should rely only on addresses published through VOID's official documentation and channels.
{% endhint %}

### Testnet Token

Robinhood Chain Testnet uses a **VOID test token** for protocol testing.

It:

* has no monetary value
* is not the mainnet VOID token
* is used only for testnet functionality

{% hint style="info" %}
The mainnet VOID token will be a **new production deployment**.

Testnet addresses and balances should not be treated as mainnet token information.
{% endhint %}


---

# 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://void-protocol-2.gitbook.io/void-protocol-docs/start-here/veil-token/tokenomics.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.