> For the complete documentation index, see [llms.txt](https://ura-labs-1.gitbook.io/ura-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ura-labs-1.gitbook.io/ura-documentation/privacy-bridge/how-the-bridge-works.md).

# How the Bridge Works

The strict Ura bridge path keeps Cardano detection, Mithril certification and Midnight confirmation as separate stages.

![Ura Privacy Bridge flow](https://1748825992-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FINAVQvcBCGwClq336pmc%2Fuploads%2F8eZHzXgGVdPHBSqVdQG5%2Fura-privacy-bridge-flow.png?alt=media)

## End-to-end sequence

| Stage              | What happens                                                  | Why it matters                                             |
| ------------------ | ------------------------------------------------------------- | ---------------------------------------------------------- |
| Deposit created    | User submits a Cardano transaction                            | Establishes the source transaction                         |
| Deposit detected   | Ura observes and records the transaction                      | Detection starts tracking but is not finality              |
| Cardano confirmed  | The transaction is sufficiently observed on Cardano           | Prepares the deposit for proof lookup                      |
| Mithril certified  | A valid CardanoBlocksTransactions proof is found and verified | Opens the strict Midnight submission gate                  |
| Midnight submitted | The bounded credit call is sent through the warm operator     | Creates a distinct Midnight transaction                    |
| Midnight confirmed | The indexer observes the expected credit                      | Prevents submit success from being mistaken for settlement |
| Claimed            | The deposit reaches terminal success and a receipt is ready   | Gives the user and operator a final classified result      |

## Failure separation

A Cardano proof delay is not a Midnight submission failure. A submitted Midnight transaction is not a confirmed credit. Keeping these stages separate makes retries and operator intervention safer.

## Current route

The currently proven path is ADA/tADA on Cardano Preprod to Midnight Preprod. Other asset routes remain future work.


---

# 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, and the optional `goal` query parameter:

```
GET https://ura-labs-1.gitbook.io/ura-documentation/privacy-bridge/how-the-bridge-works.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.