> 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/evidence-and-status.md).

# Evidence & Status

Measured Preprod evidence, dated milestones, open blockers and roadmap.

Ura separates measured evidence from targets and roadmap items.

## Status labels

| Label                            | Meaning                                                                     |
| -------------------------------- | --------------------------------------------------------------------------- |
| **Proven on Preprod**            | Exercised with network evidence on Midnight Preprod                         |
| **Proven in controlled testing** | Demonstrated in a bounded environment; not generalized                      |
| **Wallet-blocked**               | Protocol path exists, but supported user-wallet authorization is unresolved |
| **Pending retest**               | A dependency changed and a fresh measurement is required                    |
| **Planned**                      | Roadmap direction with no current support claim                             |

## Proven bridge path

Cardano deposit → Mithril certification → automatic Midnight credit submission → indexer confirmation → **CLAIMED** / receipt-ready.

## Proven capacity path

* Bounded Model A external-receiver authorization and receiver-side DUST observation.
* Bounded Model B sponsored execution.
* Warm-operator spend/source reconciliation.
* Local one-click sponsored user experience.

## Open blockers

* Generalized NIGHT redesignation signing through supported wallets.
* Lace/Midnight connector reliability and native DUST-registration issues observed on Preprod.
* Fresh Mithril timing measurement after the deployment-pipeline correction.
* Canonical request identifiers, complete replay/expiry handling and a public verifier.
* Independent multi-operator routing and failover.

## Selected development milestones

* **2 July 2026:** bounded Model A supply feeding Model B execution proven on Preprod; one-click sponsored UX proven locally.
* **16 July 2026:** relayer, delegation, application receipts and provider accounting reviewed as one community-capacity model.
* **July 2026:** strict bridge path reached CLAIMED with automatic Midnight submission and indexer confirmation.
* **25–26 August 2026:** Mithril certificate configuration mismatch identified; deployment-pipeline fix merged, with retest pending.

## Public evidence

* [Ura short demo](https://youtu.be/MqykGwrJlYM)
* [Ura public engineering portfolio](https://docs.google.com/document/d/1iDBxoQjNfm1Ez2Lx4Gw86OKmkZGms-_yd5QTRJTgzLk/edit)
* [Preprod evidence and runbooks](https://drive.google.com/drive/folders/1wDPSsaOzdLEW1LbaDPHX7Magf-VjnmR3)
* [NIGHT redesignation evidence gist](https://gist.github.com/alba-press/ce526cfce098a9970f1ef12daee437db)
* [Mithril activation discussion #3160](https://github.com/IntersectMBO/mithril/issues/3160)
* [Mithril release task #3271](https://github.com/IntersectMBO/mithril/issues/3271)
* [Midnight Wallet SDK DUST-generation guide](https://docs.midnight.network/guides/generating-dust-programmatically)

Additional sanitized transaction identifiers and commit links will be added with the first public GitHub release.


---

# 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/evidence-and-status.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.