Skip to main content

transfer

Creates a transaction and broadcasts it to the network

Request​

ㅤ

If you use multiple addresses in destinations field, make sure there are maximum 1 integrated address involved, or, if "payment id" parameter was specified, then integrated addresses are not allowed.

{
  "id": 0,
  "jsonrpc": "2.0",
  "method": "transfer",
  "params": {
    "comment": "",
    "destinations": [{
      "address": "NnBvJDuQjMG9R2j4WnYUhBYNrwZPwuyXrC7FHdVmWqaESgowDvgfWtiXeNGu8Px9B24pkmjsA39fzSSiEQG1ekB225ZnrMTBp",
      "amount": 10000000000000,
      "asset_id": "cc608f59f8080e2fbfe3c8c80eb6e6a953d47cf2d6aebd345bada3a1cab99852"
}],
    "fee": 10000000000,
    "hide_receiver": true,
    "mixin": 15,
    "payment_id": "1dfe5a88ff9effb3",
    "push_payer": false,
    "service_entries": [{
      "body": "dcfd7e055a6a3043ea3541a571a57a63e25dcc64e4a270f14fa9a58ac5dbec85dcfd7e055a6a3043ea3541a571a57a63e25dcc64e4a270f14fa9a58ac5dbec85",
      "flags": 0,
      "instruction": "",
      "security": "d8f6e37f28a632c06b0b3466db1b9d2d1b36a580ee35edfd971dc1423bc412a5",
      "service_id": ""
}],
    "service_entries_permanent": true
}
}

Request parameters​

"comment": Text comment that is displayed in UI
"destinations": List of destinations
  "address": Destination address
  "amount": Amount to transfer to destination
  "asset_id": Asset id to transfer
"fee": Fee to be paid on behalf of sender's wallet(paid in native coins)
"hide_receiver": This add to transaction information about remote address(destination), might be needed when the wallet restored from seed phrase and fully resynched, if this option were true, then sender won't be able to see remote address for sent transactions anymore.
"mixin": Specifies number of mixins(decoys) that would be used to create input, actual for pre-zarcanum outputs, for post-zarcanum outputs instead of this option, number that is defined by network hard rules(15+)
"payment_id": Hex-encoded payment_id, that normally used for user database by exchanges
"push_payer": Reveal information about sender of this transaction, basically add sender address to transaction in encrypted way, so only receiver can see who sent transaction
"service_entries": Service entries that might be used by different apps that works on top of Nirmata Network, not part of consensus
  "body": Hex-encoded body of the attachment
  "flags": Flags that help wallet to automatically process some properties of the attachment(combination of TX_SERVICE_ATTACHMENT_ENCRYPT_BODY=1, TX_SERVICE_ATTACHMENT_DEFLATE_BODY=2, TX_SERVICE_ATTACHMENT_ENCRYPT_BODY_ISOLATE_AUDITABLE=4,TX_SERVICE_ATTACHMENT_ENCRYPT_ADD_PROOF=8 )
  "instruction": Instruction that make sence for this particular service
  "security": Hex-encoded public key of the owner, optional
  "service_id": Service ID, identificator that diferent one service from another
"service_entries_permanent": Point to wallet that service_entries should be placed to 'extra' section of transaction(which won't be pruned after checkpoints)

Response​

{
  "id": 0,
  "jsonrpc": "2.0",
  "result": {
    "tx_hash": "b329cce92a23fdaf89a5ad907ca9c4c1fbd052b79ec8414438533c83b39afc2b",
    "tx_size": 0,
    "tx_unsigned_hex": ""
}
}

Response information​

  • tx_hash - string; hash identifier of the transaction that was successfully sent.
  • tx_unsigned_hex - string; hex-encoded unsigned transaction (for watch-only wallets; to be used in cold-signing process).