Allow get_beacon_proposer_index at next epoch #8235
+13
−3
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.
Proposed Changes
Continued cleanup of proposer index logic, this PR allows
get_beacon_proposer_index
to be called at the next epoch (post-Fulu), bringing it in line withget_beacon_proposer_indices
after the changes in:This is a safe change for Fulu due to the newly introduced lookahead.
Additional Info
This change is non-essential for correctness, as
get_beacon_proposer_index
is currently only called for the current epoch (state.slot()
orblock.slot()
after state advance), and in tests.