-
Notifications
You must be signed in to change notification settings - Fork 166
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 LightClientHeader
wrapper
#287
Conversation
The light client data structures were changed to accommodate additional fields in future forks (e.g., to also hold execution data). There is a minor change to the JSON serialization, where the `header` properties are now nested inside a `LightClientHeader`. The SSZ serialization remains compatible. See ethereum/consensus-specs#3190
(This one should only be merged if ethereum/consensus-specs#3190 gets accepted). |
The light client data structures were changed to accommodate additional fields in future forks (e.g., to also hold execution data). There is a minor change to the JSON serialization, where the `header` properties are now nested inside a `LightClientHeader`. The SSZ serialization remains compatible. See ethereum/consensus-specs#3190 and ethereum/beacon-APIs#287
The light client data structures were changed to accommodate additional fields in future forks (e.g., to also hold execution data). There is a minor change to the JSON serialization, where the `header` properties are now nested inside a `LightClientHeader`. The SSZ serialization remains compatible. See ethereum/consensus-specs#3190 and ethereum/beacon-APIs#287
The light client data structures were changed to accommodate additional fields in future forks (e.g., to also hold execution data). There is a minor change to the JSON serialization, where the `header` properties are now nested inside a `LightClientHeader`. The SSZ serialization remains compatible. See ethereum/consensus-specs#3190 and ethereum/beacon-APIs#287
The light client data structures were changed to accommodate additional fields in future forks (e.g., to also hold execution data). There is a minor change to the JSON serialization, where the `header` properties are now nested inside a `LightClientHeader`. The SSZ serialization remains compatible. See ethereum/consensus-specs#3190 and ethereum/beacon-APIs#287
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.
Lgtm
ick i didnt follow my own suggestion and ask for this to be added to change log :/ |
Already is listed, the change is for an API that was not yet part of a release. In CHANGES.md, I noticed just now though that they incorrectly refer to |
ah ok, that'll be my fault, i did a huge batch to get changes started |
The light client data structures were changed to accommodate additional fields in future forks (e.g., to also hold execution data).
There is a minor change to the JSON serialization, where the
header
properties are now nested inside aLightClientHeader
. The SSZ serialization remains compatible.See ethereum/consensus-specs#3190