> 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/features-and-products/private-swaps.md).

# Private Swaps

Swap tokens privately, without being front-run.

Swap one token for another directly from your shielded balance without exposing the trade to front-running bots or revealing your position.

## Why Private Swaps

Public DEX trades sit in the mempool before they confirm, where bots can see and trade against them. Swapping from inside the shielded pool removes that exposure: your intent isn't broadcast in a linkable, public way.

## How It Works

You swap shielded funds, the proof confirms you hold them, and the output returns as a new shielded note all without unshielding to a public address first.


---

# 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/features-and-products/private-swaps.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.
