Backup and restore instructions for nonce files #543
+9
−0
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
germanD
reviewed
Feb 11, 2025
There was a problem hiding this comment.
LGTM modulo threads
As a follow up, we should check with the L1 bakewr crew if both files actually need backing up. My understanding is that with current versions of Octez keeping the stateful one should suffice, and the other one can be safely removed.
But I would rather be safe than sorry.
Co-authored-by: Germán Delbianco <[email protected]>
Co-authored-by: Germán Delbianco <[email protected]>
timothymcmackin
force-pushed
the
backup-nonces
branch
from
88ff284 to
329bbdb
Compare
germanD
approved these changes
Feb 11, 2025
| The Octez baking daemon stores persistent operational data in the Octez client's data directory, notably consensus high-water marks and [random seed nonces](https://tezos.gitlab.io/active/randomness_generation.html). | ||
| If you want to back up the baker or move it to another machine and restore it, you must copy the nonce file or files from the Octez client's data directory to the equivalent directory on the new machine. | ||
| These nonce files are named `net<NETWORK_ID>_stateful_nonces` and `net<NETWORK_ID>_nonces`, where `<NETWORK_ID>` is the ID of the network, such as `netXdQprcVkpaWU_stateful_nonces` for Mainnet or `netXnHfVqm9ie_stateful_nonces` for Ghostnet. | ||
| All systems have the `net<NETWORK_ID>_stateful_nonces` file but only legacy baking deployments have the `net<NETWORK_ID>_nonces` file. |
There was a problem hiding this comment.
Suggested change
| All systems have the `net<NETWORK_ID>_stateful_nonces` file but only legacy baking deployments have the `net<NETWORK_ID>_nonces` file. | |
| All systems have the `net<NETWORK_ID>_stateful_nonces` file but only legacy baking deployments have the `net<NETWORK_ID>_nonces` file. |
systems -> deployments.
We should expand legacy to mean, that were first deployed with Octez versions earlier/older than v20.0~rc1
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.
Need to backup nonce files if you move the baker to another machine.