multiple bots about validator-registry HOT 9 CLOSED

ah I forgot about the single part, thank you

from validator-registry.

Sorry not sure I follow - the time you run restake is purely down to when you run your script. The information in this repo/previously in restake was just to show delegators what time you plan to run it.

from validator-registry.

I ran the bot manually and it restocked for osmosis and Umee but was only meant to run for the cosmos hub. How do I make it only run for the hub?

from validator-registry.

do I remove all networks in network.json, other than cosmos hub?

from validator-registry.

You can run a single network with ... run autostake cosmoshub. The setup for running multiple networks at different times would look something like this:

0 21 * * * /bin/bash -c "cd restake && docker-compose run --rm app npm run autostake osmosis" > ./restake.osmosis.log 2>&1
0 * * * * /bin/bash -c "cd restake && docker-compose run --rm app npm run autostake cerberus" > ./restake.cerberus.log 2>&1
0 9,21 * * * /bin/bash -c "cd restake && docker-compose run --rm app npm run autostake cosmoshub" > ./restake.cosmoshub.log 2>&1

It's important to understand the the autostake script runs the autostake at that time, it doesn't take into account when you said you'll run it. It's up to you to run it at the right time for each network.

from validator-registry.

You shouldn't need to change networks.json at all now. networks.local.json is useful for setting your own node, or adjusting some of the autostaking parameters for each network such as batch size. More in the restake README on that.

from validator-registry.

You can run a single network with ... run autostake cosmoshub

It would be interesting to be able to specify more networks as parameters like:
... run autostake cosmoshub osmosis akash osmosis

This way they will be queued and not run parallel, but only those indicated (even if all configured)
In certain complex infrastructures this would help

from validator-registry.

Funny you should mention, that was added last night!

from validator-registry.

Funny you should mention, that was added last night!

Oh, wow! well done :)

from validator-registry.