5 Commits (5f6cb5313031dbd99b47052e205bd347913062a3)

Author	SHA1	Message	Date
Felföldi Zsolt	86150af2e5	beacon/light: fix shutdown issues (#29946) ... * beacon/light/request: add server test for event after unsubscribe * beacon/light/api: fixed double stream.Close() * beacon/light/request: add checks for nil event callback function * beacon/light/request: unlock server mutex while unsubscribing from parent	5 months ago
Felföldi Zsolt	e6689fe090	beacon/light/sync: print error log if checkpoint retrieval fails (#29532) ... Co-authored-by: Felix Lange <fjl@twurst.com>	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
guangwu	ebf9e11af2	beacon/light/request: fix typos (#29216)	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>	8 months ago