From 497b5f8cbb1552f694f1ccf133e68beb87837b42 Mon Sep 17 00:00:00 2001 From: Paul Hauner Date: Tue, 14 Dec 2021 15:44:15 +1100 Subject: [PATCH] Add EE assumptions --- sync/optimistic.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/sync/optimistic.md b/sync/optimistic.md index be5626bf1..63c060009 100644 --- a/sync/optimistic.md +++ b/sync/optimistic.md @@ -49,6 +49,15 @@ A consensus engine MUST NOT interpret an error or failure to respond to a message as a `SYNCING`, `VALID` or `INVALID` response. A consensus engine MAY queue such a message for later processing. +### Assumptions about Execution Engine Behaviour + +This specification assumes execution engines will only return `SYNCING` when +there is insufficient information available to make a `VALID` or `INVALID` +determination on the given `ExecutionPayload` (e.g., the parent payload is +unknown). Specifically, `SYNCING` responses should be fork-specific; the search +for a block on one chain MUST NOT trigger a `SYNCING` response for another +chain. + ## Merge Transition To protect against attacks during the transition from empty `ExecutionPayload`