> 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/accounts-and-networks.md).

# Accounts and networks

Accounts under one recovery phrase, the mainnet and testnet-10 networks, and how addresses are derived and discovered.

## Accounts

One recovery phrase can hold many **accounts**. Each account is a separate set of Kaspa addresses, its own Igra address, and its own Deal Desk address, all derived deterministically from the same phrase. Accounts are useful for keeping purposes apart: a spending account and a savings account, or one account per business.

* **Active account.** Compact: **Menu → Node & network → Account**. Studio: **Settings → Network → Account**. The whole wallet (balances, Activity, Holdings, Deal Desk) follows the active account.
* **Create account.** Adds the next account in sequence. Enclave never skips numbers, so restoring the phrase elsewhere and creating the same number of accounts recovers the same addresses.
* **Rename.** Labels are stored on this device and never written on chain.

Account numbers begin at 0. Restoring a phrase restores account 0; if you had more, create them again and Enclave discovers their addresses.

### How addresses are derived

Enclave follows the standard Kaspa derivation used by the reference wallet, so a phrase created here can be restored in other standards-following Kaspa wallets and vice versa.

| Purpose                                                                    | Path                             |
| -------------------------------------------------------------------------- | -------------------------------- |
| Kaspa receive addresses                                                    | `m/44'/111111'/{account}'/0/{i}` |
| Kaspa change addresses                                                     | `m/44'/111111'/{account}'/1/{i}` |
| Igra address (one per account)                                             | `m/44'/111111'/{account}'/2/0`   |
| Deal Desk identities (named, one active per account; the first is `…/3/0`) | `m/44'/111111'/{account}'/3/{n}` |

New wallets use 24 words. Restoring accepts 12 or 24, with an optional BIP39 passphrase. Enclave derives only along this path; a phrase whose funds sit on the legacy pre-2022 Kaspa path (`m/44'/972/…`) should first be moved with a wallet that supports it.

### Discovery on restore

After a restore, Enclave scans receive and change addresses in windows of 20 along each account, widening the scan with the public Kaspa index's record of addresses that have ever been used, so that a spent address in the middle of a run does not hide later ones. Balances themselves always come from the node.

## Networks

Enclave operates on two Kaspa networks. Each has a matching Igra network, chosen automatically.

| Kaspa          | Igra                       | Address prefix | Purpose                      |
| -------------- | -------------------------- | -------------- | ---------------------------- |
| **mainnet**    | Igra mainnet (chain 38833) | `kaspa:`       | Real value                   |
| **testnet-10** | Igra Galleon (chain 38836) | `kaspatest:`   | Testing with free test coins |

Switch under **Settings → Network → Kaspa → Network**. Switching changes every endpoint (node, Igra, indexers) to that network's defaults and shows that network's balances and record; nothing is signed by switching. Addresses are the same keys with a different prefix, so a `kaspatest:` address and a `kaspa:` address for the same account are the same key on different networks. Never send mainnet KAS to a `kaspatest:` address or the reverse: Enclave refuses an address whose prefix does not match the current network.

Other Kaspa networks (testnet-11, devnet, simnet) are recognized by name but not operated: SureSign has no consensus parameters pinned for them, so it refuses to plan on them.

## Endpoints

Where the wallet reads for each network is under **Settings → Network**; see [Settings](/argon-docs/using-enclave/settings.md#network). The defaults are a managed public node and the protocols' own indexers; you can point Enclave at your own Kaspa node over loopback, at any node you trust, and at alternative indexers. Whatever you choose, SureSign treats every answer as untrusted input to be checked against the transaction it builds.