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

Introduction

The mempool, also known as the memory pool, is a collection of all transactions that have not yet been confirmed and added to a block on the blockchain. Transactions are temporarily stored in the mempool of each node on the network, until they are verified and added to a new block. The concept of mempool is both used in Ethereum and Bitcoin blockchains. We’ll focus on the Ethereum mempool, which often holds thousands of pending transactions at any given time.

PreviousMempoolNextTransaction flow

Last updated 1 year ago

📁
🟨
◽