fix: missing execution_forks in WASM client config#770
Open
zeroprooff wants to merge 1 commit intoa16z:masterfrom
Open
fix: missing execution_forks in WASM client config#770zeroprooff wants to merge 1 commit intoa16z:masterfrom
zeroprooff wants to merge 1 commit intoa16z:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 WASM client was not copying execution_forks from the base network config, falling back to ForkSchedule::default() which sets all fork timestamps to u64::MAX. This caused the EVM to run in FRONTIER mode instead of the correct fork (Cancun/Prague), breaking eth_call, eth_estimateGas and eth_createAccessList results.