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

fix: re-encode calldata in mutator and refactor #380

Merged
merged 4 commits into from
Jul 2, 2024

Conversation

0xalpharush
Copy link
Contributor

@0xalpharush 0xalpharush commented Jun 25, 2024

There was another occurrence of the same issue as #374. I've fixed it and refactored it to a common API that hopefully makes it less likely to encounter this again

@0xalpharush 0xalpharush force-pushed the fix/call-seq-mutator-encoding branch from afbd319 to e6041ff Compare July 2, 2024 17:28
@0xalpharush 0xalpharush force-pushed the fix/call-seq-mutator-encoding branch from 29ca96b to f361223 Compare July 2, 2024 18:00
@0xalpharush 0xalpharush merged commit 563b371 into master Jul 2, 2024
12 checks passed
@0xalpharush 0xalpharush deleted the fix/call-seq-mutator-encoding branch July 2, 2024 19:24
s4nsec pushed a commit that referenced this pull request Jul 9, 2024
* fix: re-encode calldata in mutator and refactor

* panic on misuse
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.

2 participants