-
Notifications
You must be signed in to change notification settings - Fork 693
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
genesis incompatibility between versions #1950
Comments
thanks for the issue @greg-szabo ! This should be fixed but just an additional point: you don't need to have the correct genesis for statesync. In fact you can have a completely blank genesis as long as the chain-id is correct. |
Actually can you confirm @greg-szabo , are you requesting the ability to validate a previous version of gaia's genesis with a more recent version? For instance gaia v6.0.0 exported genesis (cosmoshub-4) being bale to be validated by v7.1.0 gaia? |
@glnro @yaruwangway will this issue be fixed by the migration code in v8? |
We fixed export on a clean genesis, I can double check on stateful genesis. |
Hi, I think this is still not working . |
Exported a genesis from a localnet with |
This isn't a bug, rather it might be a feature we may want to support in the future. |
@julienrbrt is validating previous versions of genesis files something the sdk could support in the future? At present, my understanding is there's no way for the sdk to be able to know which version to validate against (except the current), so the expected behavior in this case would be that this fails validation. |
I don't think validating a previous genesis with a new binary should be supported. Currently, the SDK supports genesis migration, but only for different SDK versions ( |
## Description Closes: #5041 ref: cosmos/gaia#1950 (comment) --- ### Author Checklist *All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.* I have... * [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title * [ ] added `!` to the type prefix if API or client breaking change * [ ] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting)) * [ ] provided a link to the relevant issue or specification * [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/docs/building-modules) * [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing) * [ ] added a changelog entry to `CHANGELOG.md` * [ ] included comments for [documenting Go code](https://blog.golang.org/godoc) * [ ] updated the relevant documentation or specification * [ ] reviewed "Files changed" and left comments if necessary * [ ] confirmed all CI checks have passed ### Reviewers Checklist *All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.* I have... * [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title * [ ] confirmed `!` in the type prefix if API or client breaking change * [ ] confirmed all author checklist items have been addressed * [ ] reviewed state machine logic * [ ] reviewed API design and naming * [ ] reviewed documentation is accurate * [ ] reviewed tests and test coverage * [ ] manually tested (if applicable)
Closing this as the fix for this issue is forthcoming once the Hub updates the SDK to |
Summary of Bug
The Cosmos Hub (cosmoshub-4) genesis file does not pass the
validate-genesis
test withgaiad v7.1.0
. Notably:Version
v7.1.0
, v7.0.1, possibly othersThe binary is the MacOS release from this repo.
Steps to Reproduce
Expected resolution
I understand that newer versions of gaiad will introduce new features but we should have a way to still validate the genesis of yesteryear so a new node can start up, for example, using statesync.
For Admin Use
The text was updated successfully, but these errors were encountered: