Transaction Pusher

Instructions

Obtaining hex string of raw transaction from CLI wallet

  • From arq-wallet-cli --do-not-relay create a transaction which will be written to a file
  • On Linux terminal, type cat raw_arq_tx | xclip -selection clipboard
  • On Windows command line, type certutil.exe -encode -f raw_arq_tx encoded.txt & type "encoded.txt" | clip

Obtaining hex string of raw transaction from RPC wallet

  • Run arq-wallet-rpc and create a transaction with the do_not_relay and get_tx_hex parameters set to true
  • Paste the output of tx_blob into the form above

Obtaining unsigned tx set

  • Run arq-wallet-cli with a view-only wallet opened and create a transaction
  • On Linux terminal, type base64 unsigned_arq_tx | xclip -selection clipboard
  • On Windows command line, type certutil.exe -encode -f unsigned_arq_tx encoded.txt & type "encoded.txt" | clip

Obtaining signed tx set

  • Run arq-wallet-cli with the corresponding hot wallet and run sign_transfer
  • On Linux terminal, type base64 signed_arq_tx | xclip -selection clipboard
  • On Windows command line, type certutil.exe -encode -f signed_arq_tx encoded.txt & type "encoded.txt" | clip

Notes

  • Viewkey is only needed for checking a signed / unsigned tx set or pushing a signed tx set made from a view-only wallet or corresponding hot wallet
  • Data is sent to the server, as the calculations are done on the server side
  • If submitting a signed / unsigned tx set, then the private tx key, recipients, and payment id will also be sent to the server