> 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-bridging.md).

# Private Bridging

Private crypto bridging across chains without exposing a public link between source and destination wallets.

Private bridging lets you move crypto across chains without creating a public trail between your wallets. Lacuna routes cross-chain transfers through the shielded pool, so observers cannot map your source address on one network to your destination address on another.

## Why public bridges leak privacy

Most crypto bridges create a visible cross-chain link. The source address, destination address, asset, amount, and timing are easy to correlate. That makes standard blockchain bridging bad for wallet privacy, portfolio privacy, and cross-chain activity privacy.

## How private bridging works

Lacuna shields funds before they move across supported chains. Zero-knowledge proofs verify the transfer without publishing a one-to-one address mapping. You still bridge assets cross-chain, but the bridge does not leave a simple public connection between your wallets.

## Why use private bridging

* Keep your cross-chain transfers private.
* Reduce address clustering across chains.
* Move assets without exposing a direct wallet-to-wallet trail.

See [Multi-Chain Coverage](/x402-and-the-agent-economy/multi-chain-coverage.md) for supported networks.


---

# 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-bridging.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.
