Add Exact Calldata Batch Enforcer #55
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
This creates the batch counterpart of the ExactCalldataEnforcer created in #51 |
hanzel98
previously approved these changes
Mar 6, 2025
hanzel98
force-pushed
the
feat/batch-exact-calldata-enforcer
branch
from
03901d1 to
8a8a88e
Compare
hanzel98
approved these changes
Mar 7, 2025
hanzel98
force-pushed
the
feat/batch-exact-calldata-enforcer
branch
from
8a8a88e to
bba1423
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Why?
How?
Executiontypes and theExactCalldataEnforcerenforces the calldata of each execution must match.