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

# private bridging

*Cross-chain, without the trail.*

Moving funds between chains is both the riskiest and the most exposing thing most users do on-chain.

## Why bridging is risky and exposing

Bridges have been among the largest theft targets in the industry's history, and a cross-chain move is highly legible: it links an address on one chain to an address on another, often with matching amounts and timing. That link is exactly what de-anonymises users.

## Lacuna's private bridging approach

Lacuna does not run its own bridge. Instead it wraps established, audited bridges with private endpoints on each side — shielding the entry on the source chain and the exit on the destination. You gain cross-chain privacy while relying on infrastructure that is already battle-tested.

*Fig. 7 — Lacuna adds privacy at the entry and exit; the cross-chain transfer itself runs over proven, audited bridge infrastructure.*

## Security model

The approach is deliberate: the hardest and most dangerous part of bridging — moving value across chains safely — is left to specialised, audited systems, while Lacuna adds the privacy layer at the points it controls. Less new attack surface, more proven security.


---

# 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://docs.lacunalabs.io/private-bridging.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.