> For the complete documentation index, see [llms.txt](https://whitepaper.lacunalabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.lacunalabs.io/introduction/what-is-lacuna.md).

# What Is Lacuna?

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, agent payments — is verified with cryptographic proofs instead of public, traceable transactions.

## What Makes It Different

* **Non-Custodial** — keys are generated and stored only on your device. Lacuna never holds your funds.
* **Mobile-First** — built as a native mobile app, not a browser extension.
* **Private By Default** — shielding, transfers, and swaps are confidential out of the box.
* **Selective Transparency** — share a read-only viewing key when *you* choose to prove your activity.

## 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whitepaper.lacunalabs.io/introduction/what-is-lacuna.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.