-
Notifications
You must be signed in to change notification settings - Fork 2
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
use nested structs for hashing the relay order #95
Conversation
Forge code coverage:
|
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.
looks great! just a few nits
"FeeEscalator(", | ||
"address token,", | ||
"uint256 startAmount,", | ||
"uint256 endAmount,", |
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.
previously you were skipping endAmount since it's included in the tokenpermissions - any reason we decided to add it back in?
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.
Yeah we are changing the entire hash function of the RelayOrder because otherwise order hashes are not collision resistant. Ie a change in endAmount or even the token but everything else is kept the same would result in the same hash
TODO: Add tests to the relay order lib, needs to merge main