📚
EigenPhi Classroom
EigenPhiTwitterAlertSubstack
  • A Brief Introduction about EigenPhi Classroom
  • Glossary
    • MEV
    • MEV Contract
    • Malicious Token
    • Trading Volume
    • Trading Volume Change%
    • Transaction Profit Distribution (percentile)
    • Arbitrage ID
    • 1D/7D/30D
    • Liquidity Pool
    • Smart Contract
    • Protocol
    • Profit%
    • TFIDF
    • Asset, Liquidation
    • Borrower, Liquidation
    • Liquidator, Liquidation
    • Collateral, Liquidation
    • LTV, Liquidation
    • Liquidation Threshold, Liquidation
  • MEV Types
    • Arbitrage
      • Arbitrage Using 2 Tokens Between 2 Trading Venues
      • Arbitrage Involving 3 Tokens Among 3 Trading Venues
      • Arbitrage Requiring More Tokens and More Trading Venues
      • Arbitrage package
    • Sandwich MEV
    • Liquidation
      • Liquidation transaction with Aave V2 involved
  • Users of EigenPhi
    • Researcher
    • Searcher
    • Retail Investor
  • Communities & Channels
    • Our MEV Daily Report
      • Overview Section of Daily Report
      • Summary Data by MEV Types of Daily Report
      • MEV-Bot Data by MEV Types of Daily Report
      • Hot Liquidity Pools and Hot Tokens of Daily Report
      • MEV Transaction Profit Leaderboard of Daily Report
      • Download And Share Daily Report Data
    • Our Sandwich Daily Report
      • Overview Section of Sandwich Daily Report
      • Sandwich MEV Trends of Last 24 Hours and 7 Days
      • What Were the Sandwich Searchers Capable of Yesterday?
      • The 5 Most Delicious Sandwiches
      • Watch Out When Using These Protocols, Routers, and Proxies!
      • Top Attackers and Victims
      • Download And Share Sandwich Daily Report Data
    • Our Data Sources
    • Our Content and Social Channels
  • EigenPhi's Methodologies
    • Do You Have These Questions When Doing DeFi Trading?
    • 2 Biggest Concerns That Haven't Been Properly Addressed
    • 3 Pillars of DeFi: Structure, Behavior, and Network
    • The EigenPhi Way
    • Why MEV?
    • How EigenPhi Identifies MEV
      • Recognizing Atomic Arbitrage MEV Transactions
        • Implementation
        • A Typical Arbitrage Example
      • Recognizing Cross-Transaction Sandwich MEV
        • Example
Powered by GitBook
On this page
  1. EigenPhi's Methodologies
  2. How EigenPhi Identifies MEV

Recognizing Atomic Arbitrage MEV Transactions

PreviousHow EigenPhi Identifies MEVNextImplementation

Last updated 2 years ago

Since transactions can be highly complex and involve infinite unknown patterns, relying solely on specific transaction pattern matching is inadequate to identify new MEV patterns. To detect Arbitrage in transactions, we need a universal abstraction for transactions.To achieve this, we have established the following principles for recognition.

  1. We define a transaction as a collection of asset transfers.

  2. Then, we evaluate the outcomes of these transfers using a set of rules to determine if an MEV has occurred.

  3. We break down a transaction into Transfers and Trades.

  4. Our algorithm merges Transfers to form a Transfer Table.

  5. Next, we use the Transfer Table to merge the rows with the same address and generate a Combined Transfer Table.

Our rule of thumb is: if the token balance of the nearest point to the "from" or "to" address of the transaction within a strongly connected component is positive, we regard this transaction as Arbitrage.

To help you better understand it, next, we will present a detailed process and an example to illustrate our algorithm based on the Token Flow graph generated in our EigenTx tool.

Principles for Recognition