Repository navigation
Keep the Nimbus VC slashing protection DB across restarts - #491
Merged
Merged
Conversation
OisinKyne
approved these changes
Oct 5, 2026
KaloyanTanev
force-pushed
the
kalo/nimbus-keep-slashing-db
branch
from
October 5, 2026 14:03
b090b40 to
74be8ec
Compare
|
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.
nimbus/run.shranrm -rf /home/user/dataon every start, which also wiped the Nimbus VC's slashing protection DB (validators/slashing_protection.sqlite3). It now removes only the previously imported keys (secrets/andvalidators/0x*) before re-importing them, matching charon-distributed-validator-cluster.Before #490 the wipe mostly failed silently, because uid 1000 couldn't write to the root-owned
./data/vc-nimbus. Now that #490 hands that directory to uid 1000, it succeeds on every restart.