Bitcoin Node Operator

[cbeams]

See https://github.com/bisq-network/bisq/blob/master/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java

[ManfredKarrer]

2018.04 report

Running 2 instances both onion and clear net. No issues occurred that month.

[ManfredKarrer]

2018.05 report

Running 2 instances both onion and clear net. No issues occurred that month.

[Emzy]

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

[sqrrm]

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

[ripcurlx]

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

[mrosseel]

2018.05 report

Running 2 instancens both onion and clear not. No issues this month.

bisq-network/compensation#80

[cbeams]

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.conf configuration 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 #btcnode Slack 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.

[sqrrm]

@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.

[sqrrm]

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

[mrosseel]

2018.06 report

Running 2 instances both onion and clear net. No issues this month.

bisq-network/compensation#83

[ripcurlx]

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

[Emzy]

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

[ManfredKarrer]

2018.06 report

Running 2 instances both onion and clear net. No issues occurred that month.

/cc bisq-network/compensation#92

[ManfredKarrer]

2018.07 report

Running 2 instances both onion and clear net. No issues occurred that month.

/cc bisq-network/compensation#93

[sqrrm]

2018.07 report

Run two instances with both clear net and onion. No issues to report.

[ripcurlx]

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

[Emzy]

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

[mrosseel]

2018.07 report

Running 2 instances both onion and clear net. No issues this month.

bisq-network/compensation#105

[sqrrm]

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.

[ripcurlx]

2018.08 report

Running one instance both onion and clear net.

/cc bisq-network/compensation#109

[Emzy]

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

[ManfredKarrer]

2018.08 report

Running 2 instances both onion and clear net.

/cc bisq-network/compensation#112

[mrosseel]

2018.08 report

Running 2 instances both onion and clear net. No issues this month.

bisq-network/compensation#116

[ManfredKarrer]

2018.09 report

Running 2 instances both onion and clear net.

/cc bisq-network/compensation#125

[ripcurlx]

2018.09 report

Running one instance both onion and clear net. Updated from source to version v0.16.3.

/cc bisq-network/compensation#126

[sqrrm]

2018.09 report

Running 2 instances, both onion and clear net. Upgraded to v0.16.3 due to bitcoind bug.

[Emzy]

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

[mrosseel]

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

[sqrrm]

2018.10 report

2018-10-23: Updated nodes i3a5xtzfm4xwtybd.onion, 3r44ddzjitznyahw.onion to version 0.17.0

[ripcurlx]

2018.10 report

Running one instance both onion and clear net. Updated from source to version v0.17.0.

/cc bisq-network/compensation#148

[ManfredKarrer]

2018.10 report

Running 2 instances both onion and clear net. Not updated yet to 0.17.

/cc bisq-network/compensation#155

[mrosseel]

2018.10 report

Running 2 instances both onion and clear net. Did not upgrade to 0.17, will probably leave at least one of the nodes at the old version to keep some diversity.

bisq-network/compensation#157

[Emzy]

2018.10 report

Running of 3 Bitcoin Fullnodes.

3 onion address 3 clearnet address 3 VPS servers and one dedicated server.

Events:

Upgrade bitcoin-core to v0.17

/cc bisq-network/compensation#163

[sqrrm]

2018.11 report

Running 2 instances, both onion and clear net

bisq-network/compensation#173

[Emzy]

2018.11 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#175

[ripcurlx]

2018.11 report

Running one instance both onion and clear net.

/cc bisq-network/compensation#177

[ManfredKarrer]

2018.11 report

Running 2 instances both onion and clear net.

/cc bisq-network/compensation#180

[mrosseel]

2018.11 report

Running 2 instances both onion and clear net.

bisq-network/compensation#181

[heyaco]

Sorry, noob here, but how does this exactly work? I have DNS off and need some trusted & reliable nodes Onion nodes to connect to so I can pull up the DNS.

[sqrrm]

Not sure exactly what you mean, but these are the bitcoin nodes that Bisq contributors run. They are accessible over tor using their respective onion address.

[heyaco]

I do not see the addresses listed anywhere.

[sqrrm]

Indeed, the link is broken, current code at https://github.com/bisq-network/bisq/blob/5a8731c8a5e9e18e256c9df71a0d22caccfb602f/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java#L47

[ManfredKarrer]

2018.11 report

Running 2 instances both onion and clear net.

/cc bisq-network/compensation#189

[sqrrm]

2018.12 report

Running 2 instances both onion and clear net.

https://github.com/bisq-network/compensation/issues/190

[Emzy]

2018.12 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#191

[ripcurlx]

2018.12 report

Running one instance both onion and clear net.

/cc bisq-network/compensation#195

[ManfredKarrer]

My nodes run out of available disk space. Increased from 250GB to 300 GB. Costs per node now 45 EUR.

UPDATE: Turned out that I have set txindex-1 which causes a larger block size. Seems total blocksize is still about 215 GB. I am resyncing my nodes as the volumme increase failed anyway. So my 2 nodes are not available for a while.

[ManfredKarrer]

2019.01 report

Running 2 instances both onion and clear net. Had some space issues as I have set the txindex enabled which requires more space. I removed that and re-synced the whole blockchain which took quite a bit of time. Reverted back to the 250GB disk and we should not run out of space over the next couple of months.

/cc bisq-network/compensation#205

[ripcurlx]

2019.01 report

Running one instance both on onion and clear net. Since this month I see more CPU load on the bitcoin core instance. Restart did help a little bit, but still I might update this month to the newest Bitcoin Core release. Also It seems like Tor stopped the support for my Ubuntu version (14 - trusty https://deb.torproject.org/torproject.org/dists/), so I might have to update my system as well.

/cc bisq-network/compensation#206

[Emzy]

2019.01 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#212