> 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/introduction/what-is-lacuna.md).

# What Is Lacuna?

A non-custodial privacy wallet for everyday on-chain activity.

Lacuna is a non-custodial privacy wallet for everyday on-chain activity. It uses zero-knowledge proofs and a shielded pool so your balances and transactions stay confidential while you keep full control of your own keys.

Most wallets broadcast everything: who you are, what you hold, who you pay. Lacuna breaks that link. Funds you deposit enter a shielded pool, and everything you do from there, transfers, swaps, bridging, agentic payments are verified with cryptographic proofs instead of public, traceable transactions.

## What Makes It Different

* **Non-Custodial**\ <mark style="color:$info;">Keys are generated and stored only on your device. Lacuna never holds your funds.</mark>
* **Mobile-First**\ <mark style="color:$info;">Built as a native mobile app, not a browser extension.</mark>
* **Private By Default**  \ <mark style="color:$info;">Shielding, transfers, and swaps are confidential out of the box.</mark>
* **Selective Transparency**  \ <mark style="color:$info;">Share a read-only viewing key when</mark> <mark style="color:$info;"></mark>*<mark style="color:$info;">you</mark>* <mark style="color:$info;"></mark><mark style="color:$info;">choose to prove your activity.</mark>

## Who It's For

Everyday users who don't want their net worth public, traders who want to avoid being front-run, builders who need a privacy layer, and autonomous agents that pay each other on-chain.


---

# 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/introduction/what-is-lacuna.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.
