Calls split_nn_sapling.sh if low utxo count on NN #5
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.
I used FSM branch of komodo on the distant KMD node. I tested this script a little bit to split utxo for the 3P NN setup, it worked but I think that we should avoid to rely on only one explorer : if the explorer returns 0 utxo for the NN, we will split loads of utxo, it is not useful. A possible enhancement is to use several explorers (I'd like to avoid to importprivkey of the NN on the distant node).