4 Commits (a0e6381c48e95e42b70f7ac7018f690596de3fc6)

Author	SHA1	Message	Date
Felföldi Zsolt	7cbce8ed58	beacon/blsync: remove cli dependencies (#30720) ... This PR moves chain config related code (config file processing, fork logic, network defaults) from `beacon/types` and `beacon/blsync` into `beacon/params` while the command line flag logic of the chain config is moved into `cmd/utils`, thereby removing the cli dependencies from package `beacon` and its sub-packages.	4 months ago
zhiqiangxu	87465e98f9	beacon/light: remove unused CommitteeChain.signerThreshold (#30484) ... This field is a duplicate of UpdateScore.SignerCount and never referenced.	4 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>	12 months ago
Felföldi Zsolt	fff843cfaf	beacon/light: add CommitteeChain (#27766) ... This change implements CommitteeChain which is a key component of the beacon light client. It is a passive data structure that can validate, hold and update a chain of beacon light sync committees and updates, starting from a checkpoint that proves the starting committee through a beacon block hash, header and corresponding state. Once synced to the current sync period, CommitteeChain can also validate signed beacon headers.	1 year ago