> 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/token-launch-and-transparency.md).

# Token Launch & Transparency

VOID is planned to launch on **Robinhood Chain** using **Uniswap v4**.

The launch is designed around:

* transparent supply
* locked liquidity
* publicly labeled project wallets
* fixed launch protections
* verifiable on-chain deployment

{% hint style="warning" %}
VOID has **not launched on mainnet**.

The configuration below reflects the current launch plan and remains subject to final security review, deployment testing and production-readiness checks.
{% endhint %}

### Launch Principles

VOID's planned launch follows a clear set of rules:

* no presale
* no private investor round
* no token bundle
* no hidden launch wallets
* no exempt wallets
* no token-level transfer tax
* project-controlled wallets publicly labeled
* launch liquidity locked
* launch protections implemented through the official Uniswap v4 pool

### Launch Pool

The official launch pool is planned as:

**VOID / ETH on Uniswap v4**

Native ETH is preferred. WETH may be used if required by final Robinhood Chain or Uniswap tooling.

The planned pool fee is:

**1%**

#### No Secondary Launch Pair

VOID does not plan to create a project-controlled V2 VOID pair at launch.

This avoids creating an alternate launch route outside the official v4 launch protections.

Additional markets may be introduced after the temporary launch-protection period.

### Temporary Launch Trading Tax

A temporary launch tax is planned for buys and sells through the official VOID launch pool.

| Launch Window        |     Tax |
| -------------------- | ------: |
| **0–5 minutes**      | **50%** |
| **5–15 minutes**     | **25%** |
| **15–30 minutes**    | **10%** |
| **After 30 minutes** |  **0%** |

After the first 30 minutes, the temporary launch tax ends.

The normal Uniswap pool fee remains.

### How the Launch Tax Works

The launch tax:

* applies to buys and sells through the official launch pool
* is collected in ETH
* is sent to the VOID operations / treasury Safe
* is implemented through the Uniswap v4 hook
* applies equally to wallets trading through the official pool
* has no exempt wallets

The planned hook is designed so the launch-tax schedule cannot be:

* increased
* restarted
* extended
* selectively waived

after deployment.

{% hint style="info" %}
The launch tax is a temporary **pool-level protection mechanism**.

VOID itself remains a plain ERC-20 token with **no transfer tax**.
{% endhint %}

### Trading Opens Explicitly

Deploying the mainnet contracts does **not** automatically open trading.

The planned launch sequence is:

1. Deploy the final production contracts.
2. Verify the production deployment.
3. Confirm contract configuration and permissions.
4. Confirm the launch pool and LP locker.
5. Complete final security and production-readiness checks.
6. Call `open()` to enable trading.

{% hint style="warning" %}
Trading remains closed until the authorized Safe explicitly opens it.
{% endhint %}

### Launch Liquidity

The current plan is to place:

**20% of the total VOID supply**

into launch liquidity.

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

Final pool and liquidity details will be published at launch.

### LP Lock

The main launch liquidity position is currently planned to be locked for:

**12 months**

The planned locker is designed so that:

* the lock cannot be shortened
* the lock can only be extended
* there is no admin path to withdraw the position before expiry

{% hint style="success" %}
The final locker address, lock duration and on-chain verification details will be published before or at mainnet launch.
{% endhint %}

### Project-Controlled Supply

Outside launch liquidity:

* **75%** of total supply is planned to be locked, vesting or subject to controlled release schedules
* **5%** is planned to remain liquid for defined market-management and recovery purposes

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

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

{% hint style="info" %}
The 5% market-management and recovery supply forms part of the existing token allocation.

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

### No Exempt Wallets

The official launch structure is designed with **zero tax-exempt wallets**.

Project-controlled wallets are not planned to trade during the temporary launch-tax period.

### Security Review

VOID is currently **unaudited testnet software**.

An external security review by **Cyberscope** is in progress and is not complete. It covers the launch components:

* VOID token
* Uniswap v4 launch hook
* LP lockers

Before mainnet, a further audit is **planned** to cover the mainnet protocol contracts, the Noir circuits and verifier integration, and the relevant launch permissions and deployment configuration.

VOID also plans to verify the final production deployment before trading opens.

{% hint style="warning" %}
Mainnet trading will only open after the required security review, production deployment checks and final readiness verification are complete.
{% endhint %}

### What Will Be Published

Before or at launch, VOID plans to publish the information required for independent verification, including:

* official VOID contract address
* official launch pool
* launch hook address
* LP locker address
* treasury / operations Safe
* project-controlled wallet labels
* final supply allocation
* lock and vesting information
* relevant security reports
* Robinhood Chain explorer links

### Verify Before You Trade

Only use contract addresses published through official VOID documentation and channels.

Do not rely on contract addresses copied from:

* direct messages
* Telegram replies
* unofficial token trackers
* search results
* third-party posts

{% hint style="danger" %}
The official mainnet VOID contract address has **not yet been published**.

Any token claiming to be the official mainnet VOID token before VOID publishes the verified contract address should be treated as fraudulent.
{% endhint %}

### Launch Status

No mainnet launch date has been confirmed.

Mainnet is planned only after completion of:

* the required external security review
* final production deployment testing
* production-readiness checks
* final launch verification

{% hint style="info" %}
Security and production readiness take priority over launch timing.
{% 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/token-launch-and-transparency.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.
