fix engine_getPayloadV4 compliance error #33144
Closed
+10
−0
Conversation
This file contains hidden or 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
Fix the issue on engine API: engine_getPayloadV4, to make it compliant with osaka engine API spec. According to issue listed in Fusaka contest: https://audits.sherlock.xyz/contests/1140/voting/157, the issue of API: engine_getPayloadV4 should also follow the spec restriction as the previous PR on getBlobsV1: ethereum#32731
CertiK-Geth
requested review from
MariusVanDerWijden,
fjl,
jwasinger and
lightclient
as code owners
Contributor
|
I think it is also fixed by this PR, which tries to be more comprehensive: #32754 |
Contributor
|
Should be fixed by #32754 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix the issue on engine API: engine_getPayloadV4, to make it compliant with osaka engine API spec.
According to issue listed in Fusaka contest: https://audits.sherlock.xyz/contests/1140/voting/157, the issue of API: engine_getPayloadV4 should also follow the spec restriction as the previous PR on getBlobsV1: #32731