Bitcoin Node Operator

[cbeams]

The idea here is that a number of Bisq contributors take on this role, run a full node and publicly attest that their full node will run the latest major version of Bitcoin Core. Doing this provides a service to Bisq users who want to ensure they're on the correct chain during contentious forks like that posed by the forthcoming SegWit2X project.

See https://lists.bisq.network/pipermail/bisq-contrib/2017-November/000006.html for further details and links.

operator	clearnet IP:port	clearnet name	onion address
@ManfredKarrer	159.89.16.222	btc1.0-2-1.net	r3dsojfhwcm7x7p6.onion
@ManfredKarrer	165.227.34.56	btc2.0-2-1.net	vlf5i3grro3wux24.onion
@ManfredKarrer	165.227.44.202	btc3.0-2-1.net	i3a5xtzfm4xwtybd.onion
@Emzy	78.47.61.83	kirsche.emzy.de	fz6nsij6jiyuwlsc.onion
@Emzy	62.75.210.81	node2.emzy.de	c6ac4jdfyeiakex2.onion:8333
@Emzy	163.172.171.119	node1.emzy.de	sjyzmwwu6diiit3r.onion:8333
@Emzy	n/a	n/a	poyvpdt762gllauu.onion:8333
@ripcurlx	174.138.35.229:8333	btc.christophatteneder.com	lgkvbvro67jomosw.onion
@mrosseel	138.68.117.247:8333	btc.vante.me	4jyh6llqj264oggs.onion
@mrosseel	67.207.75.7	btc2.vante.me	mxdtrjhe2yfsx3pg.onion
@sqrrm	185.25.48.184	btc4.0-2-1.net	3r44ddzjitznyahw.onion:8333
@sgeisler	5.189.166.193:8333	bcwat.ch	z33nukt7ngik3cpe.onion
@jhoenicke	88.198.39.205:8333	btc.jochen-hoenicke.de	sslnjjhnmwllysv4.onion:8333
@tbocek	192.41.136.217:8333	bitcoin4-fullnode.csg.uzh.ch	n/a

[ManfredKarrer]

See also https://docs.google.com/document/d/1Fgxfrcpx1RNm36-YjqM5dLw3wXETsneEF2CKdXwJJ5Q/edit#heading=h.1rb4hptmf06h for more details.

[cbeams]

I've just assigned myself to this role. As I also just tweeted, I'm running a Bitcoin fullnode at btc.beams.io:8333. It's running Bitcoin Core 0.15.0.1 and I'll keep it up to date over time.

[cbeams]

Please add a comment similar to mine if you're a Bisq contributor willing to run a Bitcoin fullnode and keep it up to date over time. I'll add you as an assignee.

Note that this is a bonded role, so only BSQ stakeholders should apply. We'll figure out the exact bonding level later, but it'll probably be at least 1,000 BSQ.

[Emzy]

Please assign me to this role. I'm running a Bitcoin fullnode at kirsche.emzy.de:8333
It's running Bitcoin Core 0.15 and I'll keep it up to date over time.
FYI 0.15.0.1 is a GUI fix so I haven't installed it on the headless node.

[cbeams]

Done, thanks @Emzy.

[mrosseel]

Also up for this, not yet running a node atm though.

[cbeams]

Thanks @mrosseel, just post a comment here when it's up and running and I'll assign you.

[ManfredKarrer]

@cbeams @Emzy Please add your IP as well as a hostname requires DNS lookup which can be avoided here.

[cbeams]

I've added a list to the description with hostname, port and IP address. I'll update the list as folks comment here.

[Emzy]

kirsche.emzy.de (78.47.61.83)

[cbeams]

@ManfredKarrer, note that it might be good to rely on DNS lookups at first; we may want / need to move these nodes around physically over the next few months until roles etc are settled.

…

On Nov 7, 2017, at 6:03 PM, Stephan Oeste ***@***.***> wrote: kirsche.oeste.de (78.47.61.83) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[ManfredKarrer]

@cbeams Ok, good point.

[ManfredKarrer]

The DNS lookup (over Tor) takes about 600 ms on my bad internet connection (might be faster for others). So for that reason I would prefer to use the IP instead the hostname. There might be room for improvements for the DNS lookup as well...

[cbeams]

How often does that lookup happen? In any case, please do as you see fit; just wanted to put the idea out there.

…

On Nov 7, 2017, at 7:16 PM, Manfred Karrer ***@***.***> wrote: The DNS lookup (over Tor) takes about 600 ms on my bad internet connection (might be faster for others). So for that reason I would prefer to use the IP instead the hostname. There might be room for improvements for the DNS lookup as well... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[ripcurlx]

Here we go: 174.138.35.229 - a nice subdomain for the ip is coming soon :-)
My very creative subdomains: bitcoin.christophatteneder.com or btc.christophatteneder.com
Both would work...

[ManfredKarrer]

@cbeams At startup once. But it is a blocking call atm so would try to avoid it.

[alexej996]

Clearnet node: spidernet.tk:8333 (it has a dynamic IP unfortunately so it needs to use DNS to get it)
Tor node: vlf5i3grro3wux24.onion:8333

PS: The clearnet node has a onion address as well if you need.

[cbeams]

Great @alexej996, thanks!

[ManfredKarrer]

@alexej996 Yes if you can provide the onion of the spidernet.tk:8333 node would be better. We are short on onion nodes...

[alexej996]

The onion address for the clearnet node is r3dsojfhwcm7x7p6.onion

[ManfredKarrer]

@alexej996 Perfect! I will use only the 2 onion addresses.

[cbeams]

Cool, table has been updated (and now it's a proper table)

[ManfredKarrer]

FYI:
https://twitter.com/MrHodl/status/927916865183240193
https://people.xiph.org/~greg/banlist.cli.txt

[Emzy]

Bitcoin node with onion address: poyvpdt762gllauu.onion:8333
This node has no clearnet address.

[ripcurlx]

@cbeams My clearnet name is: btc.christophatteneder.com:8333

[sqrrm]

I've got and onion only 0.15.0 node on 3r44ddzjitznyahw.onion:8333

Do we require upgrades to latest minor release? Upgrading requires some downtime that I'd rather avoid.

[jhoenicke]

I upgraded to a more powerful server, hopefully with fewer timeouts. Can you change the ip from 37.221.198.57 to 88.198.39.205?

[ManfredKarrer]

Thanks for the update. The 37.221.198.57 server is not used then anymore I assume. The nodes are hard coded so the change will be only in the next update. I will change also that the domain name will be used instead of the IP (costs extra DNS lookup via Tor but is more flexible for such cases).

[jhoenicke]

The old server is still running, but that may change in the future. So it is not a problem, if the change isn't immediate.

[ManfredKarrer]

Ah cool. We will have soon an update anyway and our users are usually fast with updating. Just changed that we use the domain instead the IP if both are available.

[sgeisler]

I added a tor hidden service to my bcwat.ch node: z33nukt7ngik3cpe.onion:8333

[ManfredKarrer]

@sgeisler Ah great thanks!

[ManfredKarrer]

@tbocek @jhoenicke : Co you have your nodes also reachable as onion nodes?

[ripcurlx]

My node with hidden service: lgkvbvro67jomosw.onion:8333

[Emzy]

New hostnames for my nodes:
node1.emzy.de has address 163.172.171.119
node2.emzy.de has address 62.75.210.81

[mrosseel]

• 138.68.117.247 now has an onion address as well: 4jyh6llqj264oggs.onion
• mxdtrjhe2yfsx3pg.onion now has a clearnet IP as well: 67.207.75.7

[ManfredKarrer]

@mrosseel Can you set a domain name as well. Gives more flexibility in case of moving the host.

[ManfredKarrer]

@Emzy Can you setup tor for 78.47.61.83 and provide a domainname + IP for poyvpdt762gllauu.onion?

[ManfredKarrer]

@jhoenicke @tbocek : Do you have tor enabled for incoming connections? If so can you provide the onion address?

[ManfredKarrer]

@jhoenicke, @tbocek, @sgeisler :
Do you have the maxconnections set to default (125) or do you have set it higher?
500 seems to be good but of course cause more traffic.
We saw that the nodes are not getting filled up (and then rejecting new connections) if that limit is > 400.

Also the timeout for btc nodes is default 5 sec. which seems for Tor connections too low. We increase that now to 30 sec. Do you see any concerns by changing that?

I use those settings in bitcoin.conf:
maxconnections=500
timeout=30000

I use Tor only for incoming connections, so no setup on the btc side just edited the torrc files. That way the btc node has no risk to get partitioned from the rest of the btc network as it get mixed incoming connections and connects itself via clearnet to other btc nodes.

We will change the behavior also that we will connect to onion nodes only if the user has Tor enabled for BitcoinJ. That prevents privacy and performance issues with Tor exit nodes if Bisq nodes would connect to clearnet btc nodes over Tor.
Do you see any concerns by sticking to Tor btc nodes only (as mentioned above there should be no risk for btc network partitioning issues).

[Emzy]

My node kirsche.emzy.de has now a onion address:
78.47.61.83:8333 | kirsche.emzy.de | fz6nsij6jiyuwlsc.onion:8333

[cbeams]

Closing as superseded by #67, primarily because this issue has gotten so long and is in many ways now out of date. See also the new "Bitcoin Node Maintainer" role at #66.

The distinction between Maintainer and Operator here is important. Going forward, the Bitcoin Node Maintainer (currently @ManfredKarrer) will be responsible for updating shared bitcoin.conf config files and ensuring that all operators in the federation are aware of and up to date with changes to it. This way we should have clear lines of responsibility about ensuring that config changes get propagated across the federation in a consistent and timely way.

[heyaco]

Is this list still being maintained? I am looking for some trusted & reliable Tor fallback nodes for bitcoin.

[sqrrm]

See #67 for current nodes maintained by Bisq contributors.