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

# Testnet Faucet

Use the VOID faucet to get test tokens for Robinhood Chain Testnet.

### Get Test Tokens

1. Connect your wallet at [app.void-protocol.com](https://app.void-protocol.com).
2. Open **Testnet Faucet**.
3. Click **Claim**.

You will receive:

* **1,000 tUSDG**

Tokens are sent directly to your **public wallet**.

{% hint style="info" %}
The faucet does not give out VOID. The testnet VOID token has a fixed supply and cannot be minted, so get VOID with **Private Buy** using WETH or tUSDG.

All testnet tokens have no value. Testnet VOID is not the future mainnet VOID token.
{% endhint %}

### Faucet Limits

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Per Wallet</strong></td><td>One claim per wallet per UTC day. The limit resets at 00:00 UTC.</td></tr><tr><td><strong>Per Network</strong></td><td>Up to 5 claims per IP address per day.</td></tr></tbody></table>

### Getting WETH

You can get WETH in two ways:

* buy WETH with **tUSDG** using **Private Buy**
* wrap **testnet ETH** into WETH

{% hint style="warning" %}
All faucet assets are testnet tokens only.

They have no monetary value.
{% 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/user-guide/faucet.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.