ChainSafe / ChainSafe/gossamer-parity
Implement dump state
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
## Issue summary
- By default user run fork without persistance of changes.
- User can use `--dump-state` flag to dump current state including his changes to provided file.
- User then later can start anvil from his localdump file using `--load-state ` flag
- User can use `-s, --state-interval ` flag to dump state to the disk every N secodns.
## Other information and links
-
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the CLI entry points that define the fork and state-related flags, then trace how the current state is represented. Done means supporting --dump-state, --load-state, and periodic -s/--state-interval persistence as described.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100