> For the complete documentation index, see [llms.txt](https://docs.nullmask.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullmask.pro/user-guide/withdrawing.md).

# Withdrawing

Withdrawals move funds from your shielded balance to any Ethereum address on the base chain.

### Steps <a href="#steps" id="steps"></a>

1. Navigate to the **Unshield** tab on the Shield screen
2. Select the token
3. Enter the amount
4. Enter the destination address (or click "Use My Wallet" for your own address)
5. Confirm the transaction in your wallet

### What Happens <a href="#what-happens" id="what-happens"></a>

1. The wallet signs a transfer to the destination address
2. The proxy detects the recipient has no registered receiving key → withdrawal
3. A ZK proof is generated
4. The relayer submits the proof to the contract
5. The contract verifies the proof and sends funds directly to the destination address

### Privacy Considerations <a href="#privacy-considerations" id="privacy-considerations"></a>

* The withdrawal recipient address and amount are **public** on-chain
* Use a fresh, unlinkable address for withdrawals to maximize privacy
* You cannot withdraw to addresses that are registered on Nullmask (this is by design — use Send instead)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nullmask.pro/user-guide/withdrawing.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 `build a script that syncs our docs to a CMS` 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.