-
Notifications
You must be signed in to change notification settings - Fork 242
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
encapsulate LC data variables into single structure #3777
Conversation
Combines the LC data configuration options (serve / importMode), the callbacks (finality / optimistic LC update) as well as the cache storing light client data, into a new `LightClientDataStore` structure. Also moves the structure into a light client specific file.
@@ -79,3 +79,26 @@ type | |||
|
|||
importTailSlot*: Slot | |||
## The earliest slot for which light client data is imported. | |||
|
|||
LightClientDataStore* = object |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
technically, this is a "light server" store
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, haha, but that terminology is nowhere used yet, so sticking with "light client data" for now (technically, a client could also cache the obtained data and then provide it to others, or use it to roll-back in case it fails to advance when there is no supermajority, so use case of this data is not limited to just server)
Combines the LC data configuration options (serve / importMode), the
callbacks (finality / optimistic LC update) as well as the cache storing
light client data, into a new
LightClientDataStore
structure.Also moves the structure into a light client specific file.