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 notifications@github.com 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 notifications@github.com 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.

[ManfredKarrer]

Thanks! No upgrade needed, latest patch was UI only changes. Also good to have a bit diversity with versions.

[ManfredKarrer]

I sent out invitations to 10 other devs for providing their BTC nodes. No answer so far ;-(. If we don't get enough nodes added by them I would ask you (@cbeams, @ripcurlx, @mrosseel, @sqrrm) to run a second one if possible. Would be good to have about 50% onion nodes. If I find time I will also setup some but super buys with getting the release ready....

[tbocek]

Here is a full BTC node I'm operating: bitcoin4-fullnode.csg.uzh.ch, it has a fixed IP.

[cbeams]

Thanks, @tbocek. I've added your node to the table above, and I've sent you an invite to join the @bisq-network GitHub org, such that I can assign you to this issue.

[tbocek]

SegWit2x may not happen after all: https://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/2017-November/000685.html

[ManfredKarrer]

Yes that is great news! So the urgent threat is gone. We will still keep that feature as it avoids the privacy problems with bloom filters and because we are protected in future if such attacks repeat. We did not see such the first time (XT, Unlimted, Classic, BCH). Better to be prepared in advance. I think it is also a good resource for people who want to pick nodes from people with good reputation to connect to.

[sgeisler]

I have already sent a mail to @ManfredKarrer, you can include bcwat.ch in your list (5.189.166.193:8333).

[cbeams]

Thanks, @sgeisler. Like with with @tbocek, I've just sent you an invitation to join the @bisq-network GitHub org, so we can assign you to this issue.

[cbeams]

Note that I've updated the description of this issue to indicate that our nodes should run the latest major version of Bitcoin Core (where major version means, say, 0.14. vs 0.15.). Some diversity in minor versions is probably a good thing, and we can in most cases probably be a bit relaxed about upgrading to the very latest minor releases.

[sgeisler]

@cbeams I've started a core 0.15.0.1 node on bcwat.ch (running on port 8333). The old btcd is still running on port 8334.

[cbeams]

Roger that, @sgeisler. Did you get the invitation to join the GitHub org?

[sgeisler]

@cbeams yes, couldn't find it at first ;) (somehow it was only shown on the project's page and not in my notifications)

[mrosseel]

On slack there's a new channel called #fullnode where we can discuss installation, running and upgrades of our full nodes. Could not find slack users for @sgeisler and @tbocek => if you want please join slack via this link: https://bisq.network/slack-invite

[jhoenicke]

My node's (btc.jochen-hoenicke.de) ip is: 37.221.198.57:8333 ; ipv-6: [2a03:4000:9:8e::1]:8333

[mrosseel]

clearnet node IP: 138.68.117.247 clearnet name: btc.vante.me tor node: mxdtrjhe2yfsx3pg.onion

Note: the clearnet node and tor node are hosted on 2 separate machines

[sqrrm]

Added a new node: clearnet: 80.233.134.60:8333 no name: tor: i3a5xtzfm4xwtybd.onion:8333

[cbeams]

@sqrrm, I've added the node details above, and the table now reflects that you're running two nodes. Thanks.

[cbeams]

I've also updated the table to strike out my node for the time being. I'm in the process of upgrading the target machine and may not be able to have the node up and running reliably by the time 0.6.0 is out. I'll update the table and add another comment when I do get the node up permanently.

[themighty1]

Hi, dansmith here. Running my always-on node on 7sl6havdhtgefwo2.onion

[ManfredKarrer]

@themighty1 Thanks! We are getting more onion nodes than clear net nodes. Great!

[ripcurlx]

@tbocek & @jhoenicke: Hi Thomas & Jochen! Could you join us on Slack (https://bisq.network/slack-invite) in the #monitoring channel as well? @mrosseel has set up some basic monitoring of the full nodes and has problems connecting to your nodes now and then. Would be great to check if the error messages are false positives at the moment or if there is a real problem. Thanks! :-)

[ManfredKarrer]

@themighty1 Your node is not available. Could you have a look to it?

[Emzy]

Two new Bitcoin nodes from me: 62.75.210.81 c6ac4jdfyeiakex2.onion 163.172.171.119 sjyzmwwu6diiit3r.onion

[sqrrm]

I have moved 3r44ddzjitznyahw.onion and it now also has a clearnet address: 185.25.48.184 3r44ddzjitznyahw.onion