> 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/how-void-works.md).

# How VOID Works

VOID lets users move public assets into a private balance, use that balance privately, and withdraw back to a public wallet when they choose.

{% hint style="info" %}
VOID is **non-custodial**. Only your wallet can authorize spending your private notes.
{% endhint %}

### The Flow

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>1. Public Wallet</strong></td><td>Hold supported public tokens on Robinhood Chain.</td></tr><tr><td><strong>2. Deposit</strong></td><td>Move supported assets into VOID through a public on-chain transaction.</td></tr><tr><td><strong>3. VOID Private Balance</strong></td><td>Your deposited value becomes encrypted private notes.</td></tr><tr><td><strong>4. Private Send</strong></td><td>Send value privately to another VOID user.</td></tr><tr><td><strong>5. Private Buy / Sell</strong></td><td>Trade supported assets from your private balance through the VOID relayer.</td></tr><tr><td><strong>6. Withdraw</strong></td><td>Move funds from private balance back to a public address.</td></tr></tbody></table>

<figure><img src="https://2440728462-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8L1KmLQJiIlFg0pGYpD7%2Fuploads%2F9bVhbRPptIipFjdso6Qh%2FVOID%20Protocol_%20Private%20Activity%20Flow.png?alt=media&amp;token=d750422c-340a-4a50-a97c-c269a26fcee7" alt=""><figcaption></figcaption></figure>

### What Happens

#### Deposit

Public tokens move into VOID and become encrypted private notes.

{% hint style="warning" %}
The deposit itself is public on-chain.
{% endhint %}

#### Private Balance

Your balance is represented by encrypted notes rather than a publicly readable wallet balance.

#### Private Send

Send value to another VOID user without publishing the direct sender-to-recipient relationship.

#### Private Buy / Sell

Trade from private balance through the VOID relayer.

The underlying DEX execution remains public.

#### Withdraw

Move funds back to a public address.

Withdrawals are public on-chain.

### Behind the Scenes

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Wallet Signature</strong></td><td>Authorizes actions and unlocks your private balance.</td></tr><tr><td><strong>Proof Service</strong></td><td>Generates the zero-knowledge proof required for the private action.</td></tr><tr><td><strong>VOID Relayer</strong></td><td>Submits private trades, Private Send and Withdraw from private balance and pays their gas on testnet.</td></tr><tr><td><strong>VOID Contracts</strong></td><td>Verify proofs, commitments and nullifiers on-chain.</td></tr><tr><td><strong>Robinhood Chain</strong></td><td>Records and verifies the resulting protocol activity.</td></tr></tbody></table>

Zero-knowledge proofs allow VOID contracts to verify valid private actions without revealing the private note itself.

{% hint style="warning" %}
Deposits, withdrawals and underlying DEX trades remain public.

VOID protects the private activity between those public entry and exit points.
{% endhint %}

**Public in. Private inside VOID. Public out.**


---

# 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/how-void-works.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.