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.
Currently running the autostake script will fail if the network is not included in networks.json or networks.local.json. Networks only present in Chain Registry had to be added to networks.local.json with empty config before the script would recognise them.
This PR instead assumes the network will be found in Chain Registry if the script is run with a network name, and will only fail if the network is not present in Chain Registry. E.g.
npm run autostake nois
will now lookupnois
in the Registry and work as expected.Running the script without a network (
npm run autostake
) will continue to run the script for all networks in networks.json AND networks.local.json. It will not run for every chain in Registry, as this will take a long time.Future updates will change this
npm run autostake
command without arguments to only run for chains in networks.local.json, since this is more adaptable, but for now it remains as-is.