-
Notifications
You must be signed in to change notification settings - Fork 992
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 Pyrmont config #7797
Add Pyrmont config #7797
Conversation
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.
Genesis time is supposed to be 1605700800.
https://github.com/protolambda/pyrmont/blob/54d7f9f563b8d89c8bfc70cb62f9032ba6bc2880/config.yaml#L20
My bad, I messed up the readme and left the old toledo genesis time in there. The config is correct |
Does Prysm check the chain ID / network ID that the eth1 RPC supports? Maybe a good feature to warn the user if they are still on goerli, while they should soon be on mainnet! |
We do check. It's here: |
* Update eth1data params to double * Update spec tests tags and state field for fssz gen * Update more spec test sha tags * Update slashing params * Update slashing precompute to use config instead of hardcoded 3 * Update slashing test values due to config changes * Update configs for slashedless test * Go mod tidy * Add toledo config (#7743) * Update genesis delay to one week (#7782) * Add Pyrmont config (#7797) * Add Pyrmont config * Fix config * Update genesis time to the correct value * Remove TestExecuteStateTransition_FullBlock * Add back missing comments * Update spectests to v1.0.0 Co-authored-by: Raul Jordan <raul@prysmaticlabs.com> Co-authored-by: Preston Van Loon <preston@prysmaticlabs.com>
This PR adds Pyrmont config
https://github.com/protolambda/pyrmont