> 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/known-limitations-and-roadmap.md).

# Known Limitations & Roadmap

## Current limitations

* Preprod only.
* Generalized wallet redesignation signing unresolved.
* Current bridge latency dominated by Mithril certification cadence.
* Public request schema and verifier not finalized.
* Multi-operator failover and production reliability not proven.
* No production SLA, audit claim or mainnet claim.

## Next bounded milestones

1. Prove one supported-wallet Model A transaction end to end.
2. Retest strict bridge timing after the Mithril configuration deployment.
3. Finalize canonical request identity, nonce, expiry and terminal status.
4. Publish a bounded partner integration and receipt-verification path.
5. Run a shadow multi-provider market before a capped pilot.
6. Add independent operator routing only after accounting invariants remain intact.

## Future layers

Shielded routing, DEX liquidity, broader assets and cross-chain aggregation remain future layers. They are not current support claims.


---

# 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/known-limitations-and-roadmap.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.