proxmox/docs/04-configuration/MEV_CHAIN138_ALL_MAINNET_ROLLOUT_TRACKER.md

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

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	in_progress	in_progress	not_started	blocked_external
Curve	in_progress	in_progress	not_started	blocked_external
DODO PMM	done	done	in_progress	in_progress
DODO D3MM	done	in_progress	in_progress	in_progress
Balancer	not_started	not_started	not_started	blocked_external
SushiSwap	not_started	not_started	not_started	blocked_external
1Inch	not_started	not_started	not_started	blocked_external
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	blocked_external	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.
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.

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. 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.