> 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/security/roadmap.md).

# Roadmap

## Roadmap

The VOID roadmap outlines the major protocol and product milestones currently planned.

{% hint style="info" %}
Security and production readiness take priority over launch timing.
{% endhint %}

### Pre-Mainnet

Current priorities before mainnet include:

* external security review of production contracts
* final production deployment testing
* local browser proving
* association-set enforcement
* final governance and key separation
* production monitoring and alerting
* LP locker and launch-hook verification
* mainnet contract verification
* final launch-readiness checks

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

### Mainnet Launch

The initial VOID mainnet release is planned to include:

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>VOID Protocol</strong></td><td>Production deployment on Robinhood Chain.</td></tr><tr><td><strong>VOID Token</strong></td><td>Fixed-supply protocol token deployed on Robinhood Chain.</td></tr><tr><td><strong>Private Balance</strong></td><td>Deposit supported assets into encrypted private notes.</td></tr><tr><td><strong>Private Send</strong></td><td>Private transfers between VOID users.</td></tr><tr><td><strong>Private Buy / Sell</strong></td><td>Trade supported assets from private balance.</td></tr><tr><td><strong>Asset Registry</strong></td><td>Production registry for supported protocol assets.</td></tr><tr><td><strong>Uniswap v4 Liquidity</strong></td><td>Initial VOID / ETH launch liquidity on Robinhood Chain.</td></tr></tbody></table>

### Post-Launch Expansion

After the initial mainnet release, development is expected to expand beyond the core private balance and trading experience.

Planned areas include:

* **Asset Registry expansion**
* **Private Payments**
* **Merchant Payments**
* **Payroll**
* **AI Agent Payments**
* **Check+**
* **Disclosure Keys**
* **OTC & Treasury**
* **Wallet integrations**
* **Public SDK**

{% hint style="info" %}
Post-launch products will be introduced progressively rather than activated simultaneously at launch.
{% endhint %}

### Q1 2027

Current Q1 2027 product targets include:

* **Referral System**
* **VOID Chrome Extension**

### Roadmap Status

{% hint style="warning" %}
Roadmap items represent the current development direction and may change based on:

* security review findings
* testnet results
* Robinhood Chain infrastructure
* ecosystem dependencies
* technical requirements
* production readiness
  {% endhint %}

VOID will prioritize a secure production release over meeting an arbitrary launch date.


---

# 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/security/roadmap.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.