feat: use real entrypoint bytecode in tests #174
Merged
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.
Motivation
For accurate gas benchmarking, we shouldn't be deploying re-compiled EntryPoint code (via
new EntryPoint()
), we should use the actual EntryPoint 0.7.0 code.Solution
Commit the binary + hex representations of EntryPoint 0.7.0 and its associated contract SenderCreator.
Add these to the setup step of OptimizedTest, and use this function in AccountTestBase.
Add a small verification test to ensure the codehash of these contracts is what we expect.
For future reference, the command used to generate the
.bytecode
files isxxd -r -p name.hex > name.bytecode
.Also renames the test file
ReferenceModularAccount.t.sol
->ModularAccount.t.sol
.