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

# Sending

Shielded transfers send tokens privately from your shielded balance to another Nullmask user.

### Requirements <a href="#requirements" id="requirements"></a>

* The recipient must have a registered receiving key on Nullmask
* You must have sufficient shielded balance (amount + fee)

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

1. Navigate to the **Send** screen
2. Select the token
3. Enter the amount
4. Enter or paste the recipient's Ethereum address
5. Confirm the transaction in your wallet

### What Happens Behind the Scenes <a href="#what-happens-behind-the-scenes" id="what-happens-behind-the-scenes"></a>

1. The wallet signs a standard EIP-1559 transfer (e.g., "Send 1 ETH to 0xAlice")
2. The RPC proxy intercepts the transaction
3. The proxy checks that the recipient has a registered receiving key
4. The proxy selects funding notes from your shielded balance
5. A ZK proof is generated proving:
   * You authorized this transfer (ECDSA signature)
   * You have sufficient funds (note ownership + Merkle membership)
   * The output note is correctly encrypted for the recipient
6. The relayer submits the proof to the contract
7. The contract verifies the proof, spends your notes, and creates new notes


---

# 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/sending.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.