> 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/how-lacuna-works/shielded-pools.md).

# Shielded Pools & The Anonymity Set

Where the privacy actually comes from.

A shielded pool is a shared, on-chain pool of private notes. Privacy comes from the crowd: the more deposits and users share a pool, the larger the **anonymity set** the set of deposits any given withdrawal could plausibly have come from.

## The Idea

* Everyone shields into the same pool.
* Withdrawals and transfers are proven with zero-knowledge proofs.
* Because outputs aren't linked to inputs, an observer can't tell which deposit funded which spend.

A larger anonymity set means stronger privacy for everyone in it.

> **Roadmap:** Growing the anonymity set and the underlying Merkle-tree commitment structure is an active priority see the [Roadmap](/resources/roadmap.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/how-lacuna-works/shielded-pools.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.
