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.

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

feat: ensure no requests are included in isthmus blocks #498

Conversation

meyer9
Copy link
Contributor

@meyer9 meyer9 commented Feb 7, 2025

Ensures requests array is empty post-Isthmus, but still runs normal processing events for these contracts (just ignores the requests).

Copy link
Contributor

@refcell refcell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM but defer to maintainers

@meyer9
Copy link
Contributor Author

meyer9 commented Feb 12, 2025

Fixed a test which was broken if Isthmus was enabled but Cancun isn't.

@meyer9
Copy link
Contributor Author

meyer9 commented Feb 12, 2025

Yeah because after Isthmus requests is always an empty array, whereas prior to this change, requests was nil for the test that was modified (broke because the previous RLP item was nil).

@refcell
Copy link
Contributor

refcell commented Feb 12, 2025

Awesome stuff 🚀

@sebastianst sebastianst merged commit acea125 into ethereum-optimism:optimism Feb 13, 2025
5 of 6 checks passed
sebastianst pushed a commit that referenced this pull request Feb 26, 2025
* feat: ensure no requests are included in isthmus blocks

* Ensure cancun enabled in block encode decode test

---------

Co-authored-by: refcell <[email protected]>
sebastianst pushed a commit that referenced this pull request Feb 26, 2025
* feat: ensure no requests are included in isthmus blocks

* Ensure cancun enabled in block encode decode test

---------

Co-authored-by: refcell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants