Files
proxmox/docs/04-configuration/MEV_CHAIN138_ALL_MAINNET_ROLLOUT_TRACKER.md
defiQUG 7d60a60af7
All checks were successful
Deploy to Phoenix / deploy (push) Successful in 10s
Update MEV rollout tracker with live verification
2026-04-14 17:06:51 -07:00

6.5 KiB

MEV Chain 138 And ALL Mainnet Rollout Tracker

This tracker is the current authoritative checklist for finishing the automatable deployment and MEV-integration work for:

  • Chain 138
  • ALL Mainnet 651940

It is intentionally split into:

  • repo-side work that can be completed here
  • external rollout work that requires live deployments, funding, or chain-side acceptance

Status Legend

  • done — completed and verified
  • in_progress — partially advanced and should continue
  • blocked_external — requires live contracts, liquidity, or rollout decisions
  • not_started — no reliable completion evidence yet

Shared Platform

Area Status Notes
Admin control plane (/api/health, /api/infra, /api/stats/freshness) done Recovered and validated in earlier MEV slices.
Native DODO Chain 138 ingestion done Recovery and parity work landed.
Operator metrics, ops summary, worker metrics, metrics-surfaces done Repo-side and pushed.
Mixed native route validation done Candidate-route validation and mixed-venue smoke landed.
DODO directional fallback quoting done Shared math and simulation callers updated.
Exact protocol-grade math for every required-now protocol in_progress Improved, but not complete across V3, Curve variants, GMX, dYdX, and full DODO exactness.
Full execution adapter parity across all required-now protocols in_progress Stronger for DODO/native spot flows; broader protocol set still needs completion.

Chain 138

Verified current state

  • 2026-04-14 preflight passed:
    • canonical dotenv present
    • Core RPC http://192.168.11.211:8545
    • deployer nonce clean (pending == latest)
  • 2026-04-14 canonical bytecode sweep passed:
    • 110/110 present
    • command: bash scripts/verify/check-contracts-on-chain-138.sh
  • 2026-04-14 public protocol rollout summary captured:
    • public EVM cW token mesh loaded on all 11 desired public EVM targets
    • DODO PMM has 17 recorded public cW pools across 4 destination chains
    • Uniswap v3, Balancer, Curve 3, and 1inch are still not live on the public cW mesh
    • Wave 1 non-USD GRU assets remain canonical-only on Chain 138

Canonical GRU V2 rollout

Task Status Notes
cUSDT V2 live primary venue deployment blocked_external Needs final live venue confirmation and seeded liquidity.
cUSDC V2 live primary venue deployment blocked_external Same as above.
Remaining GRU V2 promoted families activated blocked_external Needs chain-side live venue creation, funding, and acceptance.
V1 to V2 route preference cutover blocked_external Requires seeded V2 depth and rollback window.

Required-now protocol integration on 138

Protocol Discovery / Inventory Ingestion / Math Execution / Settlement Live Rollout
Uniswap v2 not_started in_progress not_started blocked_external
Uniswap v3 done in_progress not_started done_on_chain138_canonical_surface
Curve done in_progress not_started done_on_chain138_canonical_surface
DODO PMM done done in_progress done_on_chain138_canonical_surface
DODO D3MM done in_progress in_progress in_progress
Balancer done not_started not_started done_on_chain138_canonical_surface
SushiSwap not_started not_started not_started blocked_external
1Inch done not_started not_started done_on_chain138_canonical_surface
Aave not_started not_started not_started blocked_external
GMX not_started not_started not_started blocked_external
dYdX not_started not_started not_started blocked_external

Chain 138 external completion checklist

  • register or deploy final live venue addresses
  • seed funded liquidity with execution-grade depth
  • publish final addresses into canonical deployment inventory
  • surface promoted venues in MEV config and admin coverage endpoints
  • validate at least one live execution path per promoted protocol family

ALL Mainnet 651940

Task Status Notes
Canonical protocol scope confirmed chain-by-chain in_progress Scope is documented, but chain-side live venue matrix still needs final publication.
Live native venue addresses published blocked_external No complete acceptance proof in current repo state.
Liquidity seeded for promoted families blocked_external Requires funded live venues and route acceptance.
MEV discovery wired for final live venues not_started Can proceed once final live addresses are available.
MEV ingestion validated on live state not_started Depends on real live venues.
Route generation / simulation / execution validated not_started Depends on above.
Settlement and operator acceptance complete not_started Depends on above.

Known public-rollout blockers from live summaries

  • Wave 1 GRU assets still canonical-only on Chain 138:
    • EUR
    • JPY
    • GBP
    • AUD
    • CAD
    • CHF
    • XAU
  • Public cW protocol rollout is partial:
    • DODO PMM live on public cW mesh
    • Uniswap v3 not yet live on public cW mesh
    • Balancer not yet live on public cW mesh
    • Curve 3 not yet live on public cW mesh
    • 1inch not yet live on public cW mesh
  • Ranked GRU global rollout still has 29 backlog assets outside the live manifest.
  • Non-EVM GRU target Solana remains planned / relay-dependent.
  • Arbitrum public-network bootstrap remains blocked on the current Mainnet hub leg:
    • source bridge 0xc9901ce2Ddb6490FAA183645147a87496d8b20B6
    • failed tx 0x97df657f0e31341ca852666766e553650531bbcc86621246d041985d7261bb07

Fastest Next External Actions

  1. Run the CT deploy helper once SSH to the backend path is responsive: bash scripts/deployment/deploy-mev-backend-ct2421-latest.sh --dry-run
  2. Confirm final Chain 138 GRU V2 live venue addresses for:
    • cUSDT V2
    • cUSDC V2
  3. Seed those venues and verify they appear in inventory and MEV coverage.
  4. Promote Wave 1 non-USD assets from canonical_only to active transport plus public liquidity.
  5. Publish the final ALL Mainnet native venue matrix before trying to wire full MEV discovery there.

Truthful Completion Condition

This rollout is complete only when:

  1. the repo-side protocol and control-plane work is landed and deployed, and
  2. the external venue deployment, seeding, and acceptance work is finished for both Chain 138 and ALL Mainnet.