github/consensus-specs
1
1
Fork 0
mirror of https://github.com/ethereum/consensus-specs.git synced 2026-02-01 23:05:12 -05:00
Code Issues Packages Projects Releases Wiki Activity

Add note about full verification

Browse Source
This commit is contained in:
Paul Hauner
2021-12-14 16:21:30 +11:00
parent 9d7d4d0869
commit 4f1d8152d5
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
sync/optimistic.md
View File

@@ -22,6 +22,11 @@ set:
- `optimistic_roots: Set[Root]`: `hash_tree_root(block)` where
`block.body.execution_payload` is known to be `SYNCING`.
Notably, blocks included in `optimistic_roots` have passed all verifications
included in `process_block` (noting the modifications to the
`execute_payload`). I.e., the blocks are fully verified but awaiting execution
of the `ExecutionPayload`.
A consensus engine MUST be able to retrospectively (i.e., after import) modify
the status of `SYNCING` blocks to be either `VALID` or `INVALID` based upon responses
from an execution engine. I.e., perform the following transitions: