status-im
/
eth2.0-specs
mirror of https://github.com/status-im/eth2.0-specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add EE assumptions

This commit is contained in:
Paul Hauner 2021-12-14 15:44:15 +11:00
parent 2c62ed3b77
commit 497b5f8cbb
No known key found for this signature in database
GPG Key ID: 5E2CFF9B75FA63DF
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
sync/optimistic.md
View File

@ -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 message as a `SYNCING`, `VALID` or `INVALID` response. A consensus engine MAY
queue such a message for later processing. 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 ## Merge Transition
To protect against attacks during the transition from empty `ExecutionPayload` To protect against attacks during the transition from empty `ExecutionPayload`