> For the complete documentation index, see [llms.txt](https://docs.arcan.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcan.finance/sdk/decrypt.md).

# Decrypt

The SDK opens a handle for an account that the access list allows. The plaintext stays in the app. It is not written back to Robinhood unless the contract submits a public decrypt on purpose.

## User decrypt

```ts
const balanceHandle = await token.confidentialBalanceOf(userAddress);
const clear = await arcan.userDecrypt(balanceHandle, tokenAddress, userAddress);
```

`clear` is the amount. Show it in the wallet that owns `userAddress`. A different account gets a rejected decrypt, even if it can read the handle from chain state.

The user and the contract both need persistent access. `FHE.allow` on the user and `FHE.allowThis` on the contract are the usual pair.

## Public decrypt

Only for handles the contract has marked with `FHE.makePubliclyDecryptable`.

```ts
const clear = await arcan.publicDecrypt([handle]);
```

To consume that cleartext in a contract, submit it with the decryption proof and call `FHE.checkSignatures`. Keep the handle order identical to the SDK request.

## Display

Wallets that are not allowed to decrypt should render `****`. Do not replace that with zero. Zero is a real amount. The asterisks mean the number is sealed.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.arcan.finance/sdk/decrypt.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 `build a script that syncs our docs to a CMS` 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.