You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems important that, once used, the "one time proxy" rejects any incoming transfer
@benjlevesque I'm not so sure. I think we'd still want to support partial payments. And since the expected amount can change (via increase/decreaseExpectedAmount) I don't think we can store the expected amount on the contract.
Despite the familiarity of the name "One Time Proxy", I don't think we should call it that, because we support partial payments meaning that a given proxy contract can be paid more than once. I prefer the name "SingleRequestProxy". I think it makes it clear that the Proxy is tied to a single request.
MantisClone
changed the title
Develop a PoC "One Time Proxy" payment smart contract that emits the paymentReference event in the receive() function
Develop a PoC "SingleRequestProxy" payment smart contract that emits the paymentReference event in the receive() function
Apr 30, 2024
Proposed Solution
Reference: https://miro.com/app/board/uXjVM2Pf758=/?share_link_id=761216115297
Factory Contract can spawn new instances of SingleRequestProxy.
Definition of Done
The text was updated successfully, but these errors were encountered: