Skip to content
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

✨ isValidERC6492SignatureNow #941

Merged
merged 19 commits into from
Jun 3, 2024
Merged

✨ isValidERC6492SignatureNow #941

merged 19 commits into from
Jun 3, 2024

Conversation

Vectorized
Copy link
Owner

@Vectorized Vectorized commented May 27, 2024

Description

@Agusx1211

Closes #940.

On optimization:

It's ok even if the bytes are out-of-bounds in the signature. Either subsequent mloads will go out-of-gas, or the signature verification will just fail. If there is ever a case where the byte offsets can be manipulated to make the verification pass, it means that the relevant information to make the verification pass is already publicly available on-chain -- anyone can submit a signature that will make the verification pass, even if we have all the bounds checks in place.

So what about gas-griefing? Well, the factory address is dynamic anyways...

Letting this marinate for a while.

Checklist

Ensure you completed all of the steps below before submitting your pull request:

  • Ran forge fmt?
  • Ran forge snapshot?
  • Ran forge test?

Pull requests with an incomplete checklist will be thrown out.

@Vectorized Vectorized merged commit d315b01 into main Jun 3, 2024
9 checks passed
@Vectorized Vectorized deleted the 6492 branch June 3, 2024 04:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

✨ isValidERC6492SignatureNow
1 participant