Bot Titles
POL-DEX-ARB-V1Performance So Far
POL-DEX-ARB-V1Recent Fire Attempts
POL-DEX-ARB-V1Token Reverters (24h)
POL-DEX-ARB-V1Biggest Block
POL-DEX-ARB-V1No curated obstacle text for this bot yet. Wire via L8-promote pipeline once the bot has a Tier-1 status review.
Fantasy
POL-DEX-ARB-V1If we had some way to instantly remove this bot's biggest constraint — capital, latency, signal coverage, or counterparty risk — what would the world look like? (Pending creative assessment.)
Suggestions for Improvement
POL-DEX-ARB-V1- 01PENDINGNo curated suggestions for this bot yet.
Conclusion
POL-DEX-ARB-V1Verdict: in paper mode for months, never promoted to live, and there is a structural reason for that. The bot scans Polygon V2/V3 pools cross-DEX and prints opportunities, but none have crossed the live threshold. At its last live snapshot the heartbeat showed scans flowing, opps=0, simAttempts=0. As of 2026-05-25 it is PAUSED (dex-exec tmux down) — no longer even scanning.
Failure mode #1 — two-DEX arb on a mature L2 doesn't exist at our scan latency. QuickSwap V3 + SushiSwap V3 + Uniswap V3 spreads are eaten within one or two blocks of opening by professional cross-DEX bots running on dedicated infra. By the time our scanner posts a signal, the spread is gone or inverted. The Base equivalent (BASE-V3-ARB-V1) was killed 2026-04-20 for exactly this reason.
Failure mode #2 — no contract; no flash; no leverage. This bot is parked even in paper. To convert any spread it sees into a fire, we'd need a Polygon flash-arb contract — and we already have one (POL-FLASH-ARB-V1) that is itself dormant. Doubling down on a Polygon DEX arb stack while the parent is dead is incoherent.
Failure mode #3 — stale supporting infrastructure. Polygon RPC keys are expired across the operator wallet (per POL-FLASH-ARB-V1 forensics). Even if we wanted to fire, we'd be hitting a 401 wall on the executor side.
Fixable? Same answer as POL-FLASH-ARB-V1: no, kill it. Retire the secondary alongside the flagship. If we ever revisit Polygon, it should be Aave liquidations or a Balancer-pool specialist — not two more cross-DEX arb scanners that the entire MEV ecosystem has already digested.