-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitcoin Node Operator #67
Comments
And link to new issue for "Bitcoin Node Operator" role (#39 => #67) See bisq-network/dao#28
2018.04 reportRunning 2 instances both onion and clear net. No issues occurred that month. |
2018.05 reportRunning 2 instances both onion and clear net. No issues occurred that month. |
2018.05 reportRunning of 3 Bitcoin Fullnodes. Events:One SSD died (only the Bockchain was missing) and I had to sync the node again. |
May 2018 reportRan two full instances, both onion and clearnet with no issues. Compensation request at bisq-network/compensation#77 |
2018.05 reportRunning one instance both onion and clear net. No issues occurred that month. EventsThe instance wasn't reachable for a couple of hours as connection timeouts occurred. Instance was up and running and no obvious issue was causing this problem on DigitalOcean. After a restart everything was up and running again. |
2018.05 reportRunning 2 instancens both onion and clear not. No issues this month. |
Cycle 62- Running 3 btc nodes with no issues to report - Checked internal monitor 2x day to ensure proper operation - Checked each machine daily for updates and applied as needed |
Cycle 62 reportMy 3 nodes are still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the nodes. |
Cycle 62 reportRunning 3 instances, two of which are waiting to be merged in bisq-network/bisq#7231. |
Cycle 63Running 2 instances, |
Cycle 63- Running 3 btc nodes with no issues to report - Checked internal monitor 2x day to ensure proper operation - Checked each machine daily for updates and applied as needed |
Cycle 63 reportRunning 3 instances, now that bisq-network/bisq#7231 was merged. |
Cycle 63 reportMy 3 nodes are still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the nodes. |
Cycle 64Running 2 nodes. |
Cycle 64- Running 3 btc nodes with no issues to report - Checked internal monitor 2x day to ensure proper operation - Checked each machine daily for updates and applied as needed |
Cycle 64 reportMy 3 nodes are still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the nodes. |
Cycle 64 reportRunning 3 instances. |
Cycle 65Running 2 nodes |
Cycle 65- Running 3 btc nodes with no issues to report - Checked internal monitor 2x day to ensure proper operation - Checked each machine daily for updates and applied as needed |
Cycle 65 reportMy 3 nodes are still running, though will be decommissioned soon since they have been removed from the recent 1.9.18 release, as per bisq-network/bisq#7137. Once sufficient time has elapsed, I will decommission the nodes. |
Cycle 65 reportRunning 3 instances. |
See https://github.com/bisq-network/bisq/blob/master/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java
The text was updated successfully, but these errors were encountered: