Skip to content

conditional-team/mev-engineering-stack

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

7 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

⚑ MEV Protocol

High-Performance Multi-Language MEV Engineering Stack
Low-latency detection, simulation, and execution research for EVM ecosystems.

Rust Go Solidity C CI


πŸš€ Executive Overview

MEV Protocol is a portfolio-grade systems project built to showcase production-oriented engineering across runtime boundaries.

It combines:

  • Solidity/Yul for on-chain execution paths
  • Rust for orchestration, detection, and simulation
  • Go for mempool networking and relay interaction
  • C for low-level hot-path components

The repository is structured for technical review, reproducible builds, and iterative extension.

🧱 Architecture

  • contracts/ β€” smart contracts and Foundry tests
  • core/ β€” Rust engine (mev-engine, scanner, benchmark)
  • network/ β€” Go node for mempool and relay components
  • fast/ β€” C static/shared libraries for performance-critical code
  • config/ β€” chain, DEX, and environment configuration
  • scripts/ β€” build and deployment scripts
  • docker/ β€” container runtime assets

πŸ“Œ Engineering Status

  • βœ… Multi-stack build and test flow available
  • βœ… CI pipeline configured for Rust, Go, and Solidity
  • βœ… Contract-layer callback spoofing hardening (Balancer + Uniswap V3)
  • βœ… Deterministic route validation with trusted factory/router controls
  • ⚠️ Some modules still contain placeholder/TODO logic (notably parts of detector/simulator)

Positioning is intentionally transparent: strong technical foundation with active feature completion.

πŸ› οΈ Quality & Process

  • CI workflow: .github/workflows/ci.yml
  • Local gates: make build, make test, make lint, make ci-local
  • Security hygiene: sanitized templates (config/.env.example) + strict ignore rules

πŸ” Contract Hardening Highlights

  • Flash loan callback is bound to active execution context (executor, token, amount, swap hash).
  • Uniswap V3 callbacks are accepted only from the active pool for the active swap.
  • Swap route decoding rejects malformed payloads and unknown swap types.
  • V2/V3 execution paths validate trusted routers/factories before swap execution.
  • ERC20 transfer/transferFrom/approve wrappers enforce strict return-data checks.

βœ… Post-Deploy Security Checklist

Before enabling execution in production:

  1. Set whitelisted executors.
  2. Set trusted V2 routers (FlashArbitrage).
  3. Set trusted V3 factory (FlashArbitrage).
  4. Set trusted V2/V3 factories (MultiDexRouter).
  5. Keep contract paused until off-chain simulation and dry-run checks are green.

⚑ Quick Start

Windows (PowerShell)

.\scripts\build.ps1

Linux/macOS

chmod +x scripts/build.sh
./scripts/build.sh

🎯 Why It Impresses Recruiters

This project demonstrates:

  • low-latency architecture and performance tradeoffs
  • polyglot systems integration (Rust/Go/C/Solidity)
  • smart-contract and off-chain coordination patterns
  • mature engineering workflow (CI, templates, quality gates)

βš–οΈ Responsible Use

This repository is for engineering research and education. Users are responsible for legal, compliance, and operational risk management in their jurisdiction.

πŸ“„ License

Proprietary (as currently configured in project metadata).

About

βš‘πŸ§ β›“οΈ Low-Latency MEV Engineering Stack β€” Detection, simulation and execution research across Rust, Go, Solidity and C with CI-driven workflow.

Topics

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors