Seednode Operator #15
Comments
2018.04 reportRunning 6 Bitcoin and 2 LTC instances. Digital ocean updates their servers frequently with security patches and that causes restarts which kills the seed node (no crone job for autostart). I am following the old email notifications and got alerted soon to start the seed node in such cases. |
2018.05 reportRunning 6 Bitcoin and 2 LTC instances. |
2018.05 reportRunning 1 Bitcoin instance. |
2018.05 reportRunning 1 Bitcoin instance |
2018.06 reportRunning 1 seednode instance
|
2018.06 reportRunning 1 Bitcoin instance
|
2018.06 reportRunning 6 seednode instance |
I've updated the description of this role issue and updated the @bisq-network/seednode-operators team to reflect current status. |
2018.07 reportRunning 6 seednode instance. |
Cycle 16 report
|
Cycle 17 reportRunning 5 instances, 2xV2 and 3xV3. |
Cycle 17 reportRunning 3 seednode instances |
Cycle 17 reportBoth seednodes running stable. |
Cycle 18 reportThere are 2 v2 seednodes: running stable |
Cycle 18 reportTemporary running 5 seednode instances |
Cycle 18 reportRunning 5 instances, 2xV2 and 3xV3. |
Cycle 19 reportRunning 3 instances. |
Cycle 19 reportTemporary running 5 seednode instances
|
Cycle 20 reportTemporary running 5 seednode instances
|
Cycle 20 reportRunning 3 instances. |
Cycle 21 reportTemporary running 4 seednode instances
|
Cycle 21 reportRunning 4 instances. |
This role is responsible for operating one or more Bisq seednodes.
See: btc_mainnet.seednodes
Docs: none, other than the above
Team: @bisq-network/seednode-operators
The text was updated successfully, but these errors were encountered: