-
Notifications
You must be signed in to change notification settings - Fork 0
feat: use new wrapper from upstream #3
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
Conversation
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.
What's this binary blob about?
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.
I think it comes from my editor :/ it gets automatically added to all my projects. but yes it shouldnt be here
This reverts commit e56eac3.
| GPv2Interaction.Data[][3] calldata interactions | ||
| ) external payable { | ||
| if (msg.sender != address(EVC)) { | ||
| revert Unauthorized(msg.sender); |
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.
The assumption here is that the EVC is fully trusted to forward this call without changing the parameters. Is this true?
In general I'd expect that the code checks that the settlement data used in evcInternalSettle matches the one that _wrap wants to forward to it (and also that it's called exactly once).
With the current code, the EVC contract can execute any settlement it wants once wrappedSettle is called.
best way to ensure the expected flow is followed exactly
the generic wrappers implementation has changed upstream. Modifications to use this new pattern.