status-im
/
eth2.0-specs
mirror of https://github.com/status-im/eth2.0-specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

clarify how the random block generator works

This commit is contained in:
Alex Stokes 2021-08-25 11:09:35 -07:00
parent 81971a8957
commit 0da1fe947d
No known key found for this signature in database
GPG Key ID: 99B3D88FD6C55A69
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
tests/core/pyspec/eth2spec/test/utils/random.py
View File

@ -100,6 +100,15 @@ def random_block(spec, state, _signed_blocks):
to produce a block over ``BLOCK_ATTEMPTS`` slots in order to produce a block over ``BLOCK_ATTEMPTS`` slots in order
to find a valid block in the event that the proposer has already been slashed. to find a valid block in the event that the proposer has already been slashed.
""" """
# NOTE: ``state`` has been "randomized" at this point and so will likely
# contain a large number of slashed validators. This function needs to return
# a valid block so it needs to check that the proposer of the next slot is not
# slashed.
# To do this, generate a ``temp_state`` to use for checking the propser in the next slot.
# This ensures no accidental mutations happen to the ``state`` the caller expects to get back
# after this function returns.
# Using a copy of the state for proposer sampling is also sound as any inputs used for the
# shuffling are fixed a few epochs prior to ``spec.get_current_epoch(state)``.
temp_state = state.copy() temp_state = state.copy()
next_slot(spec, temp_state) next_slot(spec, temp_state)
for _ in range(BLOCK_ATTEMPTS): for _ in range(BLOCK_ATTEMPTS):