-
Notifications
You must be signed in to change notification settings - Fork 55
Execute with permit entrypoint #477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
🛡️ Immunefi PR ReviewsWe noticed that your project isn't set up for automatic code reviews. If you'd like this PR reviewed by the Immunefi team, you can request it manually using the link below: Once submitted, we'll take care of assigning a reviewer and follow up here. |
| function RFQ_VIP( | ||
| address recipient, | ||
| ISignatureTransfer.PermitTransferFrom memory takerPermit, | ||
| ISignatureTransfer.PermitTransferFrom memory makerPermit, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you document the constraint that the permit must be the 2nd argument for all VIP actions somewhere in this file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
upon further reflection, I wonder if it's possible to enforce this in CI by reviewing the artifact produced by compiling the interface
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in a separate PR (#486) so this one can be merged independently of that script
Co-authored-by: duncancmt <1207590+duncancmt@users.noreply.github.com>
…the zid offset consistent with execute entrypoint
No description provided.