> For the complete documentation index, see [llms.txt](https://docs.lacunalabs.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lacunalabs.xyz/getting-started/your-first-private-transfer.md).

# Your First Private Transfer

How to make your first private crypto transfer with shielded balances and zero-knowledge proofs.

This walkthrough shows how to make your first private crypto transfer with Lacuna. You start with a public wallet balance and move into a shielded transfer flow.

## Step 1 — Shield

Tap **Shield**, choose the token and amount, and confirm. Your funds move into the shielded pool and a private note is created for you. On-chain, this appears as a deposit, but it does not reveal the private transaction that follows.

## Step 2 — Transfer

Tap **Send**, enter the recipient and amount, and confirm. Lacuna generates a zero-knowledge proof that verifies you control enough shielded funds without revealing your balance, identity, or source deposit.

## Step 3 — Recipient Receives

When you send inside Lacuna's shielded pool, the recipient gets a private note they can spend or unshield. You can also send directly to a public wallet address. No public blockchain link connects your deposit to the recipient's balance.

## Step 4 — Unshield (Optional)

Whenever you want funds back on a public wallet address, tap **Unshield**.

That is the full private transfer cycle: shield funds, send a private payment, and unshield when you need public settlement.


---

# 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://docs.lacunalabs.xyz/getting-started/your-first-private-transfer.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.
