> For the complete documentation index, see [llms.txt](https://privacyoncoil.gitbook.io/coil-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://privacyoncoil.gitbook.io/coil-docs/developers-and-support/recommended-application-design.md).

# Recommended Application Design

Making the private transaction lifecycle clear in your app.

An application integrating privacy infrastructure should make the transaction lifecycle understandable.

### Recommended interface states

| State                           | What the interface should explain                             |
| ------------------------------- | ------------------------------------------------------------- |
| Synchronizing                   | Wallet activity is still being scanned or updated.            |
| Awaiting approval               | A token permission or wallet confirmation is required.        |
| Preparing                       | Transaction inputs and costs are being assembled.             |
| Generating proof                | Local or configured proving work is in progress.              |
| Awaiting submission             | The transaction is ready but has not been broadcast.          |
| Submitted                       | A transaction hash exists and confirmation is pending.        |
| Confirmed                       | The blockchain has accepted the transaction.                  |
| Restricted or pending assurance | Additional conditions affect spendability.                    |
| Failed                          | The failure stage and appropriate next action are identified. |

These are recommended interface concepts, not a list of official SDK status identifiers.

### Handling private data

The application should preserve the distinction between a public transaction hash and private wallet data. Error reports should not automatically include keys, decrypted transaction histories or unnecessary account information.

### Retries

Retries should be designed carefully. Users need to know whether they are retrying proof generation, requesting another broadcaster quote or submitting another blockchain transaction.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://privacyoncoil.gitbook.io/coil-docs/developers-and-support/recommended-application-design.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.