-
Notifications
You must be signed in to change notification settings - Fork 997
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 test_genesis.py
and cleanup genesis trigger
#1202
Conversation
test_genesis.py
and fix is_genesis_trigger
In practice, a client, they would probably:
So it's unlikely they would need to regenerate Another way to describe the logic is changing the function to What do you think about it? 😸 |
Right. In practice I expect implementers to have a cache (e.g. a |
…nerator/map/list problems
5304a4a
to
a0c2f5c
Compare
|
…t, 2**DEPOSIT_CONTRACT_TREE_DEPTH` and fix tests
…about the mix-in in verification
Ready to merge imho. We can add a few additional tests after spec-freeze. Possibly even improve the efficiency of genesis construction. As clients are (very) likely not implementing it like this anyway, and state output will be the same. This description and pseudocode will at least set a baseline, and set the interface to be compatible with SSZ partials in the future. |
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.
this cleaned up nicely. Great work everyone!
test_genesis.py
and fix is_genesis_trigger
test_genesis.py
and cleanup genesis trigger
initialize_beacon_state_from_eth
is_valid_genesis_state
test_libs/pyspec/eth2spec/test/genesis/
tests