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]

r3dsojfhwcm7x7p6 was moved to one of @Emzy clearnet nodes.

[Emzy]

r3dsojfhwcm7x7p6.onion is now running temporary on 62.75.210.81 as second hidden service.

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