> For the complete documentation index, see [llms.txt](https://argon-4.gitbook.io/argon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argon-4.gitbook.io/argon-docs/using-enclave/holdings.md).

# Holdings

Holdings: every position in one register, KAS and Igra alike, with the actions each one allows and the tools to mint and deploy.

Holdings lists everything this account holds on the current network as one register: KAS, iKAS, KRC-20 tokens, Igra ERC-20 tokens, and covenant tokens the wallet recognizes.

Compact: **Assets → Holdings**. Studio: **Holdings** on the rail.

## The register

Each position shows its symbol, balance, and where it lives: **Kaspa** for KAS and KRC-20, **Igra** for iKAS and ERC-20. On the Markets branch, opening a row leads to the same token page used by Exchange. It shows the exact identity, precision, holding source and available actions. Matching symbols never merge different contracts or covenant IDs.

Balances have two kinds of authority and Holdings says which:

* **KAS and iKAS** come from the Kaspa node and the Igra endpoint.
* **Tokens** use protocol indexers and chain reads. If a source cannot refresh, Enclave retains its last observation with an unavailable-source indication. An unobserved amount remains unavailable.

## Actions

Token pages offer **Transfer**, **Buy**, **Sell** or **Exchange** when the wallet knows a supported route and amount precision. **Find exchange route** checks available token and bridge routes for that exact asset. Covenant tokens open their dedicated inspection and supported operations. Watch-only holdings remain visible without spending actions.

The action opens the existing form with the asset selected. Preparing a transaction still requires fresh checks and a SureSign review. Staking and unstaking remain under [Earn](/argon-docs/using-enclave/earn.md); receipts remain under [Activity](/argon-docs/using-enclave/activity.md).

### Send from a specific address

KRC-20 balances are recorded against particular Kaspa addresses of your account. The send form shows **Send from** with each address that holds the token and its balance, or **All addresses**. Because a KRC-20 transfer is a commit followed by a reveal, the sending address needs a little KAS to fund the commit; if it has none, **Add KAS** moves some there first.

## Mint and deploy

Enclave can create tokens and collections as well as hold them. Holdings ends with **Token tools**, which opens [Tools → Token tools](/argon-docs/using-enclave/tools.md#token-tools): **Mint tokens** and **Create a token**, each with its choice of protocol. Collectibles ends with **Collectible tools** in the same way. Every form is a SureSign review; the protocol fees are listed there.

## Covenant tokens

The qualified KCC20 program supports creating a fixed-supply token, transfers, consolidation and receive settings. Creation records a name or ticker, decimal precision and one to three initial allocations. SureSign shows the exact token amounts, KAS held by the cells and network fee before signing. There is no later minting or administrator access.

Locally created and received cells are recovered from the encrypted journal and checked against the selected Kaspa node, so discovery can continue while the directory catches up. A saved record by itself is not a balance. Foreign covenant programs remain view-only until their exact program is qualified; directory labels and metadata never grant signing authority.

## Empty state

A fresh account shows **No balances yet** with a shortcut to Deposit. Positions appear as the node and the indexers report them.