Implemented a cli arg to clear beacon database on startup #10315
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.
chose
--force-clear-dbof the 2 suggested options as it seemed closer to our naming. We don't really follow that pattern generally but it's preferable to not create another random flag to remember.fixes #10313
Documentation
doc-change-requiredlabel to this PR if updates are required.Changelog
Note
Medium Risk
Adds an explicit startup path that deletes local beacon chain database files, which is inherently destructive if misused. Scope is limited to an opt-in CLI flag and preserves validator slashing protection data.
Overview
Adds a new
--force-clear-dbCLI flag that, when enabled, deletes the beacon node’s on-disk chain database on startup (while explicitly preserving validator slashing protection).Refactors the Ephemery reset helper into
BeaconDatabaseResetand centralizes storage path/filename constants inVersionedDatabaseFactory(now public), updating related storage/config tests and callers accordingly, and documents the new flag inCHANGELOG.md.Written by Cursor Bugbot for commit a2a9daa. This will update automatically on new commits. Configure here.