Skip to content

Commit a4f5e3e

Browse files
authored
Update eip7928.md
I have added one specification for the `engine_newPayloadV5` method. According to the Amsterdam upgrade, when the `blockAccessList` field is missing in `engine_newPayloadV5`, the error message: `-32602: Invalid params` should be returned. However, without specifying which error code should be returned, the `{status: INVALID, latestValidHash: null, validationError: errorMessage | null}` may be wrongly returned according to the previous description, which may lead to inconsistencies among clients. Therefore, I think it is necessary to clearly specify the should-be-returned error code.
1 parent f910189 commit a4f5e3e

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

src/engine/eip7928.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -75,9 +75,11 @@ This method follows the same specification as [`engine_newPayloadV4`](./prague.m
7575

7676
1. Client software **MUST** return `-38005: Unsupported fork` error if the `timestamp` of the payload does not fall within the time frame of the EIP-7928 activation.
7777

78-
2. Client software **MUST** validate the `blockAccessList` field by executing the payload's transactions and verifying that the computed access list matches the provided one.
78+
2. Client software **MUST** return `-32602: Invalid params` error if the `blockAccessList` field is missing.
7979

80-
3. If the `blockAccessList` field is missing, malformed, or doesn't match the computed access list, the call **MUST** return `{status: INVALID, latestValidHash: null, validationError: errorMessage | null}`.
80+
3. Client software **MUST** validate the `blockAccessList` field by executing the payload's transactions and verifying that the computed access list matches the provided one.
81+
82+
4. If the `blockAccessList` field is malformed or doesn't match the computed access list, the call **MUST** return `{status: INVALID, latestValidHash: null, validationError: errorMessage | null}`.
8183

8284
### engine_getPayloadV6
8385

@@ -122,4 +124,4 @@ a validation **MUST** be added:
122124
1. Client software **MUST** return `-38005: Unsupported fork` error if the `timestamp` of payload greater or equal to the EIP-7928 activation timestamp.
123125

124126
For the [`engine_forkchoiceUpdatedV3`](./cancun.md#engine_forkchoiceupdatedv3) the following modification **MUST** be made:
125-
1. Return `-38005: Unsupported fork` if `payloadAttributes.timestamp` doesn't fall within the time frame of the Cancun, Prague, Osaka *or EIP-7928* forks.
127+
1. Return `-38005: Unsupported fork` if `payloadAttributes.timestamp` doesn't fall within the time frame of the Cancun, Prague, Osaka *or EIP-7928* forks.

0 commit comments

Comments
 (0)