> 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/connected-sites.md). # Connected sites How websites connect to Enclave, what they can ask for, what SureSign refuses, and the full list of services the wallet itself talks to. Enclave lets Kaspa and Igra websites *ask* your wallet to connect, sign a message, or sign a transaction. Nothing is shared and nothing is signed until you approve it in Enclave, and every signature passes through the same SureSign review as your own actions. ## Connecting When a site asks to connect, Enclave shows the request with the site's origin and the account and network it would see. An Igra site's card also asks what balance it should see: **KAS across Kaspa and Igra** (the default for a new site) or **iKAS only**; see [Igra](/argon-docs/using-enclave/igra.md#what-igra-dapps-see). **Connect** grants it; **Reject** refuses. The grant lets the site see your address on that network and ask for signatures; each signature is still a separate review. Grants are bound to the exact origin and expire after 24 hours unless renewed by the site with your approval. For Igra sites, the combined figure includes iKAS and spendable Kaspa KAS before fees. WiKAS stays separate: unwrap it in Exchange first if a site needs a native iKAS payment. Any automatic bridge funding still appears in SureSign and must fit your bridge limit. While the wallet is locked a site request waits. Unlock and the request is presented. Connected sites are listed under **Menu → Connected sites** (Compact) and **Settings → Connections** (Studio), each with a **Forget** control to revoke it. ## What a Kaspa site can ask Enclave implements the KIP-12 provider standard for Kaspa websites. The methods a site can use: | Method | What it does | Approval | | ------------------------------------- | ---------------------------------------------------------- | --------------------------- | | Connect, disconnect, request accounts | Learn your address on the current network | Connect prompt | | Chain id, public key | Read the network and the public key of the granted address | After connecting | | **Sign message** (`signPersonal`) | Sign text to prove ownership; no KAS moves | SureSign review, every time | | **Sign PSKT** | Sign your inputs in a transaction the site assembled | SureSign review, every time | Anything else in the standard, including opaque "send" and "sign transaction" calls where the wallet would be asked to sign bytes it cannot read, is refused as unsupported. A site never receives a signature without a review you approved, and never receives a key, a seed, or anything derived from one. **PSKT rules.** SureSign signs only the inputs you list, only if the wallet controls them, only with `SIG_HASH_ALL`; every other input stays byte-for-byte as the site provided it, and the review shows the entire transaction so you see what you are joining. Change is recognized as yours only if SureSign derived it; a site cannot label an output as your change. ## What an Igra site can ask Igra websites see an Ethereum-style provider. Enclave answers **read** calls (chain id, balances, contract reads, receipts, logs, gas estimates) from your configured Igra endpoint after the site has connected. Two write calls are supported, both through SureSign: | Method | What it does | | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Send transaction** (`eth_sendTransaction`) | SureSign explains recognized contract calls. A structurally valid unknown call requires explicit approval of its unknown effects. Malformed, unsupported, stale, or unsuccessfully simulated calls are refused. Signed calls are carried inside a Kaspa transaction and broadcast through Kaspa. | | **Sign message** (`personal_sign`) | Sign text to prove ownership of your Igra address. | Refused, always: raw signing (`eth_sign`), typed-data signing, signing without sending, submitting pre-signed transactions, adding chains, batching calls, and adding tokens through the provider. Switching chain is accepted only to the Igra network that matches the wallet's current network (chain 38833 on mainnet, 38836 on testnet-10). ## WalletConnect Studio can pair with Igra dApps over WalletConnect (**Settings → Connections → WalletConnect**), for sites that use it instead of an injected provider. Pairing only establishes the channel; every send still becomes a SureSign review, and the WalletConnect keys are not a signer. ## Injection Enclave places its provider on every `https://` page (and on localhost, for developers) so that a dApp can find it. The provider is a courier: it forwards requests to the extension and returns answers. It cannot read your wallet, and the extension never places secrets in a page. Enclave does not impersonate other wallets' globals. ## What Enclave connects to These are the services the wallet itself reads from or broadcasts through. Chrome shows them at install as host permissions. Pasting a different endpoint under Settings asks Chrome for permission to that one host at the moment you do it. | Purpose | Hosts | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Kaspa nodes (mainnet, testnet-10) | `luna.kaspa.blue`, `muon-10.kaspa.blue` | | Public Kaspa index (address discovery, transaction lookup, network pulse) | `api.kaspa.org`, `api-tn10.kaspa.org` | | KRC-20 indexer | `api.kasplex.org`, `tn10api.kasplex.org` | | KRC-721 indexers and artwork | `krc721.kat.foundation`, `krc721-api.kat.foundation`, `krc721-testnet.kat.foundation`, `krc721-tn10api.kat.foundation`, `images.kat.foundation` | | KNS names | `api.knsdomains.org` | | INS names | `insdomains.org` | | Igra endpoints, explorers and token icons | `rpc.igralabs.com`, `galleon-testnet.igralabs.com`, `igra-node.kat.foundation`, `explorer.igralabs.com`, `explorer.galleon-testnet.igralabs.com`, `attester-dashboard.igralabs.com`, `igralabs.com` | | Covenant directory | `kascov.io` | | Kat Bridge quotes and routes | `api.katbridge.com` | | Kaskad markets | `kaskad.live`, `testnet.kaskad.live`, `reactor.kaskad.live` | | Zealous Swap routes and logos | `igra.zealousswap.com`, `cdn-zealous-swap.fra1.cdn.digitaloceanspaces.com` | | Testnet-10 native Zealous markets and launches. Note discovery may send the selected public address, owner hash and public key; no secrets or remote signing authority. | `kaspa-tn10-api.zealousswap.com` | | Markets discovery and KRON trade state. Token and LP lookup sends the chosen trader address. Explicit launch publication sends your reviewed public metadata, creator public key and listing signature. | `api-defi.kaspa.com`, `api.kron.technology`, `idx.kron.technology` | | Consensus name discovery and record deposits. Names and owner addresses are public lookup inputs; proofs are checked on your Kaspa node. | `api.dotk.name`, `api-tn10.dotk.name` | | KatPool workers | `app.katpool.com` | | KRC-20 token logos | `kaspa-lens.com` | | Prices, for the Enclave fee and quotes | `api.coingecko.com` | | WalletConnect relay | `*.walletconnect.org`, `*.walletconnect.com` | | Your own node or indexer | `localhost`, `127.0.0.1`, `[::1]` | Explorer and documentation links open in a new tab and need no permission. None of these services receives your keys, your seed, or any secret; each receives only what it needs to answer (an address to look up, a transaction to broadcast). What each one can infer about you is described in the [Privacy Policy](/argon-docs/legal/privacy-policy.md).