mev-beta/DEPLOYMENT_CHECKLIST.md

MEV Bot Critical Fixes - Deployment Checklist

Date: October 25, 2025 Commit: 14bf75c on feature/production-profit-optimization Status: ✅ READY FOR DEPLOYMENT

---

✅ Pre-Deployment Verification

• Log audit completed - Identified 3 critical issues
• Root cause analysis - All issues documented
• Fixes implemented - All 3 fixes applied
• Build validation - make build ✅ SUCCESS
• Package tests - Modified packages pass tests
• Code committed - Commit 14bf75c created
• Documentation - Complete implementation & investigation reports

---

📦 What Was Fixed

Fix #1: Zero Address Token Bug ⚠️ CRITICAL

Impact: 100% of opportunities were failing Solution: Populate token addresses from pool contract data Expected Result: Token addresses will be valid, profit calculations accurate

Fix #2: RPC Rate Limiting 🔄 HIGH

Impact: 61 rate limit errors per scan Solution: Exponential backoff + reduced rate limit (10→5 RPS) Expected Result: <5 rate limit errors per scan

Fix #3: Pool Blacklist 🚫 MEDIUM

Impact: 12+ failed RPC calls to invalid pool Solution: Automatic blacklisting system Expected Result: Zero calls to blacklisted pools

---

🚀 Deployment Steps

1. Stop Current MEV Bot

# If running in background
pkill -f mev-bot

# Or if you know the process ID
kill <PID>

2. Archive Current Logs

./scripts/log-manager.sh archive
# OR
./scripts/archive-logs.sh

3. Build New Binary

make build

4. Verify Build

./bin/mev-bot --version
# OR
./mev-bot --version

5. Deploy & Start

# Option 1: Using run script
./scripts/run.sh

# Option 2: Direct execution
PROVIDER_CONFIG_PATH=$PWD/config/providers_runtime.yaml timeout 120 ./mev-bot start

# Option 3: With logging
PROVIDER_CONFIG_PATH=$PWD/config/providers_runtime.yaml LOG_LEVEL=info ./mev-bot start 2>&1 | tee logs/deployment_$(date +%Y%m%d_%H%M%S).log

---

🔍 Post-Deployment Monitoring (First 30 Minutes)

Critical Checks

1. Token Addresses Are Valid

# Check swap events log
tail -f logs/swap_events_*.jsonl | jq '.token0Address, .token1Address'

# Should see actual addresses like:
# "0x82aF49447D8a07e3bd95BD0d56f35241523fBab1"  ← WETH
# "0xaf88d065e77c8cC2239327C5EDb3A432268e5831"  ← USDC

# NOT zero addresses like:
# "0x0000000000000000000000000000000000000000"  ← BAD

2. Rate Limit Retries Working

# Watch for rate limit handling
tail -f logs/mev_bot.log | grep -i "rate limit\|RPS limit"

# Should see messages like:
# "⚠️ RPC rate limit hit (attempt 1/3), applying exponential backoff"
# "📊 Rate limiting configured: 5.0 requests/second"

3. Blacklisted Pool Skipped

# Verify blacklist is active
tail -f logs/mev_bot.log | grep -i "blacklist"

# Should see on startup:
# "🚫 Blacklisted pool 0xB1026b8e7276e7AC75410F1fcbbe21796e8f7526: slot0() consistently reverts"

# And during operation:
# "Skipping blacklisted pool 0xB102...7526"

4. Opportunities Being Detected

# Monitor opportunity detection
tail -f logs/mev_bot_opportunities.log | jq '.token0, .token1, .estimatedProfitUSD'

# Look for non-zero profit estimates

---

📊 Success Metrics

Within 10 Minutes

• Token addresses are NOT 0x0000...0000
• Pool blacklist message appears in logs
• Rate limiting configured at 5 RPS

Within 30 Minutes

• At least 1 opportunity with valid token addresses
• Rate limit errors < 5 (down from 61)
• No RPC calls to 0xB102...7526
• Swap events have correct token symbols

Within 1 Hour

• Multiple opportunities detected
• Token addresses matching actual pools
• Price impacts are realistic (not 10^60)
• Some opportunities marked as executable

---

🚨 Rollback Procedure

If any critical issue occurs:

Quick Rollback

# Stop the bot
pkill -f mev-bot

# Revert to previous commit
git reset --hard fcf141c

# Rebuild
make build

# Restart
./scripts/run.sh

Verify Rollback

git log --oneline -1
# Should show: fcf141c fix(uniswap): correct slot0() ABI unpacking

---

🎯 Rollback Triggers

Rollback immediately if you observe:

• ❌ More errors than before deployment
• ❌ New panic/crash not present in previous version
• ❌ Zero opportunities for 30+ minutes (regression)
• ❌ Increased rate limit errors (>100 in 30 min)

---

📈 Expected Improvements

Metric	Before	After (Expected)
Valid Token Addresses	0%	100%
Executable Opportunities	0	1-3 per 1000 swaps
RPC Rate Limit Errors	61/scan	<5/scan
Invalid Pool RPC Calls	12/scan	0/scan
Arbitrage Success Rate	0%	20-40%

---

📁 Important Files

Investigation & Documentation:

• LOG_AUDIT_FINDINGS.md - Detailed problem analysis
• FIXES_IMPLEMENTED.md - Complete implementation details
• DEPLOYMENT_CHECKLIST.md - This file

Modified Code:

• pkg/scanner/swap/analyzer.go - Token address fix
• pkg/arbitrum/connection.go - Rate limiting fix
• pkg/scanner/market/scanner.go - Pool blacklist

Logs to Monitor:

• logs/mev_bot.log - Main application log
• logs/mev_bot_errors.log - Error tracking
• logs/mev_bot_opportunities.log - Opportunity detection
• logs/swap_events_*.jsonl - Swap event data

---

💡 Tips

1. Use tmux or screen for long-running sessions
2. Archive logs before deployment to compare before/after
3. Monitor for first hour to catch any issues early
4. Check opportunity logs for realistic profit estimates
5. Note token symbols - should see WETH, USDC, USDT, not TOKEN_0x000000

---

🆘 Emergency Contacts

If Critical Issues Arise:

1. Check logs/mev_bot_errors.log for error patterns
2. Review git diff: git diff fcf141c 14bf75c
3. Use log manager: ./scripts/log-manager.sh analyze
4. Archive and investigate: ./scripts/log-manager.sh health

---

✅ Final Checklist Before Deployment

• Current bot is stopped
• Logs are archived
• New binary is built
• Config files are in place
• Ready to monitor for 30+ minutes
• Have rollback plan ready
• Know how to check success metrics

---

Ready to deploy? Run:

./scripts/run.sh

Then monitor with:

tail -f logs/mev_bot.log | grep -i "token0\|token1\|blacklist\|rate limit"

---

Deployment Date: _____________ Deployed By: _____________ Status: ⬜ Success ⬜ Rollback Required Notes: ___________________________________________________