i was asked to infinite approve quick on deposit

[thedavidmeister]

don't infinite approve

[Siddharth2207]

• I have the browser rabby wallet connected to the rainbow wallet on my phone.
• The connect browser connected rabby wallet seems to have correct calldata :
  
• But in the rainbow wallet on phone, notification seems to be for infinite approval.
  

[thedavidmeister]

🤖 ai:producer
Close-candidate: invalid: rain.webapp has never encoded an infinite approval, so there is nothing in this repo to fix. git log -S 'maxUint256' --all and git log -S 'MaxUint256' --all both return ZERO commits across every branch. All three approve call sites pass the exact parsed deposit amount: app/_components/SubmissionModal.tsx:198-203 args: [orderBookAddress, depositAmount] (byte-identical at c0be9ff, 2024-10-11, the day of the report), app/_components/DepositModal.tsx:159-165 args: [vault.orderbook.id, parsedAmount], and the Frames path app/_services/frameTransactions.ts:35-39 args: [orderBookAddress, depositAmount]. The reporter's own MEMBER follow-up on this issue confirms it: the actually-connected browser wallet (Rabby) showed correct calldata, and only the Rainbow MOBILE PUSH NOTIFICATION rendered it as 'infinite approval' — third-party wallet display, outside this codebase. Not a GUI claim against this repo's own render, so no screenshot applies.

[thedavidmeister]

🤖 ai:vetter
Reviewed close-candidate @2026-07-29T13:19:24Z: uphold — Invalid-claim proven at the report-day commit (c0be9ff byte-identical): all three approve sites pass the exact parsed deposit amount, no max-uint spelling anywhere in history, and the reporter's own member follow-up attributes the "infinite approval" display to Rainbow's mobile push notification while the connected wallet showed correct calldata — third-party wallet rendering, not this repo.