eth2.0-specs/specs/altair
Etan Kissling 56363cd94a
Define libp2p protocol for light client sync
While the current Altair specs define structures to aid light client
development, one missing key aspect is the network protocol definition.

Certain implementations have started defining their own REST based APIs,
e.g., Lodestar at https://github.com/ChainSafe/lodestar/blob/master/packages/api/src/routes/lightclient.ts
While such APIs are useful, REST does not seem to be the ideomatic
choice as the sole API available at such a low level for Ethereum.

This patch introduces a libp2p based protocol to allow light clients to
sync to the latest `BeaconBlockHeader` in a trustless and decentralized
manner, building on top of prior work from:
- @hwwhww at https://github.com/ethereum/consensus-specs/pull/2267
- @jinfwhuang at https://github.com/ethereum/consensus-specs/pull/2786
- Lodestar's REST API (also has an endpoint to fetch merkle proofs!)
2022-07-22 17:56:41 +02:00
..
light-client Define libp2p protocol for light client sync 2022-07-22 17:56:41 +02:00
beacon-chain.md PR feedback from @ralexstokes 2022-07-18 14:45:00 +08:00
bls.md rename eth1 and eth2 throughout specs and readme where reasonable 2021-08-18 17:13:24 -06:00
fork.md Move `compute_fork_version` to `fork.md` 2022-06-23 21:03:24 +02:00
p2p-interface.md Ignore subset aggregates (#2847) 2022-05-17 07:05:22 -06:00
validator.md Move `sync-protocol.md` into `light-client` subdir 2022-07-15 13:22:14 +02:00