mev-beta/research_todo_checklist.md

MEV Research Missing Elements Checklist

This file tracks our investigation of missing elements in the MEV research documentation and implementation.

Completed Items

1. Investigate actual implementation details of core systems (pkg/arbitrage, pkg/transport, pkg/scanner, pkg/profitcalc)

• Status: COMPLETED
• Details: Examined key files in each package:
  • pkg/arbitrage/service.go - Comprehensive arbitrage service with detection engine and execution framework
  • pkg/transport/websocket_transport.go - WebSocket transport for real-time monitoring
  • pkg/scanner/concurrent.go - Concurrent event processing with worker pools
  • pkg/profitcalc/profit_calc.go - Sophisticated profit calculation with slippage protection
• Findings: Core systems are implemented with comprehensive functionality including MEV detection, real-time monitoring, and profit calculation

Items to Investigate

2. Locate Timeboost auction dataset (DAO auction logs from 2025-06-2025-09)

• Status: TODO
• Description: The experiment log mentions importing DAO auction logs (2025-06–2025-09) for Timeboost cost modeling
• Next Action: Search for Timeboost-related files or datasets in the repository

3. Find simulation backtest results and implementation

• Status: TODO
• Description: The experiment mentions pending simulation results comparing different strategies
• Next Action: Look for simulation tools and reports in the tools/simulation directory

4. Examine data/pools.txt and investigate fee-tier/liquidity enrichment

• Status: TODO
• Description: Documentation mentions that data/pools.txt needs fee-tier/liquidity enrichment
• Next Action: Locate and examine the pools.txt file and any enrichment scripts

5. Look for monitoring dashboards and Grafana panel implementations

• Status: TODO
• Description: Experiment mentions building Grafana panels for spread monitoring
• Next Action: Search for Grafana dashboard configurations or monitoring implementations

6. Investigate unverified router contracts (0x82df... and 0xaa78...) and security compliance

• Status: TODO
• Description: Two router contracts are mentioned as unverified and blocklisted
• Next Action: Search for security-related files and contract verification implementations

7. Find operational procedures documentation

• Status: TODO
• Description: SOP (Standard Operating Procedures) for live operations is planned but not drafted
• Next Action: Look for operational procedure documents or runbook implementations

8. Locate MEV strategies implementation code

• Status: TODO
• Description: Beyond documentation, need to find actual code implementing MEV strategies
• Next Action: Search for arbitrage execution and MEV strategy implementation files

9. Search for performance data and profitability metrics

• Status: TODO
• Description: Need to find actual profitability metrics from live or simulated operations
• Next Action: Look for reports, metrics collection, or performance tracking files

10. Investigate cross-chain arbitrage datasets and tracking

• Status: TODO
• Description: Documentation mentions cross-chain arbitrage but has limited data tracking
• Next Action: Search for cross-chain arbitrage implementation and dataset files

Investigation Methodology

For each item, we will:

1. Search for relevant files in the repository
2. Read and analyze the implementation
3. Document findings in this checklist
4. Mark as completed when thoroughly investigated

Repository Structure of Interest

• cmd/mev-bot - Main executable
• pkg/arbitrage - Arbitrage strategies
• pkg/transport - Communication protocols
• pkg/scanner - Event scanning
• pkg/profitcalc - Profit calculation
• tools/simulation - Simulation tools
• reports/ - Reports and metrics
• data/ - Data files
• docs/ - Documentation
• internal/ - Internal utilities
• scripts/ - Scripts and automation