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

# Quickstart

Set up the Lacuna privacy wallet and make your first private crypto transfer in minutes.

Set up the Lacuna privacy wallet and make your first private crypto transfer in a few minutes.

## 1. Install The App

Download the Lacuna mobile wallet for your device:

```
iOS      ->  App Store     (search "Lacuna")
Android  ->  Google Play   (search "Lacuna")
```

## 2. Create Your Wallet

Open the app and create a new non-custodial wallet. Set a PIN and securely back up your recovery phrase. You can also import an existing wallet. See [Setting Up Your Wallet](/the-lacuna-wallet/setting-up-your-wallet.md).

## 3. Fund A Public Address

Send a supported token, such as USDC, to your wallet's public address. This works like any other crypto wallet.

## 4. Shield Your Funds

Tap **Shield** to move funds into the shielded pool. This makes your balance private for on-chain activity.

## 5. Transfer Privately

Send to anyone from inside the pool. The private transfer uses a zero-knowledge proof and is not publicly linkable to your deposit. For the full walkthrough, see [Your First Private Transfer](/getting-started/your-first-private-transfer.md).


---

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