-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[Migration] Location for genesis.json patches in documentation ? #5657
Comments
Official launch repo with latest mainnet genesis: https://github.com/cosmos/launch |
That's weird then, I can't migrate the current genesis.json file for cosmoshub-3 with those changes for v0.37
|
did you export for zero height prior to migrating? |
I just used the genesis.json from cosmos/launch (with changes to |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Foreword : I'm still not sure if this should go in cosmos-sdk or gaia repo.
Summary
Have a single location to obtain a correct genesis.json file from the validated one on cosmos/launch repo
Problem Definition
I'm trying to run a node with code from a recent PR I made #5648 and my genesis.json file is again not passing the validation step.
Before testing this change, I had to change the genesis.json file because of a
gentxs
issue I found out after digging a little bit : #5518 (comment)Now it looks like this tendermint commit will break again the current genesis.json file when trying to run a client from a recent enough commit (pulling tendermint
0.33.1
instead of0.33.0
)tendermint/tendermint@6d91c1f#diff-5761519dc31df9e1fe23c78a6d4167f2R52-R53
And apparently the format for the
evidence
module initialization in the genesis.json file changed too (outside ofslashing
and into its own module)Proposal
Have a section in the documentation specifying the breaking changes regarding
genesis.json
file so that any version of gaia/cosmos-sdk is able to rungaiad validate-genesis
andgaiad start
to join mainnet.Or a few genesis.json files coming from a gaiad migrate command to see how it should be done if we want to run it locally, and with potentially hashes for the expected values to allow sharing of those files.
PS : I currently get a panic when I try to start a node with very recent version of cosmos-sdk and gaia. Is that expected because no other node runs tendermint
0.33.1
on the network ?Full backtrace :
For Admin Use
The text was updated successfully, but these errors were encountered: