-
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
mocha-4 genesis file does not define an app version #3840
Comments
is it possible to modify the genesis and sync an existing network from scratch? if so, is that a bug? my understanding of the genesis is that its the first block. edit: |
As an alternative to modifying the genesis file: can celestia-app interpret an Did this only surface for DevOps maintained Mocha nodes because it was a regression in v2.x.x? |
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#1469 ## Testing I can state sync and block sync on Arabica and Mocha ```shell ./scripts/arabica.sh ./scripts/arabica-block-sync.sh ./scripts/mocha.sh ./scripts/mocha-block-sync.sh ```
Context
https://celestia-team.slack.com/archives/C02PFFCGMNW/p1725353291554399?thread_ts=1725273825.398589&cid=C02PFFCGMNW
Problem
Attempt to sync a v2.1.2 node from genesis with the genesis.json file defined at https://github.com/celestiaorg/networks/blob/master/mocha-4/genesis.json
Proposal
Option 1: modify Mocha genesis.json
Option 2: modify celestia-app to accomodate mocha-4's lack of app version in genesis.json
The text was updated successfully, but these errors were encountered: