> 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/testnet-status.md).

# Testnet Status

VOID is live on **Robinhood Chain Testnet**.

{% hint style="warning" %}
VOID is currently **unaudited testnet software**.

Mainnet is planned only after completion of the required external security review, production-readiness checks and final launch verification.
{% endhint %}

All testnet tokens have **no monetary value**.

### Live on Testnet

Current testnet functionality includes:

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Private Balance</strong></td><td>Deposit supported assets and receive encrypted private notes.</td></tr><tr><td><strong>Private Send</strong></td><td>Send supported assets privately to another VOID address, submitted by the VOID relayer.</td></tr><tr><td><strong>Private Buy</strong></td><td>Buy supported assets and receive them directly into private balance.</td></tr><tr><td><strong>Private Sell</strong></td><td>Sell from private balance and receive proceeds as a private note.</td></tr><tr><td><strong>Private Swap</strong></td><td>Swap one private balance into another at <code>/swap</code>, submitted by the VOID relayer.</td></tr><tr><td><strong>Withdraw</strong></td><td>Move assets from private balance back to a public address, submitted by the VOID relayer.</td></tr><tr><td><strong>Testnet Faucet</strong></td><td>Claim test assets for use on Robinhood Chain Testnet.</td></tr><tr><td><strong>Gasless Swap</strong></td><td>Public swap at <code>/gasless</code>, listed in the app menu. Swap gas is taken from the token you receive.</td></tr></tbody></table>

### Testnet VOID Token

The current testnet includes a **VOID test token** used for protocol and trading functionality.

The test token:

* has no monetary value
* is used only for testnet functionality
* is not the future mainnet VOID token
* should not be treated as mainnet token information

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

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

### Not Live Yet

The following are not currently live:

* mainnet contracts
* mainnet VOID token
* mainnet liquidity
* local browser proving
* note backup and recovery
* enforced association sets
* selective disclosure
* Check+

### Known Limits

#### Note Size

VOID uses **6 decimals**.

A single private note can hold approximately **18.4 trillion VOID**.

This is significantly above the planned mainnet supply of **1 billion VOID**.

{% hint style="info" %}
In practice, there is **no meaningful per-note limit for VOID**.
{% endhint %}

Amounts are stored as 64-bit (u64) numbers in base units, so the limit depends on the token's decimals. **WETH uses 18 decimals**, so a single note can hold only about **18.44 WETH**. Larger WETH balances are held as several notes.

### Trade Limits

Current testnet trade settings include:

| Setting                         | Current Limit |
| ------------------------------- | ------------: |
| **Maximum Price Impact**        |            3% |
| **Default Slippage**            |            1% |
| **Quote Lifetime**              |   120 seconds |
| **Minimum tUSDG Private Trade** |       1 tUSDG |
| **Minimum VOID Private Trade**  |      200 VOID |
| **Minimum WETH Private Trade**  |   0.0002 WETH |

The minimum applies to the amount you spend from your private balance in a Private Buy, Private Sell or each step of a Private Swap. It is enforced by the private pool contract. Private Buy paid from your public wallet has no minimum.

{% hint style="warning" %}
Testnet liquidity is limited.

Larger trades may fail if price impact exceeds the **3% maximum**.
{% endhint %}

### USDG

USDG can be frozen by its issuer.

USDG deposited through VOID is held inside the VOID contract, so an issuer-level freeze could affect those funds.

The app displays this warning when users interact with USDG.

{% hint style="warning" %}
Issuer controls remain in force even when an asset is held inside VOID.
{% endhint %}

### Not Final Before Mainnet

The following remain subject to final production configuration:

* mainnet contract addresses
* final production deployment
* LP structure
* market-maker terms
* secondary liquidity pairs
* mainnet launch date
* final relayer key structure
* production governance configuration
* note backup and recovery policy

The current plan is for the main ETH liquidity position to be locked for **12 months**.

The planned mainnet VOID token supply is:

**1,000,000,000 VOID**

with **6 decimals**.

{% hint style="info" %}
No mainnet launch date has been confirmed.
{% endhint %}

### Association Sets

Association sets are planned but are **not currently enforced**.

Selective disclosure is also not currently live.

The testnet includes an association-set registry, but:

* the currently published association root is a placeholder
* the circuits do not yet verify association-set membership
* the registry is controlled by the **2-of-3 Safe**

{% hint style="warning" %}
The presence of the testnet registry should not be interpreted as live association-set enforcement.
{% endhint %}

### Security Review

VOID is currently **unaudited testnet software**.

A full external security review is required before mainnet launch.

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

* 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
* deployment configuration and permissions

{% hint style="danger" %}
Do not use mainnet funds with VOID until mainnet has been officially launched and the production contract addresses have been published through official VOID channels.
{% endhint %}

### Mainnet Gate

Mainnet is planned only after:

1. completion of the required external security review
2. final production contracts are deployed
3. deployed contracts and configuration are verified
4. launch pool and LP-locker configuration are confirmed
5. production infrastructure is ready
6. final launch checks are completed
7. trading is explicitly opened

The following must also be in place before mainnet:

* local browser proving
* association-set enforcement in the circuits
* selective disclosure
* note backup and recovery
* relayer funding and abuse protection
* paid RPC infrastructure
* a published privacy and threat-model review
* a bug bounty
* production key separation and monitoring

{% 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/testnet-status.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.