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

Light client API standardization #3079

Closed
wemeetagain opened this issue Sep 3, 2021 · 4 comments
Closed

Light client API standardization #3079

wemeetagain opened this issue Sep 3, 2021 · 4 comments
Assignees
Labels
prio-medium Resolve this some time soon (tm). scope-light-clients All issues regarding light client development.

Comments

@wemeetagain
Copy link
Member

The light client syncing API should be standardized and available as a REST API.

Build consensus, write specifications, implement pocs, etc to bring the syncing API to standardization and production.

@wemeetagain wemeetagain self-assigned this Sep 3, 2021
@q9f q9f added mod4-api prio-medium Resolve this some time soon (tm). and removed q5-substantial labels Sep 14, 2021
@philknows
Copy link
Member

Create buy-in for other clients to implement. Link to the PR.

@philknows
Copy link
Member

Reference: ethereum/beacon-APIs#181

@philknows
Copy link
Member

It has been identified in the March 29 call and recently on Twitter that we need should tweak the API to allow for syncing to finalized or to head. cc: @wemeetagain @dapplion

@philknows philknows added the scope-light-clients All issues regarding light client development. label May 10, 2022
@philknows
Copy link
Member

Can we close this for #3952 @wemeetagain ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prio-medium Resolve this some time soon (tm). scope-light-clients All issues regarding light client development.
Projects
None yet
Development

No branches or pull requests

4 participants