From a3b7c6c5055fccdf529145f63946a75108910001 Mon Sep 17 00:00:00 2001 From: Mikhail Kalinin Date: Tue, 2 Aug 2022 12:25:15 +0600 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Danny Ryan --- sync/optimistic.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sync/optimistic.md b/sync/optimistic.md index 6d8f67e424..1511ce8594 100644 --- a/sync/optimistic.md +++ b/sync/optimistic.md @@ -279,9 +279,9 @@ State sync requires the knowledge of the current head of the chain to converge e If not constantly fed with the most recent head, state sync won't be able to complete because the recent state soon becomes unavailable due to state trie pruning. -Optimistic block import (i.e. import without waiting for a payload to be executed by the engine) -breaks a deadlock between the state sync and processing a beacon block by skipping payload -execution as long as execution engine is syncing. +Optimistic block import (i.e. import when the execution engine *cannot* currently validate the payload) +breaks a deadlock between the execution layer sync process and importing beacon blocks +while the execution engine is syncing. Optimistic sync works nicely with execution engines using block execution as a default sync mechanism (e.g. Erigon). It makes optimistic sync a *generalized* solution for