From 47ee4308fc9e5e7f44bae7b92787b337c29642d5 Mon Sep 17 00:00:00 2001 From: Mikhail Kalinin Date: Fri, 29 Jul 2022 17:31:32 +0600 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Hsiao-Wei Wang --- sync/optimistic.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sync/optimistic.md b/sync/optimistic.md index 6af886814..6d8f67e42 100644 --- a/sync/optimistic.md +++ b/sync/optimistic.md @@ -272,10 +272,10 @@ optimistic blocks (and vice-versa). ### Why sync optimistically? -Most of execution engines use state sync as a default sync mechanism on Ethereum Mainnet +Most execution engines use state sync as a default sync mechanism on Ethereum Mainnet because executing blocks from genesis takes several weeks on commodity hardware. -State sync requires the knowledge of the current head of the chain to eventually converge. +State sync requires the knowledge of the current head of the chain to converge eventually. 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.