Skip to content

Commit

Permalink
engine: clarification on requests
Browse files Browse the repository at this point in the history
  • Loading branch information
lightclient committed Oct 8, 2024
1 parent 48de028 commit f1ce8ce
Showing 1 changed file with 2 additions and 6 deletions.
8 changes: 2 additions & 6 deletions src/engine/prague.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,9 +35,7 @@ Method parameter list is extended with `executionRequests`.
1. `executionPayload`: [`ExecutionPayloadV3`](./cancun.md#executionpayloadv3).
2. `expectedBlobVersionedHashes`: `Array of DATA`, 32 Bytes - Array of expected blob versioned hashes to validate.
3. `parentBeaconBlockRoot`: `DATA`, 32 Bytes - Root of the parent beacon block.
4. `executionRequests`: `Array of DATA` - List of execution layer triggered requests,
each element of the list represents an SSZ encoded list of requests of a certain type as it is defined by [EIP-7685](https://eips.ethereum.org/EIPS/eip-7685)
Elements of the list **MUST** be ordered by `requestType` in ascending order.
4. `executionRequests`: `Array of DATA` - List of execution layer triggered requests. Each list element is the corresponding request type's `request_data` as defined by [EIP-7685](https://eips.ethereum.org/EIPS/eip-7685). Elements of the list **MUST** be ordered by `request_type` in ascending order.

#### Response

Expand Down Expand Up @@ -81,9 +79,7 @@ This method follows the same specification as [`engine_getPayloadV3`](./cancun.m

1. Client software **MUST** return `-38005: Unsupported fork` error if the `timestamp` of the built payload does not fall within the time frame of the Prague fork.

2. The call **MUST** return `executionRequests` list representing execution layer triggered requests obtained from the `executionPayload` transaction execution.
Each element of the list represents an SSZ encoded list of requests of a certain type as it is defined by [EIP-7685](https://eips.ethereum.org/EIPS/eip-7685).
Elements of the `executionRequests` list **MUST** be ordered by the `requestType` in ascending order.
2. The call **MUST** return `executionRequests` list representing execution layer triggered requests obtained from the `executionPayload` transaction execution. Each element of the list corresponds to the request type's `request_data` as defined by [EIP-7685](https://eips.ethereum.org/EIPS/eip-7685). Elements of the list **MUST** be ordered by `request_type` in ascending order.

### Update the methods of previous forks

Expand Down

0 comments on commit f1ce8ce

Please sign in to comment.