You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
@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).
We should some higher level endpoints to the RPC for things like
beacon_getLightClientUpdate
andbeacon_getBootstrap
and maybebeacon_lightClientStatus
to allow visibility into how our embedded light client is doing (i.e. is it tracking the head of the chain, etc).The text was updated successfully, but these errors were encountered: