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.

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

conway-genesis.json not matching the expected hash #74

Closed
robinboening opened this issue Jun 20, 2024 · 2 comments
Closed

conway-genesis.json not matching the expected hash #74

robinboening opened this issue Jun 20, 2024 · 2 comments

Comments

@robinboening
Copy link
Contributor

robinboening commented Jun 20, 2024

The currently provided conway-genesis json wasn't working. The node failed with

cardano-node: Conway related : Wrong genesis file: the actual hash is "b84bce2d465bcdb38ebd873f126a866d7ebceb154357496396fb602104329299", but the expected genesis hash given in the node configuration file is "de609b281cb3d8ae91a9d63a00c87092975612d603aa54c0f1c6a781e33d6e1e"

I had to copy the original json from here https://book.world.dev.cardano.org/environments/mainnet/conway-genesis.json to make it match the expected hash.

I can see the latest change of the file made it in to the docker image and it looks identical to the source hosted at cardano.org. I am failing to see why it isn't working with the file shipped in the image.

@abracadaniel
Copy link
Owner

The container doesn't automatically update the config.json and genesis files when changes are made to those during version updates. That will have to be done manually, or by running the init_config. Could that be the issue?

@robinboening
Copy link
Contributor Author

Thank you! Yes, that makes total sense indeed! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants