-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Dump state and restart #131
Comments
Yup, I think there was some attempt in tooling for merkleeyes for a generic restart tooling. Or should this be basecoin-specific stuff? |
Is "upgrades where we throw away history" a desired capability at launch? What's an example of an upgrade that would require this - a serialization format upgrade where the store needs to be rewritten? |
Relevant - #758 - if we implement a simple "dump store state to JSON", should solve both. |
Sure. Usecase was constant breaking testnets where we kept throwing away history. It would have been nice to easily transfer the balances on an upgrade. Maybe this is unnecessary now. But if people ask some way to do this, it would be nice to give some path. JSON dump is nice... |
Yes if there are changes in execution logic but you have a latest state you want to preserve, ideally we can dump this to json, and use it in the genesi json of a new chain |
If our goal is to allow restarting from a new Besides the utility in easily making large changes (serialization format) and restarting the chain while retaining state, this is also a convenient debugging/analysis tool in general: JSON from It does, however, require that all modules can enumerate over all state (e.g. accounts). Example implementation of a |
Additionally, applications using the SDK, including |
Example |
Closed by #901. |
* Remove error from priv.PubKey() * Update changelog
* iavl v0.17.3-osmo-v4.rc2 * upgrade iavl to v0.17.3-osmo-v4
We need a way to dump state to a neutral format that can be included in a genesis.json so we can do upgrades where we throw away history
The text was updated successfully, but these errors were encountered: