Skip to content
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.

Sign up for GitHub

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

Jump to bottom

deposit_data.json incorrect for Gnosischain #168

Closed
GLCNI opened this issue Nov 18, 2022 · 1 comment · Fixed by #172
Closed

deposit_data.json incorrect for Gnosischain #168

GLCNI opened this issue Nov 18, 2022 · 1 comment · Fixed by #172
Assignees
@cbermudez97

Comments

@GLCNI
Copy link

GLCNI commented Nov 18, 2022

Run through setup with fully synced, EL+CL clients and imported validators awaiting activation.
However, seems that the deposit_data.json is the ‘wrong network’

To Reproduce
Run through set up normally to get working EL & CL, and validator client, awaiting activation
Keys Generated
sedge keys --network gnosis

Screenshots
image
@cbermudez97
Copy link
Contributor

cbermudez97 commented Nov 21, 2022 •
edited

Hi @GLCNI. Thanks for reporting, we had the wrong fork version in our configs here. Will upload a fix for that. A quick fix for your case would be changing inside the deposit_data.json the line with "fork_version": "0000006f" to "fork_version": "00000064".

@cbermudez97 cbermudez97 mentioned this issue Nov 21, 2022
Merged
10 tasks
@GLCNI GLCNI mentioned this issue Nov 24, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cbermudez97 cbermudez97

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix wrong gnosis fork version in networks configs NethermindEth/sedge
2 participants
@cbermudez97 @GLCNI