> For the complete documentation index, see [llms.txt](https://extension-doc.rocky.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://extension-doc.rocky.exchange/using-the-wallet/home-and-assets.md).

# Home and Assets

Home is the starting point for checking the selected account, viewing assets, and opening everyday wallet actions.

## Read the balance card

* **Total Balance** is the estimated USD total for assets that have an available price quote. It is not a ledger balance by itself; use the quantity beside each asset to see how many tokens the account holds.
* The address below the balance identifies the selected Canton party. A complete Party ID has the form `<party-name>::<fingerprint>`. A fingerprint commonly begins with `1220`.
* To keep the Home card readable, Rocky Wallet preserves the party name and shortens only the fingerprint, for example `party-name::1220...last4`. Select the copy control to copy the complete Party ID, not the shortened label.

> **Price note:** A displayed `$0.00` can mean that Rocky Wallet does not currently have a price quote. It is not proof that the token quantity is zero or that the asset has no value.

## Use the Home actions

* **Send** opens the asset picker and transfer workflow.
* **Receive** shows the selected account's full Party ID and QR code.
* **Assets** lists configured assets, their ledger quantities, and available USD estimates. Select a sendable asset to start a transfer with that asset selected.
* **History** shows received assets, outgoing transfers, transfer-fee legs, and failed incoming records reported for the selected account.
* **Offers** shows incoming transfers that require a decision. Its badge counts pending, unexpired offers.
* **Settings** contains the account selector, Address Book, security controls, network information, language, and Extension version.

## Understand asset labels

Rocky Wallet keeps a normal ledger symbol such as `CC`, `CBTC`, or `USDCx` beside a quantity. If a Token Standard ledger symbol is instead the raw instrument ID, the Extension uses the configured display alias for the quantity label. A descriptive alias does not replace a normal symbol.

This distinction helps preserve the ledger-provided symbol while making instrument-ID-shaped labels readable. The asset must still have an exact configured identity before it becomes actionable.

## Refresh the current wallet view

From the top of any bottom-navigation page - **Home**, **History**, **Offers**, or **Settings** - pull down and release to refresh the current wallet view. Wait for the refresh indicator to finish before evaluating the result.

A refresh requests the data needed by the current view. Network or service failures can leave the previous snapshot on screen and show an error, so a gesture does not guarantee that every requested data source succeeded. If the result remains uncertain, compare the relevant transaction or offer with the ledger-facing record.

Next: [Supported Assets](/reference/supported-assets.md)


---

# 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://extension-doc.rocky.exchange/using-the-wallet/home-and-assets.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.