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

Add new RPC endpoints to support Beacon network data #528

Open
acolytec3 opened this issue Nov 17, 2023 · 6 comments
Open

Add new RPC endpoints to support Beacon network data #528

acolytec3 opened this issue Nov 17, 2023 · 6 comments

Comments

@acolytec3
Copy link
Collaborator

We should some higher level endpoints to the RPC for things like beacon_getLightClientUpdate and beacon_getBootstrap and maybe beacon_lightClientStatus to allow visibility into how our embedded light client is doing (i.e. is it tracking the head of the chain, etc).

@acolytec3
Copy link
Collaborator Author

@holgerd77 I'm guessing this question is related to this tracking issue maybe? If so, then this is specifically the lodestar light client and not the full beacon client. It's quite light weight but it runs inside of Ultralight and essentially just listens for beacon light client data objects that are gossiped over the portal network and updates its own internal state when it finds things its looking for (i.e. light client updates and optimistic updates).

@holgerd77
Copy link
Member

Haha, yes.

@acolytec3
Copy link
Collaborator Author

Have added:

  • beacon_getHead - returns the capella fork Light Client Header corresponding to the current known head block
  • beacon_getFinalized - returns the capella fork Light Client Header corresponding to the current known Finalized block

@acolytec3
Copy link
Collaborator Author

Added beacon_getLightClientUpdate was added in #530

@acolytec3
Copy link
Collaborator Author

This PR documents all the official beacon RPC endpoints we should implement. I think we have most of them already but should confirm against this list.

@acolytec3
Copy link
Collaborator Author

We're missing quite a few after referencing the list above. But, we're missing lots of endpoints all around, the entire trace sub-namespace is missing so we should think about implementing some of these.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants