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. General
  2. Mempool

Role of Hackless

PreviousTransaction timeNextTypes of Transactions

Last updated 1 year ago

Hackless tools monitor transactions for issues such as front-running; and detect manipulation early allowing users to cancel transactions. But more importantly, offers private transactions that remain undetected and bypass the mempool. This is a sure way to avoid getting frontrun and lose value on your trades.

The mempool represents a loose collection of independent and inconsistent mempools maintained by thousands of nodes and acts as a temporary holding place for transactions until they are included in a block. Insights in the mempool can help you be aware of possible dangers that are lurking and waiting to strike when the time is right. With countermeasures by Hackless in combating bots that try to extract value of normal blockchain transactions you can rest assured, your transactions are safe and sound.

📁
🟨
◽
AntiSandwich