You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we need to wait until the beacon chain sends us a new payload followed by an FCU until we start syncing. We could (in theory) just fetch the payload that we are FCU'd to from the network and start syncing way earlier.
This is a big problem on networks without new blocks being built, since we will not be able to sync them without new fork-choices
The text was updated successfully, but these errors were encountered:
Light CL nodes would no longer be required to leech beacon blocks gossip (they cannot fully validate, so can't be active peers on it) to drive EL while the full CL is undergoing maintenance.
Conversely, it might useful to also start sync on newPayload to fetch side chains as part of exploring their validity, for example after an execution client bug :) this would allow the CL to discard such chains after optimistically having synced them without choosing them as the current fork.
Rationale
Right now we need to wait until the beacon chain sends us a new payload followed by an FCU until we start syncing. We could (in theory) just fetch the payload that we are FCU'd to from the network and start syncing way earlier.
This is a big problem on networks without new blocks being built, since we will not be able to sync them without new fork-choices
The text was updated successfully, but these errors were encountered: