status-im/eth2.0-specs
2
0
Fork 0
mirror of https://github.com/status-im/eth2.0-specs.git synced 2025-03-01 18:50:35 +00:00
Code Issues Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source 
Co-authored-by: Hsiao-Wei Wang <hsiaowei.eth@gmail.com>
This commit is contained in:
Mikhail Kalinin 2022-07-29 17:31:32 +06:00 committed by GitHub
parent 29b3afeff3
commit 47ee4308fc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
sync/optimistic.md
View File

@ -272,10 +272,10 @@ optimistic blocks (and vice-versa).
### Why sync optimistically? ### 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. 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 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. because the recent state soon becomes unavailable due to state trie pruning.