> 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.md). # Privacy Bridge The Mithril-gated Cardano-to-Midnight bridge, state machine and receipt model. The Ura Privacy Bridge is the first reference application of Ura's shared Midnight infrastructure. Its current proven route is ADA/tADA from Cardano Preprod into a shielded Midnight-side claim flow. ## Verified state flow 1. A user submits a normal Cardano transaction. 2. Ura detects the deposit and records it in the bridge state machine. 3. The bridge waits for Mithril certification; transaction detection alone is not accepted as final proof. 4. After certification, Ura submits the bounded Midnight credit through the warm operator. 5. The Midnight indexer confirms the credit. 6. The deposit reaches **CLAIMED** and a receipt is available. ## Trust boundary Mithril is the Cardano-side certification gate. The bridge does not treat a merely observed transaction as sufficient evidence for the strict path. The Midnight submission and confirmation phase is separate from Cardano certification. This separation keeps failures classifiable and prevents an observed Cardano transaction from being confused with a completed Midnight claim. ## Measured Preprod baseline The last strict measured run spent about **52.9 minutes** waiting for Mithril certification and about **2.8 minutes** on Midnight submission and confirmation. Across observed runs, certification was typically about 47–60 minutes. A faster target is pending a Mithril deployment correction and fresh end-to-end measurement. It is not yet a measured result or service-level commitment. ## Scope * Current proven route: ADA/tADA on Preprod. * Future routes: ETH, XRP, SOL and BNB. * Future routes are roadmap items, not current support. --- # 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.md?ask=&goal= ``` `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.