Scripts for syncing an archive node from genesis. #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 tasks
scirner22
previously approved these changes
Jun 17, 2024
allow completed touch-file to execute after an upgrade is hit
|
This PR is in draft/progress as it is currently being tested (in full). When that process complete (and there are no further changes) I will move this to ready for review and merge. |
|
This has been tested locally and was used to build up archive snapshots. |
iramiller
commented
Sep 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a set of basic scripts for creating an archive node that is synced from genesis. A conscious choice was made to use separate and simple scripts for each version so that any associated changes associated with that upgrade can be included (such as switching database backends from cleveldb to goleveldb.
This process is a useful solution for #24 as we have noticed that many users that need an archive node prefer to create their instance directly and not rely on snapshots created by others for integrity and security reasons.