feat(anvil): Include CREATE2 deployer by default on new instances
#5391
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
Evalir
changed the title
anvil): Include CREATE2 deployer by default on new instances
Evalir
changed the title
anvil): Include CREATE2 deployer by default on new instances
mattsse
approved these changes
Aug 18, 2023
mikelodder7
pushed a commit
to LIT-Protocol/foundry
that referenced
this pull request
Sep 12, 2023
…foundry-rs#5391) * chore: install create_2_deployer * chore: docs * chore: comment codes * fix: set proper runtime code * fmt
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.
Motivation
Closes #4807.
Solution
Include the
CREATE2factory deployer when starting up anvil by default, and add a new--disable-default-create2-deployerflag to not deploy it. It will also not be deployed if anvil is forking, to properly simulate the conditions of that chain.TODOs: