pod network integration (Shadow mode)

[AryanGodara]

Changes

• winner-selection crate: New crate implementing deterministic solution hashing and combinatorial auction arbitration logic
• Driver pod flow: After computing a solution, drivers submit bids to pod network, wait for auction end, fetch all bids, and run local winner selection
• Configuration: New [pod] TOML config section for endpoint, auction contract, and wallet
• Playground: Added driver2/baseline2 services to test multi-driver pod scenarios
• Bug fixes: Dynamic WETH address lookup, graceful handling of None scores

How to Test

1. Start playground: cd playground && docker compose up
2. All pod-related logs are prefixed with [pod]
3. Check driver logs: docker compose logs -f driver driver2 | grep "\[pod\]"
4. Look for:
   • pod provider built with wallet
   • preparing bid submission payload
   • bid submission succeeded
   • local arbitration completed
   • local winner selected

Playground Testing Status (updating as I go)

What's Working

1. All services start successfully — autopilot, orderbook, driver, driver2, baseline, baseline2
2. Pod provider initialization — Both drivers log [pod] pod provider built with wallet
3. Bid payload preparation — Drivers prepare pod bid submission payloads with solution data
4. Local arbitration fallback — When pod network is unreachable, autopilot performs local winner selection
5. Winner selection via pod logic — Autopilot logs [pod] CoW winner selected with computed scores
6. Order settlement — Orders are settled on-chain via the winning driver

What didn't work in the local playground

• Pod bid TX submission fails — cow.pod.network:8545 is unreachable from Docker containers (DNS)
• This is expected; the local arbitration fallback works correctly

Test I ran

• Swapped 4 ETH → ~7.4K USDC
• Both solvers (baseline, baseline2) competed and submitted solutions
• Winner selected via pod arbitration logic (baseline won auction 170)

Related

• Closes Pod Integration (Shadow Mode) #4126
• Supersedes feat: pod integration #4052 (rebased onto main, cleaned up, and polished)

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

1 out of 2 committers have signed the CLA.
✅ (AryanGodara)[https://github.com/AryanGodara]
❌ @ogabrielides
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	tokio@​1.49.0 ⏵ 1.47.1	+3
	vergen@​8.3.2 ⏵ 8.3.1
	toml@​0.8.23 ⏵ 0.8.14
	tokio-stream@​0.1.18 ⏵ 0.1.17
	tower@​0.5.3 ⏵ 0.5.2
	url@​2.5.8 ⏵ 2.5.0	+1

View full report