Skip to content

Commit

Permalink
Relax the requirement to respond with SYNCING
Browse files Browse the repository at this point in the history
  • Loading branch information
mkalinin committed Sep 24, 2021
1 parent 9bca6ed commit ab4ec22
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/engine/interop/specification.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ This structure maps on the [`ExecutionPayload`](https://github.com/ethereum/cons

5. In the case when the parent block is unknown, client software **MUST** pull the block from the network and take one of the following actions depending on the parent block properties:
- If the parent block is a PoW block as per [EIP-3675](https://eips.ethereum.org/EIPS/eip-3675#specification) definition, then all missing dependencies of the payload **MUST** be pulled from the network and validated accordingly. The call **MUST** be responded according to the validity of the payload and the chain of its ancestors.
- If the parent block is a PoS block as per [EIP-3675](https://eips.ethereum.org/EIPS/eip-3675#specification) definition, then the call **MUST** be responded with `SYNCING` status and sync process **SHOULD** be initiated accordingly.
- If the parent block is a PoS block as per [EIP-3675](https://eips.ethereum.org/EIPS/eip-3675#specification) definition, then the call **MAY** be responded with `SYNCING` status and sync process **SHOULD** be initiated accordingly.

### engine_consensusValidated

Expand Down

1 comment on commit ab4ec22

@firewolf1969
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

src/engine/interop/specification.md

Please sign in to comment.