-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix: use proper type for engine_newPayloadV2 #4630
Conversation
Codecov Report
... and 26 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This appears to fix pre-shanghai but now we have an issue with all CL clients making it across to capella. Looking into this now. |
Now we get a rejection on an request with an empty withdrawals entry. Request
Response
I second the regression testing. I've added reth instances into my testing workflow at least. |
nice catch, this change did not fix it entirely, due to how deserialization now works. fixing asap |
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, missing withdrawals post shanghai are caught during validation against timestmap
LGTM |
Should fix #4628
The spec we linked in docs says to use
ExecutionPayloadV2
:This is incorrect as noted in the issue. We already had a type for the correct version, which was used as the return value for
engine_getPayloadV2
, but it was not used as the input forengine_newPayloadV2
.Will look into developing some testing for this, since we've had similar bugs that were not regression tested.