4 Commits (06cbc80754c3930828cc605f151554bc7ec36eb9)

Author	SHA1	Message	Date
zhiqiangxu	84a80216c6	beacon/light: optimize lock usage in `HeadTracker` (#30485) ... minimizes the time when the lock is held	2 months ago
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
Aaron Chen	723b1e36ad	all: fix mismatched names in comments (#29348) ... * all: fix mismatched names in comments * metrics: fix mismatched name in UpdateIfGt	8 months ago
Felföldi Zsolt	aadcb88675	cmd/blsync, beacon/light: beacon chain light client (#28822) ... Here we add a beacon chain light client for use by geth. Geth can now be configured to run against a beacon chain API endpoint, without pointing a CL to it. To set this up, use the `--beacon.api` flag. Information provided by the beacon chain is verified, i.e. geth does not blindly trust the beacon API endpoint in this mode. The root of trust are the beacon chain 'sync committees'. The configured beacon API endpoint must provide light client data. At this time, only Lodestar and Nimbus provide the necessary APIs. There is also a standalone tool, cmd/blsync, which uses the beacon chain light client to drive any EL implementation via its engine API. --------- Co-authored-by: Felix Lange <fjl@twurst.com>	9 months ago