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. 🟨MEV

β—½Introduction

MEV, short for Maximal Extractable Value, refers to the additional value that miners or validators can extract from a block beyond the standard transaction fees. By having the power to choose which transactions go into a block and their order, validators/miners can potentially take advantage by including their own transactions and prioritizing them over others in the mempool.

PreviousMEVNextMEV process

Last updated 2 years ago