status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
nimbus-eth2/docs/the_nimbus_book/src/optimistic-sync.md

21 lines
1.4 KiB
Markdown
Raw Normal View History

Optimistic mode (#4262) In optimistic mode, Nimbus will sync optimistically even when the execution client is offline / not available. An optimistic node is less secure because it has not validated block transactions via the execution client and can thus not be used for validation duties.
2022-10-26 20:44:45 +00:00
# Optimistic sync
Doc fixes, part 2 (#4806) * part 2 of the initial doc fixes - spelling fixes - grammar fixes - em-dashes should be em-dashes (`—`): double dashes (`--`) are not rendered properly - reduce overusage of em-dashes, some of those should be separate sentences - use the correct syntax for notes, tips and warnings - every sentence is in a separate line (helps with future diffs) - add missing dots at the end of list items - fix some lists * sentences on separate lines in the remaining files
2023-04-11 15:42:35 +00:00
Optimistic sync is the process of syncing an execution and consensus client concurrently, without having the consensus client wait for the execution client.
During optimistic sync, the consensus client quickly syncs up to the latest consensus but delays verifying block execution payloads: it continuously informs the execution client of the latest consensus head, allowing the execution client to perform a snapshot sync directly to the latest state.
Optimistic mode (#4262) In optimistic mode, Nimbus will sync optimistically even when the execution client is offline / not available. An optimistic node is less secure because it has not validated block transactions via the execution client and can thus not be used for validation duties.
2022-10-26 20:44:45 +00:00
Once the execution client has caught up, the consensus and execution clients work in lock-step each validating the block.
Doc fixes, part 2 (#4806) * part 2 of the initial doc fixes - spelling fixes - grammar fixes - em-dashes should be em-dashes (`—`): double dashes (`--`) are not rendered properly - reduce overusage of em-dashes, some of those should be separate sentences - use the correct syntax for notes, tips and warnings - every sentence is in a separate line (helps with future diffs) - add missing dots at the end of list items - fix some lists * sentences on separate lines in the remaining files
2023-04-11 15:42:35 +00:00
Both execution and consensus clients must be fully synced to perform validation duties: while optimistically synced, validator duties (attestation, sync committee and block production work) are skipped.
Optimistic mode (#4262) In optimistic mode, Nimbus will sync optimistically even when the execution client is offline / not available. An optimistic node is less secure because it has not validated block transactions via the execution client and can thus not be used for validation duties.
2022-10-26 20:44:45 +00:00
Always-on optimistic mode (#4458) With https://github.com/status-im/nimbus-eth2/pull/4420 implemented, the checks that we perform are equivalent to those of a `SYNCING` EL - as such, we can treat missing EL the same as SYNCING and proceed with an optimistic sync. This mode of operation significantly speeds up recovery after an offline EL event because the CL is already synced and can immediately inform the EL of the latest head. It also allows using a beacon node for consensus archival queries without an execution client. * deprecate `--optimistic` flag * log block details on EL error, soften log level because we can now continue to operate * `UnviableFork` -> `Invalid` when block hash verification fails - failed hash verification is not a fork-related block issue
2023-01-04 15:51:14 +00:00
!!! info "Running without execution client"
Doc fixes, part 2 (#4806) * part 2 of the initial doc fixes - spelling fixes - grammar fixes - em-dashes should be em-dashes (`—`): double dashes (`--`) are not rendered properly - reduce overusage of em-dashes, some of those should be separate sentences - use the correct syntax for notes, tips and warnings - every sentence is in a separate line (helps with future diffs) - add missing dots at the end of list items - fix some lists * sentences on separate lines in the remaining files
2023-04-11 15:42:35 +00:00
Nimbus continues to sync optimistically when the execution client is not available thanks to its built-in execution payload verifier.
Always-on optimistic mode (#4458) With https://github.com/status-im/nimbus-eth2/pull/4420 implemented, the checks that we perform are equivalent to those of a `SYNCING` EL - as such, we can treat missing EL the same as SYNCING and proceed with an optimistic sync. This mode of operation significantly speeds up recovery after an offline EL event because the CL is already synced and can immediately inform the EL of the latest head. It also allows using a beacon node for consensus archival queries without an execution client. * deprecate `--optimistic` flag * log block details on EL error, soften log level because we can now continue to operate * `UnviableFork` -> `Invalid` when block hash verification fails - failed hash verification is not a fork-related block issue
2023-01-04 15:51:14 +00:00
Optimistic mode (#4262) In optimistic mode, Nimbus will sync optimistically even when the execution client is offline / not available. An optimistic node is less secure because it has not validated block transactions via the execution client and can thus not be used for validation duties.
2022-10-26 20:44:45 +00:00
## Identifying optimistic sync
Doc fixes, part 2 (#4806) * part 2 of the initial doc fixes - spelling fixes - grammar fixes - em-dashes should be em-dashes (`—`): double dashes (`--`) are not rendered properly - reduce overusage of em-dashes, some of those should be separate sentences - use the correct syntax for notes, tips and warnings - every sentence is in a separate line (helps with future diffs) - add missing dots at the end of list items - fix some lists * sentences on separate lines in the remaining files
2023-04-11 15:42:35 +00:00
An optimistically synced node can be identified by examining the "Slot start" log message.
When optimistically synced, the `sync` key will have a `/opt` suffix, indicating that it's waiting for the execution client to catch up:
Optimistic mode (#4262) In optimistic mode, Nimbus will sync optimistically even when the execution client is offline / not available. An optimistic node is less secure because it has not validated block transactions via the execution client and can thus not be used for validation duties.
2022-10-26 20:44:45 +00:00
```
Doc fixes, part 2 (#4806) * part 2 of the initial doc fixes - spelling fixes - grammar fixes - em-dashes should be em-dashes (`—`): double dashes (`--`) are not rendered properly - reduce overusage of em-dashes, some of those should be separate sentences - use the correct syntax for notes, tips and warnings - every sentence is in a separate line (helps with future diffs) - add missing dots at the end of list items - fix some lists * sentences on separate lines in the remaining files
2023-04-11 15:42:35 +00:00
INF 2022-10-26 18:57:35.000+02:00 Slot start topics="beacnde" slot=4998286 epoch=156196 sync=synced/opt peers=29 head=f21d399e:4998285 finalized=156194:91e2ebaf delay=467us953ns
Optimistic mode (#4262) In optimistic mode, Nimbus will sync optimistically even when the execution client is offline / not available. An optimistic node is less secure because it has not validated block transactions via the execution client and can thus not be used for validation duties.
2022-10-26 20:44:45 +00:00
```