feat(mocknet): use neard fork-network to set up mocknet nodes #11034
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.
This adds support in neard_runner.py for nodes whose initial state will be created via
neard fork-network
instead of by parsing a big records json file. This will result in much faster startup times.It will be implemented by detecting what files exist in the
~/.near/setup
directory. If they contain justgenesis.json
andrecords.json
, we assume we're running an old version of node setup, and if it looks like it contains a full NEAR home directory, we will assume it's prepared to be used withneard fork-network
. The only thing that changes formirror.py
is that agenesis_time
argument will be required in this case in order to get a consistent network fromneard fork-network set-validators
across all the nodes