MEV Wiki
  • Introduction
  • Resource List
  • Terms and Concepts
    • DeFi
    • Automated Market Maker
    • Arbitrage
    • Lending Platforms
    • Slippage
    • Liquidations
    • Priority Gas Auctions
    • Transaction Ordering
  • Attack Examples
    • Front-running
    • Sandwich attack
    • Back-running
    • Liquidations
    • Time bandit attack
    • Uncle bandit attack
  • Attempts to trick the bots
    • Salmonella
    • Kattana
    • Other attempts
  • Solutions
    • Front-running as a Service (FaaS) or MEV Auctions (MEVA)
      • Private Transactions
      • BackRunMe by bloXroute
      • Flashbots
      • mistX by alchemist
      • KeeperDAO
      • EDEN Network (ArcherSwap)
      • Optimism
      • MiningDAO
      • BackBone Cabal
    • MEV Minimization
      • Conveyor (Automata Network)
      • SecretSwap (Secret Network)
      • Fair sequencing service (Chainlink)
      • Arbitrum (Offchain Labs)
      • Vega protocol
      • CowSwap
      • Veedo (StarkWare)
      • LibSubmarine
      • Sikka
      • Shutter Network
    • Other solutions
      • B.Protocol
  • Miscellaneous
  • Contributions
Powered by GitBook
On this page

Was this helpful?

Solutions

PreviousOther attemptsNextFront-running as a Service (FaaS) or MEV Auctions (MEVA)

Last updated 3 years ago

Was this helpful?

Different approaches to tackling the MEV problem

There are largely 2 schools of thought when it comes to approaching the MEV problem

  1. Offense - MEV is here to stay so let's find a way to extract and democratize it.

  2. Defense - MEV is bad so let's try to prevent it.

Projects like Automata Network are in the Defense camp where the solution ingests transactions and outputs transactions in a determined order. This creates a front-running-free zone that removes the chaos of transaction reordering.

To further explain, we have put different approaches into 3 categories:

Conveyor
Front-running as a Service (FaaS) or MEV Auctions (MEVA)
MEV Minimization
Other solutions