-
Notifications
You must be signed in to change notification settings - Fork 289
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
fix: mocha block sync on v2.x #3843
Conversation
What about just defaulting to 1 if it is empty? |
I can do. The current approach only special cases mocha-4 b/c that's the only testnet we support that has an empty app version. IMO future chains (even testnets) should have an initial app version populated so this approach doesn't default to 1 for them, instead it panics. |
Discussed w/ Callum offline and decided to not special case mocha. Instead we'll default to app version 1. |
Need to forward port this to main |
Moving to draft. Discussion w/ @cmwaters :
|
a6fd76b
to
b540ee9
Compare
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.
LGTM
Closes #3840 by implementing option 2 because it seems like a bad practice to modify
genesis.json
after the chain has launched.Blocked on celestiaorg/celestia-core#1469Testing
I can state sync and block sync on Arabica and Mocha