--- Log opened Mon Jun 14 00:00:37 2021 01:29 -!- belcher_ is now known as belcher 02:05 -!- greypw [~greypw@grey.pw] has joined #bitcoin-core-pr-reviews 02:10 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has joined #bitcoin-core-pr-reviews 02:58 -!- djinni` [~djinni@static.38.6.217.95.clients.your-server.de] has quit [Quit: Leaving] 03:06 -!- djinni` [~djinni@static.38.6.217.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 05:07 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews 05:07 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection] 05:17 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has quit [Read error: Connection reset by peer] 05:18 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 05:19 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has quit [Read error: Connection reset by peer] 05:20 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 05:25 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has quit [Read error: Connection reset by peer] 05:26 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 05:36 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has quit [Read error: Connection reset by peer] 05:37 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 05:41 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has quit [Read error: Connection reset by peer] 05:41 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 06:59 -!- prusnak[m] [~stickmatr@2001:470:69fc:105::98c] has quit [Read error: Connection reset by peer] 07:00 -!- prusnak[m] [~stickmatr@2001:470:69fc:105::98c] has joined #bitcoin-core-pr-reviews 07:21 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has quit [Read error: Connection reset by peer] 07:22 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 07:28 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has quit [Read error: Connection reset by peer] 07:30 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 08:16 -!- ivan1 [~ivan@189.172.223.227] has joined #bitcoin-core-pr-reviews 09:06 -!- user__ [~davterra@178.128.106.205] has joined #bitcoin-core-pr-reviews 09:08 -!- davterra [~davterra@178.128.106.205] has quit [Ping timeout: 268 seconds] 09:09 -!- user__ is now known as davterra 10:08 -!- jonatack [jonatack@user/jonatack] has quit [Quit: Connection closed] 10:27 -!- jonatack [jonatack@user/jonatack] has joined #bitcoin-core-pr-reviews 10:27 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection] 10:27 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #bitcoin-core-pr-reviews 10:29 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-pr-reviews 10:41 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #bitcoin-core-pr-reviews 10:41 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection] 10:46 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 252 seconds] 10:58 < pinheadmz_> can bitcoind listen on both ipv4 and ipv6? I know it can make outbound connections on both (+onion and i2p) but can it also advertise multiple public hosts if available? 11:07 < sipa> yes 11:07 < sipa> you can specify externalip multiple times 11:07 < pinheadmz_> ahh, dope tnx 11:31 < michaelfolkson> https://bitcoin.stackexchange.com/questions/107025/can-bitcoind-listen-on-both-ipv4-and-ipv6 11:34 < sipa> i gyess i only answered your last question 11:34 < pinheadmz_> dang michaelfolkson yer fast 11:36 < sipa> by default bitcoind will bind on INADDRV6_ANY (::0) 11:36 < sipa> which means it can accept connections arriving on your host both as ipv4 or ipv6 11:36 < michaelfolkson> Ooh interesting, thanks :) Will add 11:37 < sipa> michaelfolkson: i would really appreciiate it if you don't just copy paste my answers here on stackexchange 11:37 < sipa> context and conversation gets lost 11:38 < michaelfolkson> :( I find it really useful though 11:38 < michaelfolkson> But if that's what you wish I'll stop doing it 11:40 < sipa> for example, in this i wasn't even done answering really, i only commented on the last part (advetizing multiple hosts) 11:40 < michaelfolkson> Ask permission each time or just don't do it at all? 11:40 < sipa> answer whennyoh know tje answer 11:40 < sipa> answer when you know the answer, and can explain it 11:41 < sipa> not just copy-paste something 11:41 < michaelfolkson> Ok that leaves a question without an answer and often you'll be the one answering it on StackExchange anyway :) 11:41 < michaelfolkson> But ok, will do in future 11:44 < sipa> pinheadmz_: so we listen on ipv6, but as the ipv4 address space is embedded in ipv6, that means you can also accept ipv4 connections that way (they'll look like they come from the ipv4-embedded in-ipv6 address) 11:45 < sipa> pinheadmz_: so that happens automatically unless you use -nolisten or specifically set a bind address with -bind 11:45 < pinheadmz_> that makes sense for ::0 but on digital ocean for example Ill have different IPs for v4 and v6, so adding extra -extrernalip makes sense, and is cool 11:45 < sipa> advertizing addresses is actually completely independent from listening on them 11:46 < pinheadmz_> sure i get that 11:46 < pinheadmz_> the second part of my question is what i really wanted to know 11:46 < sipa> ok 11:46 < pinheadmz_> and they are both gossiped in addr messages, always encoded as ipv6 (or ipv4-embedded-in-ipv6) ? 11:47 < sipa> pre-BIP155 addr rumouring used a flat ipv6 namespace, with ipv4 and tor v2 addresses embedded in subranges of that space 11:47 < pinheadmz_> oh right i forgot the addr messages are bigger now for onionv3 11:48 < sipa> since BIP155 with addrv2 every address has an explicit network identifier 11:48 < pinheadmz_> ok cool 11:48 < sipa> and socin addrv2, iov4 addresses are just sent as 4-byte ipv4 addresses with the ipv4 marker 11:49 < sipa> yeah, tor v3 addresses are 16 bytes 11:50 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has quit [Quit: Connection closed for inactivity] 11:51 -!- Talkless [~Talkless@mail.dargis.net] has quit [Read error: Connection reset by peer] 11:52 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-pr-reviews 12:07 -!- keyan [~keyan@2603-8080-1205-e353-fde3-0741-ba38-00c4.res6.spectrum.com] has joined #bitcoin-core-pr-reviews 12:10 -!- keyan [~keyan@2603-8080-1205-e353-fde3-0741-ba38-00c4.res6.spectrum.com] has quit [Client Quit] 12:11 < jonatack> pinheadmz_: (maybe) complementary info, have a look at the -externalip documentation (both paragraphs) in doc/tor.md 12:13 < jonatack> come to think of it, the -externalip help in src/init.cpp could maybe use some more info 12:13 < pinheadmz_> jonatack thanks yeah I usually grep `bitcoind -h` a lot too but those defs are usually very simple 12:14 < jonatack> (putting it on my to-do list for after feature freeze) 12:14 < pinheadmz_> tor.md has nice long explanations of those options 12:15 < pinheadmz_> whats the best place to see everything that could go in a bitcoin.conf file? it bitcoind -h the most complete? 12:15 -!- pinheadmz_ is now known as pinheadmz 12:16 < jonatack> yes, i added info in doc/tor.md (often after a "TIL moment" seeing sipa discuss it on IRC), and in some places like -externalip the help could use catching up 12:18 < jonatack> yes bitcoind -h, or for us, "use the source luke" 12:18 < jonatack> er, read the source 12:18 < pinheadmz> lol yes the source is strong with me 12:34 < sipa> jonatack: i forget which but there was once some command line tool that had a --use-the-force-luke instead of --force 12:36 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!] 14:50 -!- robertspigler [~robertspi@2001:470:69fc:105::2d53] has joined #bitcoin-core-pr-reviews 17:50 -!- l3kk0 [~l3kk0@c-73-22-213-40.hsd1.il.comcast.net] has joined #bitcoin-core-pr-reviews 19:54 -!- davterra [~davterra@178.128.106.205] has quit [Quit: Leaving] 20:06 < _aj_> sipa: growisofs apparently 20:18 < sipa> ibdeed! that was it! 20:26 -!- ivan2 [~ivan@2806:10b7:2:b296:7145:7444:8d24:fb7d] has joined #bitcoin-core-pr-reviews 20:28 -!- ivan1 [~ivan@189.172.223.227] has quit [Ping timeout: 244 seconds] 21:34 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-core-pr-reviews 21:37 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 252 seconds] 22:48 -!- belcher_ [~belcher@user/belcher] has quit [Quit: Leaving] 23:56 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has joined #bitcoin-core-pr-reviews --- Log closed Tue Jun 15 00:00:38 2021