Add operator rollback and slashing recovery guides#127
Merged
Conversation
Neotamandua
previously approved these changes
May 28, 2026
Co-authored-by: Neotamandua <107320179+Neotamandua@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Adds operator-facing recovery docs for two cases that have come up in support:
node-installerreleaseThe rollback guide covers mainnet/testnet commands, verification steps, and downgrade caveats. The slashing guide focuses on restoring healthy node operation first: version, sync status, logs, staking status, and post-recovery monitoring. It also explains that if the node is healthy again, operators should unstake and restake, since slashing can be caused by temporary operational issues such as cloud downtime, network disruption, or downtime during a live node update.