Solidity core contract differential fuzzing #4100
Open
Conversation
This file contains 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
evan-gray
reviewed
Aug 27, 2024
I was concerned about tying CI to an RPC given we're forking mainnet for this fuzz test, and from what I've seen it looks like we hit the endpoint pretty hard |
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.
The original purpose of this fuzzing suite was to give more confidence around the changes in #3366. This fuzz test suite uses both the currently deployed core contract, and deploys the current local implementation, before performing an arbitrary sequence of calls across both forks.
Given the timeline and consensus around that PR is unclear I've decided to pull these fuzz tests into this PR.
Fuzz tests can be executed with: