Fix dependent root retrival genesis case #14053
Merged
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.
#14039 fixed several issues related to duty retrieval. One key fix was to avoid heavily mutating the state for retrieving the beacon state proposer. However, after merging the PR, we realized it broke long-running end-to-end tests for the beacon API.
Currently, getting the dependent root does not work in the genesis case. A genesis state does not have any dependent root when requesting at slot 0, as demonstrated by these two test cases:
This PR fixes the issue by using the genesis root in the beacon database if the genesis epoch is specified in the request.