fix(anvil): correctly set hardfork-specific block fields #9202
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
klkvr
requested review from
DaniPopes,
mattsse,
grandizzy,
yash-atreya and
zerosnacks
as code owners
2 tasks
DaniPopes
approved these changes
Oct 26, 2024
flaub
pushed a commit
to risc0/risc0
that referenced
this pull request
Oct 28, 2024
This PR updates the pinned foundry version for the `risc0-ethereum` CI checks to the latest nightly version. This nightly includes a fix for foundry-rs/foundry#9202 which was causing problems with the latest `alloy` release.
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
ref #9198 (comment)
Right now
parent_beacon_block_root,withdrawals_rootandrequests_hashare always being set toNone. They are indeed always empty but we should set empty values if corresponding hardfork is enabled.