feat(network): add state persistence for P-Chain data across restarts #7
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
Problem
Loss of P-Chain state or custom subnet tracking on node restart. When running
lux network startandlux network stopcycles, the P-Chain registrations, subnet data, validator sets, and balances were not being preserved.Solution
This PR implements automatic state persistence by:
network_state.jsonduringnetwork stopnetwork start--no-snapshotflag for users who want a clean start--dev-modeflag for automatic subnet trackingTest plan