-
Notifications
You must be signed in to change notification settings - Fork 973
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
Fix initialize_beacon_state_from_eth1
previous_version
#2634
Conversation
On second thought, I’m not convinced what correct behavior for this versioning is.
Because of the above, I’d argue to either initialize it to The altair analogue of this function uses |
my two cents (just because I raised the problem). current_version=MERGE_FORK_VERSION, # [Modified in Merge]
previous_version=current_version I was also exploring the idea about introducing a non-configurable constant |
My institution was making it more like a mainnet real case, but you convinced me that If possible, I'd like to also change Altair Note: it has nothing to do with the mainnet consensus, just for testing. |
Agreed that it's reasonable to adjust the altair function as well. This affects not only testing, but also testnets/networks that deploy their genesis from altair logic. I don't think we have any such nets today, so it's okay to introduce this change |
Thank @tbenr for finding this error!