Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define libp2p protocol for light client sync #2802

Merged
merged 2 commits into from
Jul 26, 2022
Merged

Define libp2p protocol for light client sync #2802

merged 2 commits into from
Jul 26, 2022

Commits on Jul 22, 2022

  1. 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 #2267
    - @jinfwhuang at #2786
    - Lodestar's REST API (also has an endpoint to fetch merkle proofs!)
    etan-status committed Jul 22, 2022
    Configuration menu
    Copy the full SHA
    56363cd View commit details
    Browse the repository at this point in the history

Commits on Jul 25, 2022

  1. Improve grammar

    Co-authored-by: Hsiao-Wei Wang <hsiaowei.eth@gmail.com>
    etan-status and hwwhww authored Jul 25, 2022
    Configuration menu
    Copy the full SHA
    52a741f View commit details
    Browse the repository at this point in the history