feat(beacon-network): add json-rpc method to get the latest finalized state root #1364
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was wrong?
To be able to validate
HistoricalSummariesWithProof, we want to access the latest finalized beacon state root from the light client module.The current design in HeaderOracle relies on JSON-RPC requests for accessing the data from the overlay networks.
This endpoint is required for fixing #1323.
Here is a PR to add the endpoint to beacon json-rpc specs as it will be useful for hive testing.
How was it fixed?
portal_beaconFinalizedStateRootjson-rpc endpoint.This endpoint was tested locally with beacon synced node.
To-Do