roles
roles copied to clipboard
bisq-network
Bitcoin Node Operator
See https://github.com/bisq-network/bisq/blob/master/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java
2018.04 report
Running 2 instances both onion and clear net. No issues occurred that month.
2018.05 report
Running 2 instances both onion and clear net. No issues occurred that month.
2018.05 report
Running of 3 Bitcoin Fullnodes. 3 onion address 3 clearnet address 3 VPS servers and one dedicated server.
Events:
One SSD died (only the Bockchain was missing) and I had to sync the node again.
bisq-network/compensation#76
May 2018 report
Ran two full instances, both onion and clearnet with no issues.
Compensation request at https://github.com/bisq-network/compensation/issues/77
2018.05 report
Running one instance both onion and clear net. No issues occurred that month.
Events
The 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.
/cc bisq-network/compensation#71
2018.05 report
Running 2 instancens both onion and clear not. No issues this month.
bisq-network/compensation#80
Would any of the current @bisq-network/btcnode-operators be up for taking over the role of Bitcoin Node Maintainer (#66) from @ManfredKarrer?
This means the following:
- Take administrative ownership of the https://github.com/bisq-network/bisq-btcnode repository (which currently has no activity, but see below)
- Put together a common
bitcoin.confconfiguration file that all @bisq-network/btcnode-operators stay in sync with, and version control it in the aforementioned repository. This basically means figuring out what everyone is using right now for configuration, and normalizing that into what everyone should be using. - Staying on top of any issues that show up in the bisq-btcnode repository and being on point for any conversations / questions in the
#btcnodeSlack channel. - Doing monthly reports on the Bitcoin Node Maintainer role issue at #66.
I think this is quite low-hanging fruit with basically no extra ongoing work other than the quick report every month, and it would be a real value-add to get the common config file put together.
@cbeams @ManfredKarrer I feel I should take this one. My organizational skills are really not made for any kind of admin role but this one seems pretty manageable.
2018.06 report
- 2018-06-07 restarted tor service on 3r44ddzjitznyahw.onion as it was not reliably accepting tor connections, looks good after tor restart
End of month
No further issues running two nodes, i3a5xtzfm4xwtybd.onion and 3r44ddzjitznyahw.onion
2018.06 report
Running 2 instances both onion and clear net. No issues this month.
bisq-network/compensation#83
2018.06 report
Running one instance both onion and clear net. No issues occurred that month.
/cc https://github.com/bisq-network/compensation/issues/84
2018.06 report
Running of 3 Bitcoin Fullnodes.
- 3 onion address
- 3 clearnet address
- 3 VPS servers and one dedicated server.
Events:
none
bisq-network/compensation#88
2018.06 report
Running 2 instances both onion and clear net. No issues occurred that month.
/cc bisq-network/compensation#92
2018.07 report
Running 2 instances both onion and clear net. No issues occurred that month.
/cc bisq-network/compensation#93
2018.07 report
Run two instances with both clear net and onion. No issues to report.
2018.07 report
Running one instance both onion and clear net. Updated the system, switched to a cheaper plan on DigitalOcean and upgraded and built Bitcoin core from source for version 0.16.1.
/cc bisq-network/compensation#98
2018.07 report
Running of 3 Bitcoin Fullnodes.
3 onion address 3 clearnet address 3 VPS servers and one dedicated server.
Events:
none
/cc bisq-network/compensation#100
2018.07 report
Running 2 instances both onion and clear net. No issues this month.
bisq-network/compensation#105
2018.08 report
i3a5xtzfm4xwtybd.onion had a hard drive crash. After replacing the hard drive it also stopped spontaneously, seemingly due to a tor issue and had to be restarted.
End of month
No further issues after replacing hard drive. Connection count seems to hover around 250 - 300 per instance.
2018.08 report
Running one instance both onion and clear net.
/cc bisq-network/compensation#109
2018.08 report
Running of 3 Bitcoin Fullnodes.
3 onion address 3 clearnet address 3 VPS servers and one dedicated server.
Events:
none
/cc bisq-network/compensation#111
2018.08 report
Running 2 instances both onion and clear net.
/cc bisq-network/compensation#112
2018.08 report
Running 2 instances both onion and clear net. No issues this month.
bisq-network/compensation#116
2018.09 report
Running 2 instances both onion and clear net.
/cc bisq-network/compensation#125
2018.09 report
Running one instance both onion and clear net. Updated from source to version v0.16.3.
/cc bisq-network/compensation#126
2018.09 report
Running 2 instances, both onion and clear net. Upgraded to v0.16.3 due to bitcoind bug.
2018.09 report
Running of 3 Bitcoin Fullnodes.
3 onion address 3 clearnet address 3 VPS servers and one dedicated server.
Events:
none
/cc bisq-network/compensation#136
2018.09 report
Running 2 instances both onion and clear net. Upgraded from source to the 0.16.3 release due to security concerns.
bisq-network/compensation#141
2018.10 report
2018-10-23: Updated nodes i3a5xtzfm4xwtybd.onion, 3r44ddzjitznyahw.onion to version 0.17.0
2018.10 report
Running one instance both onion and clear net. Updated from source to version v0.17.0.
/cc bisq-network/compensation#148