core/vm: evm options to ignore max-bytecode-size and support caller overriding #366
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
Signed-off-by: protolambda <proto@protolambda.com>
protolambda
force-pushed
the
evm-options
branch
from
103f03f to
7a8962c
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.
Description
NoMaxCodeSizeEVM config option, to run larger contracts (forge scripts specifically) in the Go EVMCallerOverrideEVM config option, to implement EVM-caller pranks, to support forge scripts.Tests
Existing tests cover precompiles, max-code-size and caller usage. The config option code-paths are used and tested in the monorepo.
Metadata
Part of unblocking ethereum-optimism/optimism#11490