stx_transferSip10Ft

Request a transfer of a SIP-010 fungible token to a specified recipient.

Method name

stx_transferSip10Ft

Leather builds a call to the token contract's transfer function and attaches its own post-condition: the sender sends exactly amount of asset. The request's postConditions and postConditionMode are not applied. The transfer carries no memo.

Parameters

Parameter	Description	Required	Type
recipient	Stacks c32-encoded address of the recipient	✅	string
asset	Fully qualified token identifier, as <contract address>.<contract name>::<token name>	✅	string
amount	Amount in the token's smallest unit	✅	number | string
address	Stacks address to send from. Defaults to the active account	❌	string
network	Network identifier	❌	string
fee	Transaction fee in microSTX	❌	number | string
nonce	Transaction nonce	❌	number | string
sponsored	Build a sponsored transaction	❌	boolean

Example request

try {
  // Request an sBTC transfer
  const response = await window.LeatherProvider.request("stx_transferSip10Ft", {
    recipient: "SP3TB3AJ0XMZ9S6CGY2CQ6R06H1Z6DJQ1SH15ZP2H",
    asset: "SM3VDXK3WZZSA84XXFKAFAF15NNZX32CTSG82JFQ4.sbtc-token::sbtc-token",
    amount: "1000", // 1,000 sats (sBTC has 8 decimals)
  });

  console.log("Response:", response);
} catch (error) {
  console.log("Request error:", error);
}

Example Response

{
    "jsonrpc": "2.0",
    "id": "d3f1a7b0-5e6c-4f18-92a4-8e3b9f7c5c71",
    "result": {
        "txid": "f9c2a8f1e3b1d5a7c8e2f6a9d4b3e1c7f2a5d9b8c6e4f1a3b7d2e9c5f8a1b6c3",
        "transaction": "dead...beef"
    }
}

When the active account is a multisig policy, the transaction is proposed to the co-signers rather than broadcast. The result then carries status: "proposed" and a proposalId, and txid stays empty until the co-signers complete and broadcast it.