-
Notifications
You must be signed in to change notification settings - Fork 22
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
Altair genesis seems to use phase0 BeaconBlockBody
in latest_block_header
#7
Comments
It seems that to fix this would require updating |
Genesis initialization seems to occur in Lines 50 to 64 in e6966a1
|
Closing as @moshe-blox found that the incompatibility was due to an old bundled version of |
Fix is ready: ethpandaops/ethereum-genesis-generator#7 |
Altair genesis networks generated with this tool are incompatible with Lighthouse, failing due a mismatch between the genesis block root derived from the genesis state's
latest_block_header
and the genesis block root derived by creating an emptyaltair.BeaconBlock
containing the genesis state'sstate_root
.For example, for the attached
testnet-dir
from Moshe Revah at @bloxapp the derived genesis block roots are:0x49a68856395936166cdebb98e7d8e5b354ebe5a809dd7731021f6625b9b0b453
from thelatest_block_header
(wrong)0xb03680d13635efb166b3a5a6f44e5d1d2b6cf78f6bbde1ecdff7cdbc7ff019a6
from an emptyaltair.BeaconBlock
(correct)The Lighthouse code for computing each root is:
According to the spec, the
latest_block_header
should use an Altair block and should maintain the invariant that the block roots derived via these two methods are identical: https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md#initialize-state-for-pure-altair-testnets-and-test-vectorsTherefore I believe this is a bug in
eth2-testnet-genesis
, although I can't spot it in a quick skim ofaltair.go
.testnet-dir.zip
The text was updated successfully, but these errors were encountered: