> 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/user-safety.md).

# User Safety

## Security Best Practices

### Protect Your Wallet

{% hint style="danger" %}
**Never share your seed phrase or private key.**

VOID will never ask for either.
{% endhint %}

### Check the URL

Only use the official VOID websites:

* `void-protocol.com`
* `app.void-protocol.com`

{% hint style="warning" %}
Always check the domain carefully before connecting your wallet or signing a message.
{% endhint %}

### Back Up Your Wallet

Your private notes are tied to your wallet.

If you permanently lose access to your wallet, you may also lose access to your private balance.

{% hint style="warning" %}
Note backup and recovery are **not live yet**.
{% endhint %}

### Read Every Signature Request

Unlocking your private balance uses a **wallet signature**.

It is:

* not a payment
* not an on-chain transaction
* not a transfer of funds

Always check exactly what your wallet is asking you to sign.

### Remember What Is Public

Withdrawals are public on-chain.

A withdrawal reveals:

* receiving address
* token
* amount
* your wallet as the transaction sender only if you choose to submit the withdrawal from your own wallet (normally the VOID relayer submits it)

{% hint style="info" %}
Once funds leave VOID and return to a public wallet, normal public-chain visibility applies.
{% endhint %}

### Testnet Privacy Is Limited

Privacy is more limited on testnet because the anonymity set is still small.

Timing, amounts and public entry or exit activity may make transactions easier to correlate.

{% hint style="warning" %}
Do not treat VOID testnet as a guarantee of anonymity.
{% endhint %}

### Senders Can Recognise Their Notes Being Spent

Whoever creates a note knows its nullifier secret. If someone sends you a note, they can potentially recognise when that particular note is later spent. They cannot spend it or see your other notes.

### WETH Note Size

A single private note can hold about **18.44 WETH** (18 decimals, 64-bit amount limit). 6-decimal tokens such as VOID have a much higher practical limit. Larger WETH balances are held as several notes.

### USDG Can Be Frozen

USDG can be frozen by its issuer.

This can also affect USDG held inside the VOID contract.

{% hint style="info" %}
VOID privacy does not remove issuer-level controls built into the underlying asset.
{% endhint %}

### Testnet Only

{% hint style="danger" %}
Do not use real funds.

VOID is currently running on Robinhood Chain Testnet and the production contracts have not yet completed the required external security review.
{% endhint %}

### Beware of Impersonators

VOID admins will never DM you first asking for:

* funds
* seed phrases
* private keys

{% hint style="danger" %}
Anyone asking for your seed phrase or private key is attempting to compromise your wallet.
{% 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/security/user-safety.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.