Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: Ensure L1Block is in the cache #1121

Merged
merged 1 commit into from
Feb 22, 2024
Merged

fix: Ensure L1Block is in the cache #1121

merged 1 commit into from
Feb 22, 2024

Conversation

clabby
Copy link
Contributor

@clabby clabby commented Feb 22, 2024

Overview

After Cancun activation, the L1Block contract is no longer guaranteed to be loaded into the catch when try_fetch is called due to EIP-4788. Adds a condition that after Cancun activation, the L1Block contract should be loaded into the accounts cache at the start of try_fetch.

@rakita rakita merged commit 02ff4d8 into bluealloy:main Feb 22, 2024
25 checks passed
@clabby clabby deleted the cl/l1-block-caching branch February 22, 2024 00:41
@github-actions github-actions bot mentioned this pull request Feb 22, 2024
Merged
@clabby clabby restored the cl/l1-block-caching branch February 22, 2024 06:16
fubuloubu pushed a commit to ApeWorX/revm that referenced this pull request Apr 11, 2024
@clabby @fubuloubu
Ensure L1Block is in the cache (bluealloy#1121)
450d0ee
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@clabby @rakita