> 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/transfer.md). # Transfer Send KAS, KRC-20 tokens, and Igra assets; fee controls, coin control, batch sends, and two-step actions. Transfer sends what you hold. Compact has it in the dock; Studio has it on the rail, and every Holdings row offers **Send** for its own asset. Use the **Asset** selector to choose KAS or a transferable token in your account. KAS is one entry for both layers: type a `kaspa:` address or `.kas` name and it leaves as KAS on Kaspa; type an `0x` address or `.igra` name and it leaves as iKAS on Igra. Enclave never guesses from anything else. Collectibles have their own transfer action in **Collectibles** and do not appear in this picker. In Compact, the recipient comes first; QR and payment-link shortcuts are under **Fill from a payment request**. Use **Contacts** beside any address field to pick a person, then one of their saved wallets. Wallets the field cannot take are shown with the reason. Names are private display hints; SureSign keeps the full destination visible. See [Contacts](/argon-docs/using-enclave/contacts.md). ## Send KAS 1. Enter a **recipient**: any Kaspa address (Schnorr `kaspa:q…`, ECDSA `kaspa:qyp…` as used by Tangem and many exchanges, or a program address), a `.kas` name, or a payment link. Studio can **Scan QR**; Compact can paste a **Payment URI** or read one from an **Image** or the **Camera**. 2. Enter an **amount**, or **Send max**. 3. Choose **Plan review** and read the SureSign review. See [Your first transaction](/argon-docs/start-here/first-transaction.md). **Names.** A `.kas` name is resolved through the KNS indexer and the resolved address is shown beside it. Enclave resolves the name again at the moment you approve; if the answer has changed, the flow stops rather than sending to the new answer. **Several recipients.** **Add recipient** puts more than one payment in a single transaction. Enclave warns that a batch links those recipients on chain, and SureSign warns again at review. ### Fee The default, **Network minimum**, pays exactly Kaspa's relay minimum for the transaction's mass, computed by SureSign at review. **Custom** (Studio: **Custom floor**) lets you set a higher fee floor for busy periods. Fees are per mass, so a transaction spending many small Notes costs more than one spending a single Note. See [Fees](/argon-docs/using-enclave/fees.md). ### Coin control By default SureSign chooses which Notes to spend: it prefers a single Note that covers the amount, then Notes from the same cluster, and only then joins clusters. You can take over: * **Choose Notes** opens the selection; Notes you froze in [Note Management](/argon-docs/using-enclave/notes.md) are never spent automatically. * **Use only selected** (Studio: **Strict · only these**) spends exactly the Notes you chose and fails if they do not cover the amount. * **Prefer selected** (Studio: **Preferred · top up if short**) starts with your selection and tops up from other unfrozen Notes if needed. * **Use automatic selection** returns control to SureSign. The default mode is set under **Settings → Privacy → Note selection default**. {% hint style="info" %} **"Kaspa will not carry a Note this small next to your change."** Kaspa's storage-mass rule (KIP-9) makes a transaction that leaves a very small output beside a large change output disproportionately expensive. When SureSign meets this, it stops and explains instead of quietly inflating the fee. Send a larger amount, or use **Send max** to move the whole Note. {% endhint %} ## Send a KRC-20 token Choose the token from **Transfer → Asset**, or open it from **Holdings** and choose **Send**. KRC-20 balances live on specific Kaspa addresses of your account, so the form shows **Send from**: all lots, or one custody address. A KRC-20 transfer is a **two-step action**: a *commit* transaction that funds a small script output, then a *reveal* transaction that carries the inscription. SureSign plans both, you approve once, and the two are signed in order with the second waiting for Kaspa to recognize the first. The commit needs a little KAS on the custody address; if there is none, the form offers **Add KAS**. KRC-20 transfers pay no protocol fee, only the miner fee for the two transactions. Minting and deploying pay Kasplex's protocol fees; see [Holdings](/argon-docs/using-enclave/holdings.md#mint-and-deploy). ## Send on Igra Choose **KAS** and give an Igra recipient — an `0x…` address or a `name.igra` INS name — or choose an ERC-20 token or ERC-721 collectible from the asset selector, Holdings or Collectibles. Before you plan, the form says what SureSign will bridge from Kaspa for this amount (*about N KAS*), or why it would refuse: more than this account holds, or more than your automatic bridge limit. If you give a Kaspa recipient while all your KAS is on Igra, the form points you at Exchange to bring iKAS back as KAS; Enclave never bridges out on its own. Every Igra write is carried inside a Kaspa transaction: SureSign builds the EVM transaction, signs it with this account's Igra key, and wraps it in a Kaspa L1 carrier that you review like any other Kaspa transaction. The review shows both lanes: the KAS the carrier costs on Kaspa, and the iKAS that moves on Igra. The iKAS **available** figure counts iKAS, WiKAS and the spendable KAS on Kaspa together (the info glyph beside it says what is included); **Max** fills the most one send can ask for across both layers: your iKAS and WiKAS plus what Kaspa can bridge within your automatic bridge limit, keeping 1.5 KAS back for the bridge's fee and the carrier. If your Igra address does not hold enough iKAS for the action and its gas, SureSign first unwraps WiKAS you hold, then bridges the rest from Kaspa through Igra's permissionless entry (sized to the shortfall, never below 10 KAS, never above your [automatic bridge limit](/argon-docs/using-enclave/igra.md#automatic-bridge-limit)), each shown as its own step in the same approval. See [Igra](/argon-docs/using-enclave/igra.md). Transfers to the token's own contract, or to a collection's contract, are refused before review. ## Two-step actions Some actions are two Kaspa transactions by nature: KRC-20 and KRC-721 mints and transfers (commit, then reveal), and Igra actions that need a token approval first (approve, then act). SureSign plans the whole sequence as one **package** and you approve it once. The review's headline says how many steps there are and the progress track shows each. The second step waits until Kaspa has accepted the first and, for Igra, until Igra has executed it. If the window is closed or the browser stops in between, the package is not lost: Home shows **Unfinished packages** and offers to finish it. A partly signed package is never re-approvable; finishing it uses the approval you already gave, for the steps you already read. ## After you send The progress track shows Broadcast → Accepted → Confirmed (10 confirmations). *Accepted* is your node's word: the moment it drops the Notes you spent. The count then ticks against your node's live sink blue score, so it moves at Kaspa's pace — about ten a second — and the public index's exact accepting score replaces the node's estimate as soon as it arrives. Igra actions add a fourth beat that waits for Igra to execute. The movement appears in [Activity](/argon-docs/using-enclave/activity.md) with every fee, Note, and identifier, and **Kaspa explorer** opens it on the public explorer.