Reflect changes in the queue

Author: jihoonsong

src/engine/common.md

@@ -99,6 +99,7 @@ The list of error codes introduced by this specification can be found below.
 | -38003 | Invalid payload attributes | Payload attributes are invalid / inconsistent. |
 | -38004 | Too large request | Number of requested entities is too large. |
 | -38005 | Unsupported fork | Payload belongs to a fork that is not supported. |
+| -38006 | Unknown parent | Parent does not exist / is not available. |
 
 Each error returns a `null` `data` value, except `-32000` which returns the `data` object with a `err` member that explains the error encountered.
 

src/engine/experimental/eip7805.md

@@ -10,6 +10,10 @@ This specification is based on and extends [Engine API - Osaka](./osaka.md) spec
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 
 - [Constants](#constants)
+- [Structures](#structures)
+  - [PayloadAttributesV4](#payloadattributesv4)
+- [Routines](#routines)
+  - [Payload building](#payload-building)
 - [Methods](#methods)
   - [engine_newPayloadV5](#engine_newpayloadv5)
     - [Request](#request)
@@ -19,11 +23,10 @@ This specification is based on and extends [Engine API - Osaka](./osaka.md) spec
     - [Request](#request-1)
     - [Response](#response-1)
     - [Specification](#specification-1)
-  - [engine_updatePayloadWithInclusionListV1](#engine_updatepayloadwithinclusionlistv1)
+  - [engine_forkchoiceUpdatedV4](#engine_forkchoiceupdatedv4)
     - [Request](#request-2)
     - [Response](#response-2)
     - [Specification](#specification-2)
-  - [Update the methods of previous forks](#update-the-methods-of-previous-forks)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
@@ -33,6 +36,27 @@ This specification is based on and extends [Engine API - Osaka](./osaka.md) spec
 | - | - |
 | `MAX_BYTES_PER_INCLUSION_LIST` |  `uint64(8192) = 2**13` |
 
+## Structures
+
+### PayloadAttributesV4
+
+This structure has the syntax of [`PayloadAttributesV3`](./cancun.md#payloadattributesv3) and appends a single field: `inclusionList`.
+
+- `timestamp`: `QUANTITY`, 64 Bits - value for the `timestamp` field of the new payload
+- `prevRandao`: `DATA`, 32 Bytes - value for the `prevRandao` field of the new payload
+- `suggestedFeeRecipient`: `DATA`, 20 Bytes - suggested value for the `feeRecipient` field of the new payload
+- `withdrawals`: `Array of WithdrawalV1` - Array of withdrawals, each object is an `OBJECT` containing the fields of a `WithdrawalV1` structure.
+- `parentBeaconBlockRoot`: `DATA`, 32 Bytes - Root of the parent beacon block.
+- `inclusionList`: `Array of DATA` - Array of transaction objects, each object is a byte list (`DATA`) representing `TransactionType || TransactionPayload` or `LegacyTransaction` as defined in [EIP-2718](https://eips.ethereum.org/EIPS/eip-2718).
+
+## Routines
+
+### Payload building
+
+This routine follows the same specification as [Payload building](./paris.md#payload-building) with the following changes to the processing flow:
+
+1. Client software **SHOULD** take `payloadAttributes.inclusionList` into account during the payload build process. The built `ExecutionPayload` **MUST** satisfy the inclusion list constraints with respect to `payloadAttributes.inclusionList` as defined in [EIP-7805](https://eips.ethereum.org/EIPS/eip-7805).
+
 ## Methods
 
 ### engine_newPayloadV5
@@ -51,13 +75,16 @@ Method parameter list is extended with `inclusionList`.
 
 #### Response
 
-Refer to the response for [`engine_newPayloadV4`](./prague.md#engine_newpayloadv4).
+* result: [`PayloadStatusV1`](./paris.md#payloadstatusv1), values of the `status` field are modified in the following way:
+  - `INVALID_BLOCK_HASH` status value is supplanted by `INVALID`.
+  - `INCLUSION_LIST_UNSATISFIED` status value is appended.
+* error: code and message set in case an exception happens while processing the payload.
 
 #### Specification
 
 This method follows the same specification as [`engine_newPayloadV4`](./prague.md#engine_newpayloadv4) with the following changes:
 
-1. Client software **MUST** return `{status: INVALID_INCLUSION_LIST, latestValidHash: null, validationError: null}` if there are any transactions of `inclusionList` that are not part of the `executionPayload`, even if they can be appended at the end of the `executionPayload`.
+1. Client software **MUST** return `{status: INCLUSION_LIST_UNSATISFIED, latestValidHash: null, validationError: null}` if `executionPayload` fails to satisfy the inclusion list constraints with respect to `inclusionList` as defined in [EIP-7805](https://eips.ethereum.org/EIPS/eip-7805).
 
 ### engine_getInclusionListV1
 
@@ -81,35 +108,26 @@ This method follows the same specification as [`engine_newPayloadV4`](./prague.m
 
 3. Client software **MUST NOT** include any [blob transaction](https://eips.ethereum.org/EIPS/eip-4844#blob-transaction) within the provided list.
 
-### engine_updatePayloadWithInclusionListV1
+4. Client software **MUST** return `-38006: Unknown parent` error if a block with the given `parentHash` does not exist.
+ 
+### engine_forkchoiceUpdatedV4
 
 #### Request
 
-* method: `engine_updatePayloadWithInclusionListV1`
+* method: `engine_forkchoiceUpdatedV4`
 * params:
-  1. `payloadId`: `DATA`, 8 Bytes - Identifier of the payload build process.
-  2. `inclusionList`: `inclusionList`: `Array of DATA` - Array of transaction objects, each object is a byte list (`DATA`) representing `TransactionType || TransactionPayload` or `LegacyTransaction` as defined in [EIP-2718](https://eips.ethereum.org/EIPS/eip-2718).
-* timeout: 1s
+  1. `forkchoiceState`: [`ForkchoiceStateV1`](./paris.md#forkchoicestatev1).
+  2. `payloadAttributes`: `Object|null` - Instance of [`PayloadAttributesV4`](#payloadattributesv4) or `null`.
+* timeout: 8s
 
 #### Response
 
-* result: `payloadId`: `DATA|null`, 8 Bytes - identifier of the payload build process or `null`
-* error: code and message set in case an exception happens while getting the inclusion list.
+Refer to the response for [`engine_forkchoiceUpdatedV3`](./cancun.md#engine_forkchoiceupdatedv3).
 
 #### Specification
 
-1. Given the `payloadId` client software **MUST** update payload build process building with`inclusionList`. The transactions must be part of the execution payload unless it fails to be included at the end of it.
-
-2. Client software **SHOULD** ignore any [blob transactions](https://eips.ethereum.org/EIPS/eip-4844#blob-transaction) present in the `inclusionList` when updating the execution payload.
-
-### Update the methods of previous forks
-
-This document defines how FOCIL payload should be handled by the [`Prague API`](./prague.md).
-
-For the following methods:
-
-- [`engine_newPayloadV4`](./prague.md#engine_newpayloadV4)
+This method follows the same specification as [`engine_forkchoiceUpdatedV3`](./cancun.md#engine_forkchoiceupdatedv3) with the following changes to the processing flow:
 
-a validation **MUST** be added:
+1. Extend point (7) of the `engine_forkchoiceUpdatedV1` [specification](./paris.md#specification-1) by defining the following sequence of checks that **MUST** be run over `payloadAttributes`:
 
-1. Client software **MUST** return `-38005: Unsupported fork` error if the `timestamp` of payload or payloadAttributes greater or equal to the FOCIL activation timestamp.
+    1. `payloadAttributes` matches the [`PayloadAttributesV4`](#payloadattributesv4) structure, return `-38003: Invalid payload attributes` on failure.