mirror of
https://github.com/status-im/eth2.0-specs.git
synced 2025-01-20 23:49:54 +00:00
Expand on opti-sync in context of block sync
This commit is contained in:
parent
a3b7c6c505
commit
b9476bf0ee
@ -283,9 +283,14 @@ Optimistic block import (i.e. import when the execution engine *cannot* currentl
|
|||||||
breaks a deadlock between the execution layer sync process and importing beacon blocks
|
breaks a deadlock between the execution layer sync process and importing beacon blocks
|
||||||
while the execution engine is syncing.
|
while the execution engine is syncing.
|
||||||
|
|
||||||
Optimistic sync works nicely with execution engines using block execution as a default
|
Optimistic sync is also an optimal strategy for execution engines using block execution as a default
|
||||||
sync mechanism (e.g. Erigon). It makes optimistic sync a *generalized* solution for
|
sync mechanism (e.g. Erigon). Alternatively, a consensus engine may inform the execution engine with a payload
|
||||||
interaction between consensus and execution engine during the sync process.
|
obtained from a checkpoint block, then wait till 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.
|
||||||
|
|
||||||
|
Aforementioned premises make optimistic sync a *generalized* solution for interaction between consensus and
|
||||||
|
execution engines during the sync process.
|
||||||
|
|
||||||
### Why `SAFE_SLOTS_TO_IMPORT_OPTIMISTICALLY`?
|
### Why `SAFE_SLOTS_TO_IMPORT_OPTIMISTICALLY`?
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user