From 9352f127ef1c3cc324749ae8f82d00daea578953 Mon Sep 17 00:00:00 2001 From: Danny Ryan Date: Tue, 9 Aug 2022 07:49:41 -0600 Subject: [PATCH] minor typo --- sync/optimistic.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sync/optimistic.md b/sync/optimistic.md index b2a30aef68..ea0ed75007 100644 --- a/sync/optimistic.md +++ b/sync/optimistic.md @@ -285,7 +285,7 @@ while the execution engine is syncing. Optimistic sync is also an optimal strategy for execution engines using block execution as a default sync mechanism (e.g. Erigon). Alternatively, a consensus engine may inform the execution engine with a payload -obtained from a checkpoint block, then wait till the execution layer catches up with it and proceed +obtained from a checkpoint block, then wait until the execution layer catches up with it and proceed in lock step after that. This alternative approach would keep user in limbo for several hours and would increase time of the sync process as batch sync has more opportunities for optimisation than the lock step.