-
Notifications
You must be signed in to change notification settings - Fork 106
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
distributable node snapshot #4370
Comments
You mean something like this https://docs.oasis.dev/general/run-a-node/advanced/copy-state-from-one-node-to-the-other? |
oh ok yeah. since we have that written up, let's go ahead and check that first item off the list then |
One of the validators, @Bambarello, is already providing such a snapshot. See https://github.com/Bambarello/cosmos-snapshots and http://snapshots.alexvalidator.com:8081/. Is this what you mean @pro-wh? |
Yeah, I think those are the kind of snapshot. Thanks for sharing the links. The remaining item in this issue is about adding a tool for creating those snapshots. |
We now also have Oasis Snapshots (https://snapshots.oasis.io/), an official service providing Oasis Network snapshots. |
However, there is no snapshot data for the latest version (oasis-4) |
You should be able to sync the latest version from genesis very quickly so no snapshot is needed yet ;) |
I used statesync to start up, but I couldn't sync the data Log: |
It is too early for the new network for there to be any snapshots available. Just sync from genesis, it should be quite fast. |
I see what this means, the pre-V4 data is almost completely discarded, but the block height does not start at 0. Thank you very much |
suppose I have a "serverdir" of a node that's synced. Someone wants to get my copy of that.
goal:
formulate instructions for how to prepare a distributable (i.e. no secret information) bundle of a synced node's state so that recipient can get chain history from a trusted sourcedoneThe text was updated successfully, but these errors were encountered: