-
Notifications
You must be signed in to change notification settings - Fork 231
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
chore: flatten eip-7685 requests into a single opaque list #1383
Conversation
882bb2f
to
60acd18
Compare
After some thinking we likely do not gain much by retaining the type here instead of using blobs, since validation is mostly a CL responsibility now, and system contracts adhering to EIP-7685 return the requests pre-serialized. For user-facing RPC it will matter more, but at that point in time it's ok to pay for the ser/de cost, while we'd likely want to avoid it during execution. Restructuring the PR. |
e877abf
to
c9fcae4
Compare
c5911ff
to
fd12107
Compare
c093f3a
to
e2e6581
Compare
Looks like I need to update |
e2e6581
to
9e2510f
Compare
9e2510f
to
16a7f33
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
why? |
## Motivation There is no longer a V4 execution payload in Pectra, so it does not make sense that there would be one for Optimism. The v4 payload envelope still exists, but it now wraps a v3 payload. See also alloy-rs/alloy#1383 Based on #175 ## Solution Remove the V4 payload. ## PR Checklist - [ ] Added Tests - [ ] Added Documentation - [ ] Breaking changes --------- Co-authored-by: Yash Atreya <[email protected]>
## Motivation There is no longer a V4 execution payload in Pectra, so it does not make sense that there would be one for Optimism. The v4 payload envelope still exists, but it now wraps a v3 payload. See also alloy-rs/alloy#1383 Based on #175 ## Solution Remove the V4 payload. ## PR Checklist - [ ] Added Tests - [ ] Added Documentation - [ ] Breaking changes --------- Co-authored-by: Yash Atreya <[email protected]>
Motivation
The three different request fields have been replaced by a single field.
Requests over engine API will now be in an opaquely encoded format as defined by EIP-7685, and they will be in a single list.
See ethereum/execution-apis#591
Solution
Requests are now a list of opaque
Bytes
. Additionally, the changes to the engine API also removes the need forExecutionPayloadV4
, so I've removed that (and all variants of it).PR Checklist