> 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/capacity-protocol/wallet-integration-status.md).

# Wallet Integration Status

Model A requires a wallet-supported authorization path. The required result is one transaction that a user can review, balance, sign and submit without transferring NIGHT custody.

## Expected connector flow

1. The dApp creates an intent containing the redesignation and a NIGHT output.
2. The wallet balances the transaction.
3. The holder reviews and signs it.
4. The signed transaction is submitted.
5. Ura observes the external receiver relationship and resulting capacity.

## Acceptance test

The path is considered supported only after one fresh Preprod transaction is built, balanced, wallet-signed, submitted and observed at the requested receiver.

## Current blocker

Existing wallet/SDK feedback says the generic balancing APIs should support the flow, but the flow is not currently tested end to end. Lace connector and native DUST-registration failures have also been observed on Preprod.

Ura is seeking direct technical coordination with wallet and DApp Connector owners. No unsupported workaround is treated as completion.


---

# 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/capacity-protocol/wallet-integration-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.