Hackless Docs
WebsiteTelegramTwitterDiscord
  • 📁General
    • 🟨Intro
    • 🟨Mempool
      • ◽Introduction
      • ◽Transaction flow
      • ◽Transaction time
      • ◽Role of Hackless
    • 🟨Types of Transactions
    • 🟨MEV
      • ◽Introduction
      • ◽MEV process
      • ◽Downsides MEV
      • ◽Role of Hackless
  • 📂Products
    • ✳️Wallet Rescue
      • 🟨Intro
      • 🟨Types of transactions
        • ◽Native Token Transfer
        • ◽Token Transfer
        • ◽NFT: ERC-721/ERC-1155
        • ◽HEX Data Tx
        • ◽Signed Raw Tx
      • 🟨Basic flow
      • 🟨Payments
    • ✳️RPG Bot
      • 🟨Intro
      • 🟨Setting up the bot
      • 🟨Monitoring and detection
      • 🟨RPG response example
    • ✳️Anti-Sandwich
      • 🟨Intro
      • 🟨Basic flow
      • 🟨Payment transaction
      • 🟨Swap settings
      • 🟨Custom tokens
      • ❗Troubleshooting
        • ▫️Token not found
        • ▫️Insufficient liquidity
        • ▫️Insufficient asset balance
        • ▫️The price is unknown
        • ▫️Processing transaction error
Powered by GitBook
On this page
  1. Products
  2. Wallet Rescue
  3. Types of transactions

HEX Data Tx

PreviousNFT: ERC-721/ERC-1155NextSigned Raw Tx

Last updated 1 year ago

Use this type of transaction if you need to interact with a smart contract, such as claiming tokens from a staking smart contract.

Sender Address: the address from which you want to interact with the smart contract.

Smart Contract Address: the address of the smart contract you want to interact with.

HEX Data: the encoded data of the transaction that contains information needed for interaction with the smart contract.

Value: the amount of native network tokens you may need to send together with the HEX data to the smart contract. By default, this parameter is '0', and in most cases, it should remain '0'.

⚠️ Please note that when claiming tokens from a staking smart contract, the 'Value' parameter IS NOT THE AMOUNT OF TOKENS THAT YOU CLAIM ⚠️

When all the fields are filled, you may sign the transaction.

📂
✳️
🟨
◽