-
Notifications
You must be signed in to change notification settings - Fork 71
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
Snapshots are not contiguous #2169
Comments
If you want the blocks to start from genesis, either you need to sync from genesis or download a blocks.log from someone. Snapshots only contain the state at exactly the time (block height) of the snapshot. No history. |
@matthewdarwin how big is a full block log now for EOS? |
it's just under 3TiB |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello. I am trying to bootstrap a leap 5.0.0 node completely from the snapshots provided here. I want my
blocks.log
file to begin from genesis. Unfortunately, there does not seem to be a way to achieve this. I tried restoring fromsnapshot-2024-01-30-22-eos-v6-0354914962.bin
, and while that worked successfully, it doesn't give me all the blocks prior to 354914963. When I tried to add the next snapshot in the list, I received this error:I am invoking leap as follows:
Is this user error? Are the official snapshots intended to be non-contiguous? I do not want to wait months for the node to sync.
The text was updated successfully, but these errors were encountered: