> 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/faq.md).

# Questions and answers

Short answers to the questions people ask most about Enclave and SureSign.

## Custody and recovery

<details>

<summary>Who holds my keys?</summary>

You do. The recovery phrase is generated on your device by SureSign, encrypted with your password (or passkey), and stored only in this browser's extension storage. Enclave has no servers and no accounts; the Developer cannot see, recover, freeze, or move anything.

</details>

<details>

<summary>I lost my recovery phrase. Can you help?</summary>

No one can. If the wallet is still unlocked on this browser, open Security → Recovery phrase now and write it down. If the vault is gone and the phrase is gone, the funds are unreachable. This is the nature of self-custody, and it is why Enclave shows the phrase once and reminds you until you confirm the backup.

</details>

<details>

<summary>Can I restore my Enclave phrase in another wallet?</summary>

Yes. Enclave uses standard BIP39 phrases and the standard Kaspa derivation path, so any standards-following Kaspa wallet can restore it. Your Igra and Deal Desk addresses are on dedicated branches of the same path; a wallet that does not derive them will not show those balances, but they are not lost.

</details>

<details>

<summary>Is a passkey a backup?</summary>

No. A passkey unlocks the vault on this device; it does not contain the phrase and cannot restore the wallet elsewhere. Your backup is the written recovery phrase.

</details>

## Signing

<details>

<summary>Why does the Approve button stay disabled?</summary>

You have not reached the end of the review. Scroll to the bottom; the status line changes from *Read to the end to sign* and the button enables. Opening Technical details adds more to read. The gate is deliberate: the review is the contract.

</details>

<details>

<summary>What does "Blocked" on a review mean?</summary>

SureSign could not fully decode the request: an unknown contract or function, an unrecognized covenant template, a signing mode it does not support, or a provider outside its pinned set. Nothing was signed. The action cannot proceed until the request is reduced to terms SureSign understands. See [Fail closed](/argon-docs/suresign/fail-closed.md).

</details>

<details>

<summary>Can a website make me sign something I did not see?</summary>

No. Every signature a site can obtain passes through the same review you read for your own transactions, and the approval is bound to the hash of exactly what is signed. A site can ask; only you can approve.

</details>

<details>

<summary>Why does the review show KAS leaving for an Igra action?</summary>

Every Igra action is carried inside a Kaspa transaction, so the review shows the Kaspa side (the Notes spent, the carrier output, any Enclave fee, your change) as well as the Igra side (the contract call and its effect). *Leaves this wallet* is the KAS that actually leaves your control. See [Igra](/argon-docs/using-enclave/igra.md).

</details>

## Balances

<details>

<summary>What does Spendable count?</summary>

Spendable is your unfrozen Kaspa Notes plus the iKAS Enclave has observed on Igra, counted one to one, because a Transfer to an Igra address can spend either. It leaves out Notes you have frozen, Notes reserved for a package in progress, watch-only balances and the Deal Desk float; each is listed beneath it. Holdings still shows KAS and iKAS as separate facts. See [Home](/argon-docs/using-enclave/home.md).

</details>

<details>

<summary>My tokens disappeared but my KAS is fine.</summary>

Tokens are indexed facts; KAS is a consensus fact. If the KRC-20 or KRC-721 indexer is unreachable or behind, Enclave shows nothing for tokens rather than a stale guess, and Home says so. Your tokens are unchanged on chain. Try again later, or select another replica under Settings → Network.

</details>

<details>

<summary>Why does a received KRC-20 token take longer to appear than KAS?</summary>

KAS appears as soon as your node sees the transaction. A token balance appears when the indexer has processed the inscription, typically a little later.

</details>

<details>

<summary>I restored my wallet and a balance is missing.</summary>

Check that you entered the same BIP39 passphrase, if the wallet had one; a different passphrase is a different wallet. If the funds were on a second account, create the account again under Settings → Network → Account. If the funds sat on an address deep in a run of spent addresses, Enclave's discovery uses the public index to widen its scan; give it a moment and refresh.

</details>

## Fees

<details>

<summary>What does Enclave charge?</summary>

One fee, about US$0.20 in KAS, on the action that opens a position or a covenant: the economic step of an Exchange job, entering an Earn position, creating a vault or escrow. Never on transfers, approvals, withdrawals, claims, or any party who did not open the covenant. It is always a named line on the review. See [Fees](/argon-docs/using-enclave/fees.md).

</details>

<details>

<summary>Why did my swap cost 10 KAS in Enclave fee?</summary>

The fee targets US$0.20 and is clamped between 1 and 20 KAS. When the public price feed is unavailable at planning time, the fee is 10 KAS. The KAS figure on the review is always the amount charged.

</details>

## Privacy

<details>

<summary>Does Enclave track me?</summary>

No. There is no telemetry, no analytics, no crash reporting, no account, and nothing to opt out of. The services the wallet reads from (nodes, indexers, providers, the price feed) see the requests they answer, as described in the [Privacy Policy](/argon-docs/legal/privacy-policy.md).

</details>

<details>

<summary>Why is the wallet asking me to use a fresh address?</summary>

Kaspa addresses are public. Reusing one links every payment to it. Deposit offers a fresh address after each receipt (on by default under Settings → Privacy) so separate requests stay separate. Your old addresses keep working.

</details>

## Compatibility

<details>

<summary>Which browsers?</summary>

Chrome 116 or later and Chromium browsers of the same generation with side panel support. Enclave is a Manifest V3 extension.

</details>

<details>

<summary>Is Enclave a general Ethereum wallet?</summary>

No. Enclave supports Igra, Kaspa's EVM Layer, for the contracts SureSign has pinned and can explain. It does not connect to Ethereum or other EVM chains, and it refuses raw or typed-data signing. See [Igra](/argon-docs/using-enclave/igra.md#what-enclave-deliberately-does-not-do-on-igra).

</details>

<details>

<summary>Where do I get help?</summary>

The feedback board at [enclave.fider.io](https://enclave.fider.io/), <support@onargon.com>, or a direct message to **@argonmining** on X, Telegram, or Discord. For a bridge, swap, pool, or dApp, contact the provider that operates it. Nobody acting for Enclave will ever ask for your recovery phrase.

</details>