> For the complete documentation index, see [llms.txt](https://docs.redact.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redact.money/using-redact/confidential-balances-wallet.md).

# Confidential Balances (Wallet)

Redact has a built in wallet that can be used to:

1. View your token balances as a breakdown between public and confidential balances.
2. View your past transactions (including confidential transactions).
3. Transfer encrypted tokens between wallets.&#x20;

The wallet can be opened by pressing the **CONNECT** button in the top right corner of the dApp. If you are already connected, the button will display your connected wallet address instead:

<figure><img src="https://3289548442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBtZLqCP6brcfNsL0LJh%2Fuploads%2F1I7MYUdpGKNAmFy88ORT%2FToken%20Balance.png?alt=media&amp;token=63cc86f3-9dc6-4197-ab4a-56495a77f7f1" alt=""><figcaption></figcaption></figure>

Once open, you will see your native token balance, as well as a list of ERC20 tokens. Each token in the list shows the breakdown of public vs confidential balance. The history tab shows a list of all transactions that have been executed in Redact.

<figure><img src="https://3289548442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBtZLqCP6brcfNsL0LJh%2Fuploads%2FV8Wkzsa9LWf7HmmRN67z%2Fbalance%20and%20transaction.png?alt=media&amp;token=8bee349a-1da1-426d-b8f9-c70706748746" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note that ETH/WETH are combined in this view. Both ETH and WETH are encrypted into the same confidential token **eETH** so they have been combined in the token list.

You can read more about ETH/WETH in the [ConfidentialERC20.sol](https://docs.redact.money/architecture/confidentialerc20.sol.md)page.
{% endhint %}

Each of the rows in this list can be expanded to view the individual balances and claimable amounts for each token. As an example, lets open the LINK token page:

<figure><img src="https://3289548442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBtZLqCP6brcfNsL0LJh%2Fuploads%2F0X9pqUfuz5x8PrzWeVUx%2Ftoken_page.png?alt=media&amp;token=5c39e383-d4cf-4345-82ed-c4e8fba4477c" alt=""><figcaption><p>LINK token page</p></figcaption></figure>

This page shows the encrypted balance (5 eLINK), public balance (16 LINK), and claimable balance (3 LINK).&#x20;

The encrypted balance, 5 in this case, is a value that is ***only*** visible to the owner of the account. In order to view this data, it is fetched from the CoFHE coprocessor as a `sealed` value (meaning it is still in an encrypted state, but it can be unsealed locally within Redact), and then `unsealed` locally using an autogenerated Permit.


---

# 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://docs.redact.money/using-redact/confidential-balances-wallet.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.
