Official Go implementation of the Ethereum protocol

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Felföldi Zsolt 256d4b099c beacon/light: request finality update explicitly when necessary (#29567) ... This PR adds an extra mechanism to sync.HeadSync that tries to retrieve the latest finality update from every server each time it sends an optimistic update in a new epoch (unless we already have a validated finality update attested in the same epoch). Note that this is not necessary and does not happen if the new finality update is delivered before the optimistic update. The spec only mandates light_client_finality_update events when a new epoch is finalized. If the chain does not finalize for a while then we might need an explicit request that returns a finality proof that proves the same finality epoch from the latest attested epoch.		7 months ago
..
head_sync.go	beacon/light: request finality update explicitly when necessary (#29567)	7 months ago
head_sync_test.go	beacon/light: request finality update explicitly when necessary (#29567)	7 months ago
test_helpers.go	beacon/light: request finality update explicitly when necessary (#29567)	7 months ago
types.go	beacon/light: request finality update explicitly when necessary (#29567)	7 months ago
update_sync.go	beacon/light: request finality update explicitly when necessary (#29567)	7 months ago
update_sync_test.go	beacon/light: request finality update explicitly when necessary (#29567)	7 months ago