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

# Welcome

A mobile, non-custodial privacy wallet for private crypto transactions and agentic payments.

Lacuna is a mobile-native, non-custodial privacy wallet for private crypto transactions. Shield your assets, then swap, bridge, transfer, and pay without exposing your activity on a public blockchain.

It combines on-chain privacy, shielded balances, and self-custody in one mobile wallet. Your keys stay on your device, and nobody else can view or move your funds.

## Where To Start

* **New Here?** Read [What Is Lacuna?](/introduction/what-is-lacuna.md) for the big picture.
* **Want To Try It?** Jump to the [Quickstart](/getting-started/quickstart.md) and make your first private transfer.
* **Building On Lacuna?** Head to the [Wallet & Developer SDK](/for-developers/sdk.md).

## How Lacuna Works

1. **Shield**\ <mark style="color:$info;">Move funds into a private shielded pool for confidential on-chain activity.</mark>
2. **Use**\ <mark style="color:$info;">Make private transfers, swaps, bridging, and payments from inside the pool.</mark>
3. **Unshield**\ <mark style="color:$info;">Withdraw to a public wallet address whenever you need public settlement.</mark>


---

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