> 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/the-lacuna-wallet/overview.md).

# Wallet Overview

A non-custodial mobile privacy wallet for shielded balances, private transfers, and private crypto payments.

The Lacuna wallet is the core of the protocol. Private swaps, bridging, transfers, and agentic payments all run through it. It is a non-custodial mobile privacy wallet, so you hold the keys and the app never holds your funds.

## What The Wallet Does

* Holds both **public balances** for normal blockchain use and **shielded balances** for private transactions.
* Lets you **shield, unshield, and transfer** funds with on-chain privacy.
* Powers **private swaps, private bridging, and x402 payments** from inside the shielded pool.
* Manages **viewing keys** for optional selective disclosure and compliance workflows.

## Non-Custodial, Always

Your private keys and shielded note secrets are generated and stored only on your device. There is no Lacuna server that can access, freeze, or move your funds. If you lose your device, your [Backup & Recovery](/the-lacuna-wallet/backup-recovery.md) flow restores everything.

## The Privacy Model

<figure><img src="https://2289142168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYjyKq8HBCbrrexf9ASZm%2Fuploads%2FYViKhkbfKi3mTGwrs8fX%2FChatGPT%20Image%20Jun%2022%2C%202026%2C%2012_37_50%20AM.png?alt=media&amp;token=c04b69b2-995e-4cca-af02-6d079d6e4419" alt=""><figcaption></figcaption></figure>


---

# 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/the-lacuna-wallet/overview.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.
