12019-06-22T00:00:01  *** k0da has quit IRC
  22019-06-22T00:03:48  *** Gunni1 has joined #bitcoin-core-dev
  32019-06-22T00:05:49  *** qwebirc303118 has quit IRC
  42019-06-22T00:07:19  *** scoop has quit IRC
  52019-06-22T00:33:01  *** bralyclow has quit IRC
  62019-06-22T00:33:49  *** bralyclow has joined #bitcoin-core-dev
  72019-06-22T00:38:37  *** bralyclow has quit IRC
  82019-06-22T00:44:47  *** hugohn has joined #bitcoin-core-dev
  92019-06-22T00:50:57  *** DeanGuss has joined #bitcoin-core-dev
 102019-06-22T00:51:34  *** owowo has quit IRC
 112019-06-22T00:56:08  *** owowo has joined #bitcoin-core-dev
 122019-06-22T00:56:09  *** owowo has joined #bitcoin-core-dev
 132019-06-22T00:57:18  *** pinheadmz has quit IRC
 142019-06-22T01:05:48  *** hugohn has quit IRC
 152019-06-22T01:10:14  *** bralyclow has joined #bitcoin-core-dev
 162019-06-22T01:33:03  *** pinheadmz has joined #bitcoin-core-dev
 172019-06-22T01:36:07  *** aseem has joined #bitcoin-core-dev
 182019-06-22T01:42:32  *** Chris_Stewart_5 has joined #bitcoin-core-dev
 192019-06-22T01:43:59  *** bralyclow has quit IRC
 202019-06-22T01:52:34  *** bralyclow has joined #bitcoin-core-dev
 212019-06-22T01:52:36  *** rafalcpp_ has joined #bitcoin-core-dev
 222019-06-22T01:52:58  *** queip has quit IRC
 232019-06-22T01:52:58  *** rafalcpp has quit IRC
 242019-06-22T01:57:02  *** pinheadmz has quit IRC
 252019-06-22T01:57:43  *** Chris_Stewart_5 has quit IRC
 262019-06-22T01:58:24  *** rafalcpp has joined #bitcoin-core-dev
 272019-06-22T01:58:47  *** rafalcpp_ has quit IRC
 282019-06-22T02:01:44  *** queip has joined #bitcoin-core-dev
 292019-06-22T02:07:48  *** scoop has joined #bitcoin-core-dev
 302019-06-22T02:12:16  *** scoop has quit IRC
 312019-06-22T02:21:40  *** ddustin has quit IRC
 322019-06-22T02:22:17  *** ddustin has joined #bitcoin-core-dev
 332019-06-22T02:27:02  *** ddustin has quit IRC
 342019-06-22T02:32:57  *** hugohn has joined #bitcoin-core-dev
 352019-06-22T02:34:11  *** pinheadmz has joined #bitcoin-core-dev
 362019-06-22T02:35:37  *** aseem has quit IRC
 372019-06-22T02:36:21  *** ddustin has joined #bitcoin-core-dev
 382019-06-22T02:36:28  *** aseem has joined #bitcoin-core-dev
 392019-06-22T02:37:45  *** hugohn has quit IRC
 402019-06-22T02:38:47  *** ddustin has quit IRC
 412019-06-22T02:48:16  *** aseem has quit IRC
 422019-06-22T03:00:01  *** Gunni1 has quit IRC
 432019-06-22T03:04:32  *** pinheadmz has quit IRC
 442019-06-22T03:07:05  *** DeanGuss has quit IRC
 452019-06-22T03:18:41  *** ddustin has joined #bitcoin-core-dev
 462019-06-22T03:18:51  *** survivor has joined #bitcoin-core-dev
 472019-06-22T03:31:48  *** jtimon has quit IRC
 482019-06-22T03:36:58  *** ddustin has quit IRC
 492019-06-22T03:44:43  *** profmac has quit IRC
 502019-06-22T03:53:16  *** dviola has quit IRC
 512019-06-22T03:58:18  *** profmac has joined #bitcoin-core-dev
 522019-06-22T04:03:21  *** dongcarl has quit IRC
 532019-06-22T04:03:44  *** Isthmus has quit IRC
 542019-06-22T04:04:14  *** Isthmus has joined #bitcoin-core-dev
 552019-06-22T04:06:10  *** dongcarl has joined #bitcoin-core-dev
 562019-06-22T04:43:11  *** d_t has quit IRC
 572019-06-22T04:51:10  *** surja795 has joined #bitcoin-core-dev
 582019-06-22T04:56:00  *** surja795 has quit IRC
 592019-06-22T05:20:00  *** infinitis has joined #bitcoin-core-dev
 602019-06-22T05:22:06  *** hebasto has joined #bitcoin-core-dev
 612019-06-22T05:31:36  *** surja795 has joined #bitcoin-core-dev
 622019-06-22T05:33:29  *** bralyclow has quit IRC
 632019-06-22T05:34:06  *** bralyclow has joined #bitcoin-core-dev
 642019-06-22T05:37:05  *** surja795 has quit IRC
 652019-06-22T05:38:56  *** spinza has quit IRC
 662019-06-22T05:39:12  *** bralyclow has quit IRC
 672019-06-22T05:51:18  *** teardown has quit IRC
 682019-06-22T06:00:01  *** survivor has quit IRC
 692019-06-22T06:00:48  *** bralyclow has joined #bitcoin-core-dev
 702019-06-22T06:09:35  *** scoop has joined #bitcoin-core-dev
 712019-06-22T06:12:55  *** oneark has joined #bitcoin-core-dev
 722019-06-22T06:14:13  *** rafalcpp_ has joined #bitcoin-core-dev
 732019-06-22T06:14:38  *** queip has quit IRC
 742019-06-22T06:14:38  *** rafalcpp has quit IRC
 752019-06-22T06:15:10  *** ddrm has joined #bitcoin-core-dev
 762019-06-22T06:20:27  *** queip has joined #bitcoin-core-dev
 772019-06-22T06:34:48  *** phyll1s_work has joined #bitcoin-core-dev
 782019-06-22T06:53:11  <kallewoof> sipa: I may be slow, but I thought the coinbase transaction contained the witness commitment, so simply getting the hash of everything (including coinbase) should commit to witness commitment as well.
 792019-06-22T06:54:37  <sipa> kallewoof: yup, it does!
 802019-06-22T06:54:52  <sipa> you're right
 812019-06-22T06:55:14  <kallewoof> sipa: OK, then I should be fine without GetWitnessHash, as the witness data is already committed to then, right?
 822019-06-22T06:55:23  <sipa> yeah
 832019-06-22T06:55:43  * sipa zZzZ
 842019-06-22T06:55:48  <jb55> lol
 852019-06-22T06:56:01  *** teardown has joined #bitcoin-core-dev
 862019-06-22T06:56:28  <kallewoof> Thanks :) G'night!
 872019-06-22T06:57:15  *** scoop has quit IRC
 882019-06-22T07:03:10  *** d_t has joined #bitcoin-core-dev
 892019-06-22T07:05:30  *** d_t has quit IRC
 902019-06-22T07:25:15  *** surja795 has joined #bitcoin-core-dev
 912019-06-22T07:30:02  *** surja795 has quit IRC
 922019-06-22T07:30:39  *** ddrm has quit IRC
 932019-06-22T07:39:14  *** infinitis has quit IRC
 942019-06-22T07:39:46  *** Guyver2 has joined #bitcoin-core-dev
 952019-06-22T07:42:50  <kallewoof> Matthew Haywood suggested that a UTXO for an address that was previously spent from should be called "associate". It is currently referred to as a "used" or "reused" address/output/balance. Associate balance. Associate output. I kind of like that.
 962019-06-22T07:44:05  <sipa> i would suggested tainted, but that word has another meaning alreadg
 972019-06-22T07:45:27  <sipa> not sure i like associate
 982019-06-22T07:45:44  <sipa> it doesn't really convey badness
 992019-06-22T07:45:50  <sipa> "exposed" ?
1002019-06-22T07:46:08  * sipa bad at sleeping
1012019-06-22T07:46:19  *** cluelessperson has joined #bitcoin-core-dev
1022019-06-22T07:59:14  *** rafalcpp has joined #bitcoin-core-dev
1032019-06-22T07:59:16  <luke-jr> kallewoof: addresses are never spent from
1042019-06-22T07:59:45  <kallewoof> Exposed is nice, too.
1052019-06-22T07:59:53  *** tripleslash has quit IRC
1062019-06-22T08:00:01  *** rafalcpp_ has quit IRC
1072019-06-22T08:00:05  <kallewoof> luke-jr: I am bad at formulating this stuff, but you understand what I am saying.
1082019-06-22T08:00:08  *** queip has quit IRC
1092019-06-22T08:00:13  *** scoop has joined #bitcoin-core-dev
1102019-06-22T08:00:41  <luke-jr> kallewoof: I think the new paradigm you are introducing is harmful.
1112019-06-22T08:01:46  <kallewoof> luke-jr: Mind explaining?
1122019-06-22T08:02:23  <luke-jr> kallewoof: addresses have nothing to do with when the UTXOs get spent later
1132019-06-22T08:02:48  <luke-jr> kallewoof: your new stuff is creating such a link, give credence to the "from address" myth
1142019-06-22T08:03:18  <luke-jr> and not really solving more than a very narrow subset of the problems of address reuse
1152019-06-22T08:03:40  <kallewoof> luke-jr: that is not my intention. I am trying to address a specific privacy issue where someone can map your UTXO set.
1162019-06-22T08:04:34  <luke-jr> it's because it's too specific/special-cased
1172019-06-22T08:05:03  <luke-jr> seeking to have a term like "associate" above demonstrates the problem with it IMO
1182019-06-22T08:05:05  *** scoop has quit IRC
1192019-06-22T08:05:26  <luke-jr> no such term should exist, because it's not a real relationship
1202019-06-22T08:05:43  *** sfhi has joined #bitcoin-core-dev
1212019-06-22T08:06:02  *** queip has joined #bitcoin-core-dev
1222019-06-22T08:07:23  <kallewoof> I am a bit confused, to be honest. If I ask you for an address to send you a payment for some service, I then know that this address is with very high accuracy belonging to luke-jr. If you spend from it, I know with reasonable accuracy that you own at least one of the outputs unless you have no change output. If I then send to that address and you use it again with other inputs, I know those inputs are luke-jr.
1232019-06-22T08:07:56  <luke-jr> kallewoof: you don't spend from an address, and spending the UTXO is not necessarily the same person you sent to
1242019-06-22T08:09:09  <luke-jr> https://en.bitcoin.it/wiki/From_address
1252019-06-22T08:10:03  <luke-jr> sending a transaction with 1 output pays 1 address and creates 1 UTXO, but the address and UTXO are not inherently related
1262019-06-22T08:10:10  <kallewoof> I am a bit confused, to be honest. If I ask you for an address to send you a payment for some service, I then know that the UTXO resulting in me sending money to this address is with very high accuracy belonging to luke-jr. If you spend this UTXO, I know with reasonable accuracy that you own all the inputs unless it's a coinjoin or something. If I then create another UTXO by sending to that address and you use this UTXO
1272019-06-22T08:10:11  <kallewoof> with other inputs, I know those inputs are luke-jr as well.
1282019-06-22T08:10:36  <kallewoof> Yes, but the normal case is that a UTXO belonging to you does not suddenly change ownership.
1292019-06-22T08:11:37  <luke-jr> the address represents the recipient and purpose of the payment; the UTXO controls the actual funds, and may very well be part of a shared wallet
1302019-06-22T08:12:17  <luke-jr> there is no assumption of a normal case
1312019-06-22T08:13:10  <luke-jr> (and shared wallets are fairly normal too anyway)
1322019-06-22T08:14:35  <luke-jr> (shared wallets are also a best practice in custodial situations)
1332019-06-22T08:19:07  <kallewoof> luke-jr: I would love to fix this, but I'm not sure what good phrasing would be. Would you be up for making a PR?
1342019-06-22T08:19:51  <luke-jr> kallewoof: I don't know what you mean. The problem is the behaviour, not phrasing.
1352019-06-22T08:20:17  <luke-jr> (well, maybe phrasing is also an issue, dunno - but it's not the main issue)
1362019-06-22T08:20:47  <kallewoof> luke-jr: Why did you not concept NACK either of the PRs? There were two of them. This has been going on for 2 years..
1372019-06-22T08:21:13  <kallewoof> luke-jr: I may not agree with you but at least we could have discussed the direction before it was merged.
1382019-06-22T08:21:20  <luke-jr> I thought I did and got ignored
1392019-06-22T08:21:46  <kallewoof> luke-jr: you said "it does not fully address the problem with address reuse". That's not a concept NACK on the code itself, it's saying "this is not enough".
1402019-06-22T08:21:56  <luke-jr> "an address that has been used before, and the UTXOs received at the same time have been spent" should neither have a term nor affect behaviour
1412019-06-22T08:21:57  <kallewoof> which I interpreted as "we need to do more beyond this" (but it's a start)
1422019-06-22T08:23:23  <kallewoof> luke-jr: Should wallets avoid spending UTXO:s that are associated with a pubkey that is known to have been spent by the wallet itself?
1432019-06-22T08:23:43  <kallewoof> luke-jr: Should wallets distinguish between these, and other UTXO:s, in any way?
1442019-06-22T08:26:25  <luke-jr> kallewoof: IMO wallets should not accept multiple payments with the same address, and if they do, should flag them all as permanently unconfirmed until the specific UTXOs get spent (which is kinda unrelated to the payment, but confirmations usually are anyway)
1452019-06-22T08:27:23  <luke-jr> (or possibly flag one as confirmed, and spend only that one by itself, waiting for it to be confirmed before any others are spent)
1462019-06-22T08:27:53  <kallewoof> luke-jr: Since miners can still mine those payments, you are saying that wallets should dinstiguish between them. That is what #13756 does, right?
1472019-06-22T08:27:55  <gribble> https://github.com/bitcoin/bitcoin/issues/13756 | wallet: "avoid_reuse" wallet flag for improved privacy by kallewoof · Pull Request #13756 · bitcoin/bitcoin · GitHub
1482019-06-22T08:28:27  <luke-jr> kallewoof: based on the address reuse alone, not address reuse PLUS "the UTXOs created were spent"
1492019-06-22T08:29:04  <sipa> what does the utxos being spent have to do with it?
1502019-06-22T08:29:11  <kallewoof> luke-jr: So basically, take what I did and add a further restriction where it immediately marks up the 2nd+ payments, even if I ahvent spent the first, right?
1512019-06-22T08:29:25  <luke-jr> kallewoof: right
1522019-06-22T08:29:37  <luke-jr> sipa: the current behaviour is the same as before, until a UTXO is spent
1532019-06-22T08:29:47  <sipa> ah
1542019-06-22T08:30:25  <sipa> i don't understand what spending has to do with it still
1552019-06-22T08:30:47  <luke-jr> kallewoof: some care may be needed in the case of multiple un-mined transactions paying the same address; you'd probably want to mark the lower value regardless of arrival order
1562019-06-22T08:30:58  <sipa> or whether you're talking about behavior in a release, in master, or how you imagine it
1572019-06-22T08:31:01  <kallewoof> sipa: idea is, even if you send multiple times, no harm/no foul until i spend it. assuming i spend it all at once, you wont gain anything from giving me extra money.
1582019-06-22T08:31:16  <luke-jr> kallewoof: but there IS harm/foul
1592019-06-22T08:31:34  <luke-jr> just not that narrow specific case you addressed
1602019-06-22T08:32:09  <kallewoof> luke-jr: I mean, yes, but the harm/foul happened before I even spent the outputs.
1612019-06-22T08:32:29  <sipa> well the issue is someone *expecting* multiple payments to the same address
1622019-06-22T08:32:38  <sipa> that issue is addressed by educating
1632019-06-22T08:33:05  <sipa> once the payments have been made, there is a distinct issue, which is a privacy loss
1642019-06-22T08:33:37  <sipa> which only manifests if being paid again after already having spent the first utxo
1652019-06-22T08:33:37  <luke-jr> the current-master strange behaviour is only going to make education worse :p
1662019-06-22T08:34:00  *** skylove has joined #bitcoin-core-dev
1672019-06-22T08:35:23  <sipa> i doubt that
1682019-06-22T08:35:49  <kallewoof> I need to go, but I will see if I can figure out what the problem is and how to fix it. I am honestly a bit confused. And surprised.
1692019-06-22T08:36:04  <luke-jr> it will further the myth that address reuse is only harmful if you "spend from" it first
1702019-06-22T08:36:40  <luke-jr> (which will in turn strengthen and for the first time give Core credibility to the "from address" myth)
1712019-06-22T08:38:16  <luke-jr> I should also go to bed
1722019-06-22T08:39:17  *** spinza has joined #bitcoin-core-dev
1732019-06-22T08:43:11  *** sfhi2 has joined #bitcoin-core-dev
1742019-06-22T08:46:57  *** sfhi has quit IRC
1752019-06-22T08:58:48  *** tripleslash has joined #bitcoin-core-dev
1762019-06-22T08:59:38  *** sfhi has joined #bitcoin-core-dev
1772019-06-22T09:00:01  *** phyll1s_work has quit IRC
1782019-06-22T09:02:37  *** sfhi2 has quit IRC
1792019-06-22T09:03:59  *** dfreedm has joined #bitcoin-core-dev
1802019-06-22T09:13:45  *** rex4539 has joined #bitcoin-core-dev
1812019-06-22T09:21:25  *** luke-jr has quit IRC
1822019-06-22T09:24:12  *** luke-jr has joined #bitcoin-core-dev
1832019-06-22T09:26:49  *** skylove has quit IRC
1842019-06-22T09:37:01  *** promag_ has joined #bitcoin-core-dev
1852019-06-22T09:37:02  *** promag has quit IRC
1862019-06-22T09:47:56  *** michaelfolkson has joined #bitcoin-core-dev
1872019-06-22T09:59:52  *** rex4539 has quit IRC
1882019-06-22T10:00:49  *** bitcoin-git has joined #bitcoin-core-dev
1892019-06-22T10:00:50  <bitcoin-git> [bitcoin] meshcollider pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/32e94538185b...2cbcc55ba6ae
1902019-06-22T10:00:50  <bitcoin-git> bitcoin/master 53c3c1e Karl-Johan Alm: wallet/rpc/getbalances: add entry for 'mine.used' balance in results
1912019-06-22T10:00:51  <bitcoin-git> bitcoin/master 3d2ff37 Karl-Johan Alm: wallet/rpc: use static help text
1922019-06-22T10:00:52  <bitcoin-git> bitcoin/master 71d0344 Karl-Johan Alm: docs: release note wording
1932019-06-22T10:00:53  *** bitcoin-git has left #bitcoin-core-dev
1942019-06-22T10:01:49  *** bitcoin-git has joined #bitcoin-core-dev
1952019-06-22T10:01:49  <bitcoin-git> [bitcoin] meshcollider merged pull request #16239: wallet/rpc: follow-up clean-up/fixes to avoid_reuse (master...2019-06-followup-avoidreuse) https://github.com/bitcoin/bitcoin/pull/16239
1962019-06-22T10:01:50  *** bitcoin-git has left #bitcoin-core-dev
1972019-06-22T10:03:47  *** michaelfolkson has quit IRC
1982019-06-22T10:17:10  *** spinza has quit IRC
1992019-06-22T10:18:14  <meshcollider> promag: what's the status with #13339, is that still happening or should it be closed?
2002019-06-22T10:18:17  <gribble> https://github.com/bitcoin/bitcoin/issues/13339 | wallet: Replace %w by wallet name in -walletnotify script by promag · Pull Request #13339 · bitcoin/bitcoin · GitHub
2012019-06-22T10:21:00  *** emilengler has joined #bitcoin-core-dev
2022019-06-22T10:25:49  *** belcher has quit IRC
2032019-06-22T10:34:46  *** sfhi has quit IRC
2042019-06-22T10:40:34  <fanquake> meshcollider when thinking about the wallet GUI, what end user do you normally have in mind? Somewhere on the spectrum of "new non-technical user, just downloaded Bitcoin Core" & "one of the engineers that helps build Bitcoin Core"?
2052019-06-22T10:40:56  *** rex4539 has joined #bitcoin-core-dev
2062019-06-22T10:41:34  <fanquake> Just trying to figure out who we are targeting in #15450. Seems like it's leaning towards engineers.
2072019-06-22T10:41:38  <gribble> https://github.com/bitcoin/bitcoin/issues/15450 | [GUI] Create wallet menu option by achow101 · Pull Request #15450 · bitcoin/bitcoin · GitHub
2082019-06-22T10:42:56  <meshcollider> fanquake: usually the former, I think more advanced users will prefer to use the command line anyway, I think the two main purposes the GUI serves in my mind is 1) for less technical users that just want to start it up and run bitcoin, and 2) for more advanced users to do stuff that would be really painful on the command line like coin selection stuff
2092019-06-22T10:44:30  <meshcollider> in that specific case, I think multiwallet is not inherently complicated if create, open, close, whatever are all available in the GUI?
2102019-06-22T10:44:40  <fanquake> Fair enough. I think we should really be trying to optimise for 1) (with hidden options/config etc still available for 2)).
2112019-06-22T10:44:52  <meshcollider> yeah I agree
2122019-06-22T10:44:58  *** bitcoin-git has joined #bitcoin-core-dev
2132019-06-22T10:44:58  <bitcoin-git> [bitcoin] fanatid opened pull request #16267: bench: Benchmark blockToJSON (master...bench-blocktojson) https://github.com/bitcoin/bitcoin/pull/16267
2142019-06-22T10:44:59  *** bitcoin-git has left #bitcoin-core-dev
2152019-06-22T10:45:57  <meshcollider> but at least in my mind, most computer-users are familiar with basic open, close, create commands, it seems natural to have a create command if we already have decent GUI multiwallet support
2162019-06-22T10:46:53  <fanquake> Yea I've got no issue with create. I'm thinking in the create flow. In the ideal non-technical user world, we've just got the name field, with those other three options hidden in a "Advanced Users" drop-down (and encrypt wallet checked by default, if that's not too aggressive).
2172019-06-22T10:47:16  <fanquake> and there'd be no way to tick encrypt wallet, and actually end up with an unencrypted wallet.
2182019-06-22T10:47:57  <meshcollider> yep
2192019-06-22T10:48:13  <meshcollider> that would suit the general use case fine IMO
2202019-06-22T10:48:20  <fanquake> I'm even concerned "Make Blank Wallet" is going to get ticked quite a lot, when users don't mean it, because the logical non-technical thought will be, why would I want anything other than a blank wallet..
2212019-06-22T10:48:29  <fanquake> I'll add my thoughts to that discussion anyways.
2222019-06-22T10:49:17  <meshcollider> +1
2232019-06-22T10:49:51  *** spinza has joined #bitcoin-core-dev
2242019-06-22T11:53:14  *** spinza has quit IRC
2252019-06-22T11:55:57  *** omonk has joined #bitcoin-core-dev
2262019-06-22T11:58:55  *** spinza has joined #bitcoin-core-dev
2272019-06-22T12:00:01  *** dfreedm has quit IRC
2282019-06-22T12:00:32  *** surja795 has joined #bitcoin-core-dev
2292019-06-22T12:00:37  *** Guyver2 has quit IRC
2302019-06-22T12:05:27  *** surja795 has quit IRC
2312019-06-22T12:12:44  *** rex4539 has quit IRC
2322019-06-22T12:16:52  *** tw1sted1 has joined #bitcoin-core-dev
2332019-06-22T12:21:00  *** surja795 has joined #bitcoin-core-dev
2342019-06-22T12:25:53  *** surja795 has quit IRC
2352019-06-22T12:41:54  *** Chris_Stewart_5 has joined #bitcoin-core-dev
2362019-06-22T12:53:17  *** jtimon has joined #bitcoin-core-dev
2372019-06-22T13:09:24  *** emilengler has quit IRC
2382019-06-22T13:18:16  *** jtimon has quit IRC
2392019-06-22T13:20:07  <achow101> fanquake: I looked at having the options hidden, but I couldn't figure out how to do it in qt with a lot of hacks and things I don't know how to do
2402019-06-22T13:20:39  <achow101> Re blank wallet, do you have any suggestions for a better name?
2412019-06-22T13:37:06  *** rex4539 has joined #bitcoin-core-dev
2422019-06-22T13:42:43  *** scoop has joined #bitcoin-core-dev
2432019-06-22T13:50:02  *** cubancorona has quit IRC
2442019-06-22T13:50:23  *** cubancorona has joined #bitcoin-core-dev
2452019-06-22T13:50:36  *** d_t has joined #bitcoin-core-dev
2462019-06-22T13:51:55  *** lnostdal has quit IRC
2472019-06-22T13:52:13  *** bralyclow01 has joined #bitcoin-core-dev
2482019-06-22T13:53:14  <fanquake> achow101: That's fair enough. I'm not sure re "Blank", going to think about it a bit more.
2492019-06-22T13:55:06  *** d_t has quit IRC
2502019-06-22T13:55:38  *** bralyclow has quit IRC
2512019-06-22T14:11:18  *** surja795 has joined #bitcoin-core-dev
2522019-06-22T14:16:11  *** surja795 has quit IRC
2532019-06-22T14:17:12  *** bralyclow01 has quit IRC
2542019-06-22T14:17:37  *** bralyclow has joined #bitcoin-core-dev
2552019-06-22T14:21:05  *** lightlike has joined #bitcoin-core-dev
2562019-06-22T14:32:50  *** lnostdal has joined #bitcoin-core-dev
2572019-06-22T14:37:03  *** Guyver2 has joined #bitcoin-core-dev
2582019-06-22T14:40:34  *** scoop has quit IRC
2592019-06-22T14:47:15  *** Chris_Stewart_5 has quit IRC
2602019-06-22T14:51:44  *** bralyclow has quit IRC
2612019-06-22T14:52:09  *** michaelfolkson has joined #bitcoin-core-dev
2622019-06-22T14:52:19  *** bralyclow has joined #bitcoin-core-dev
2632019-06-22T15:00:01  *** tw1sted1 has quit IRC
2642019-06-22T15:07:22  *** surja795 has joined #bitcoin-core-dev
2652019-06-22T15:12:09  *** surja795 has quit IRC
2662019-06-22T15:31:36  *** aseem has joined #bitcoin-core-dev
2672019-06-22T15:35:41  *** RISCi_ATOM1 has joined #bitcoin-core-dev
2682019-06-22T15:39:38  *** aseem has quit IRC
2692019-06-22T15:50:07  *** aseem has joined #bitcoin-core-dev
2702019-06-22T15:50:54  *** lnostdal has quit IRC
2712019-06-22T15:52:06  *** bralyclow has quit IRC
2722019-06-22T15:52:52  *** bralyclow has joined #bitcoin-core-dev
2732019-06-22T15:54:09  *** bralyclow01 has joined #bitcoin-core-dev
2742019-06-22T15:55:08  *** aseem has quit IRC
2752019-06-22T15:57:58  *** bralyclow has quit IRC
2762019-06-22T16:01:37  *** scoop has joined #bitcoin-core-dev
2772019-06-22T16:05:09  *** sakalli_ has joined #bitcoin-core-dev
2782019-06-22T16:05:32  *** sakalli_ has joined #bitcoin-core-dev
2792019-06-22T16:05:52  *** scoop has quit IRC
2802019-06-22T16:05:53  *** sakalli_ has joined #bitcoin-core-dev
2812019-06-22T16:06:36  *** d_t has joined #bitcoin-core-dev
2822019-06-22T16:10:26  *** sakalli_ has quit IRC
2832019-06-22T16:15:39  *** bralyclow01 has quit IRC
2842019-06-22T16:16:04  *** bralyclow has joined #bitcoin-core-dev
2852019-06-22T16:24:41  *** bralyclow has quit IRC
2862019-06-22T16:25:32  *** lnostdal has joined #bitcoin-core-dev
2872019-06-22T16:25:42  *** bralyclow has joined #bitcoin-core-dev
2882019-06-22T16:30:02  *** bralyclow has quit IRC
2892019-06-22T16:39:49  *** michaelfolkson has quit IRC
2902019-06-22T17:07:33  *** lightlike has quit IRC
2912019-06-22T17:20:32  *** belcher has joined #bitcoin-core-dev
2922019-06-22T17:25:43  *** bralyclow has joined #bitcoin-core-dev
2932019-06-22T17:29:45  *** PastaPasta has joined #bitcoin-core-dev
2942019-06-22T17:30:09  *** pinheadmz has joined #bitcoin-core-dev
2952019-06-22T17:52:58  *** aseem has joined #bitcoin-core-dev
2962019-06-22T17:56:46  *** justanotheruser has quit IRC
2972019-06-22T17:57:10  *** justanotheruser has joined #bitcoin-core-dev
2982019-06-22T17:58:43  *** surja795 has joined #bitcoin-core-dev
2992019-06-22T18:00:02  *** RISCi_ATOM1 has quit IRC
3002019-06-22T18:04:19  *** guilhermeblanco has joined #bitcoin-core-dev
3012019-06-22T18:06:08  *** aseem has quit IRC
3022019-06-22T18:07:02  *** aseem has joined #bitcoin-core-dev
3032019-06-22T18:10:50  *** bralyclow01 has joined #bitcoin-core-dev
3042019-06-22T18:11:26  *** aseem has joined #bitcoin-core-dev
3052019-06-22T18:12:58  *** bralyclow has quit IRC
3062019-06-22T18:16:38  *** aseem has quit IRC
3072019-06-22T18:21:46  *** rex4539 has quit IRC
3082019-06-22T18:33:56  *** bralyclow01 has quit IRC
3092019-06-22T18:34:18  *** bralyclow has joined #bitcoin-core-dev
3102019-06-22T18:40:03  *** surja795 has quit IRC
3112019-06-22T18:41:26  *** oneark has quit IRC
3122019-06-22T18:45:22  *** ddustin has joined #bitcoin-core-dev
3132019-06-22T18:49:14  *** ddustin has quit IRC
3142019-06-22T18:53:30  *** ddustin has joined #bitcoin-core-dev
3152019-06-22T18:58:16  *** aseem has joined #bitcoin-core-dev
3162019-06-22T19:00:43  *** aseem has quit IRC
3172019-06-22T19:02:15  *** aseem has joined #bitcoin-core-dev
3182019-06-22T19:04:22  *** ghost43 has quit IRC
3192019-06-22T19:04:46  *** ghost43 has joined #bitcoin-core-dev
3202019-06-22T19:14:38  *** surja795 has joined #bitcoin-core-dev
3212019-06-22T19:15:40  *** PastaPasta has quit IRC
3222019-06-22T19:22:30  *** ddustin has quit IRC
3232019-06-22T19:24:46  *** ddustin has joined #bitcoin-core-dev
3242019-06-22T19:34:37  *** surja795 has quit IRC
3252019-06-22T19:41:23  *** aseem has quit IRC
3262019-06-22T19:41:55  *** aseem has joined #bitcoin-core-dev
3272019-06-22T19:45:21  *** Victorsueca has quit IRC
3282019-06-22T19:47:12  *** Victorsueca has joined #bitcoin-core-dev
3292019-06-22T19:49:22  *** aseem_ has joined #bitcoin-core-dev
3302019-06-22T19:49:37  *** Chris_Stewart_5 has joined #bitcoin-core-dev
3312019-06-22T19:49:49  *** surja795 has joined #bitcoin-core-dev
3322019-06-22T19:50:50  *** aseem has quit IRC
3332019-06-22T19:50:51  *** aseem_ is now known as aseem
3342019-06-22T19:55:27  *** hugohn has joined #bitcoin-core-dev
3352019-06-22T19:57:47  *** aseem has quit IRC
3362019-06-22T20:00:01  *** surja795 has quit IRC
3372019-06-22T20:04:36  *** d_t has quit IRC
3382019-06-22T20:09:20  *** BlueMatt has quit IRC
3392019-06-22T20:09:42  *** BlueMatt has joined #bitcoin-core-dev
3402019-06-22T20:10:25  *** rex4539 has joined #bitcoin-core-dev
3412019-06-22T20:27:29  *** ddustin has quit IRC
3422019-06-22T20:55:00  *** michaelfolkson has joined #bitcoin-core-dev
3432019-06-22T20:58:06  *** Guyver2 has quit IRC
3442019-06-22T21:00:02  *** guilhermeblanco has quit IRC
3452019-06-22T21:04:42  *** phoenixlzx1 has joined #bitcoin-core-dev
3462019-06-22T21:05:39  *** michaelfolkson has quit IRC
3472019-06-22T21:23:42  *** michaelfolkson has joined #bitcoin-core-dev
3482019-06-22T21:25:02  *** rh0nj has quit IRC
3492019-06-22T21:26:08  *** rh0nj has joined #bitcoin-core-dev
3502019-06-22T21:27:41  *** PastaPasta has joined #bitcoin-core-dev
3512019-06-22T21:50:02  <ossifrage> I have 'onlynet=ipv4' in my bitcoin.conf, but I saw this today (with 2cbcc55ba) "Error: Couldn't open socket for incoming connections (socket returned error Address family not supported by protocol (97))"
3522019-06-22T21:54:27  *** ddustin has joined #bitcoin-core-dev
3532019-06-22T21:57:52  *** ddustin has quit IRC
3542019-06-22T21:58:29  *** ddustin has joined #bitcoin-core-dev
3552019-06-22T21:59:59  <ossifrage> Hmm, I looked back over the logs and it has been doing that for a while.
3562019-06-22T22:01:53  *** ddustin_ has joined #bitcoin-core-dev
3572019-06-22T22:01:55  *** ddustin has quit IRC
3582019-06-22T22:05:54  *** spinza has quit IRC
3592019-06-22T22:09:03  *** rafalcpp_ has joined #bitcoin-core-dev
3602019-06-22T22:09:28  *** rafalcpp has quit IRC
3612019-06-22T22:10:30  *** queip has quit IRC
3622019-06-22T22:17:25  *** queip has joined #bitcoin-core-dev
3632019-06-22T22:19:30  *** spinza has joined #bitcoin-core-dev
3642019-06-22T22:19:51  *** rafalcpp has joined #bitcoin-core-dev
3652019-06-22T22:20:48  *** rafalcpp_ has quit IRC
3662019-06-22T22:34:51  <sipa> ossifrage: onlynet is about outgoing connections, it does not affect incoming
3672019-06-22T22:42:50  *** IGHOR has quit IRC
3682019-06-22T22:45:30  *** IGHOR has joined #bitcoin-core-dev
3692019-06-22T22:50:56  *** IGHOR has quit IRC
3702019-06-22T22:52:49  <ossifrage> sipa, ah, thanks
3712019-06-22T22:53:23  *** ddustin_ has quit IRC
3722019-06-22T22:54:12  *** ddustin has joined #bitcoin-core-dev
3732019-06-22T22:54:49  *** IGHOR has joined #bitcoin-core-dev
3742019-06-22T23:03:47  *** michaelfolkson has quit IRC
3752019-06-22T23:10:32  *** scoop has joined #bitcoin-core-dev
3762019-06-22T23:12:46  *** d_t has joined #bitcoin-core-dev
3772019-06-22T23:14:16  *** jonatack has joined #bitcoin-core-dev
3782019-06-22T23:14:31  *** scoop has quit IRC
3792019-06-22T23:15:21  *** d_t has quit IRC
3802019-06-22T23:16:35  *** jonatack has quit IRC
3812019-06-22T23:22:51  *** IGHOR has quit IRC
3822019-06-22T23:26:31  *** scoop has joined #bitcoin-core-dev
3832019-06-22T23:27:16  *** IGHOR has joined #bitcoin-core-dev
3842019-06-22T23:28:31  *** simplecoin has joined #bitcoin-core-dev
3852019-06-22T23:31:19  *** scoop has quit IRC
3862019-06-22T23:32:40  *** ctrlbreak has quit IRC
3872019-06-22T23:33:08  *** ctrlbreak has joined #bitcoin-core-dev
3882019-06-22T23:41:17  *** belcher has quit IRC
3892019-06-22T23:42:10  *** belcher has joined #bitcoin-core-dev
3902019-06-22T23:44:54  *** justanotheruser has quit IRC
3912019-06-22T23:46:53  *** scoop has joined #bitcoin-core-dev
3922019-06-22T23:50:07  *** simplecoin has quit IRC
3932019-06-22T23:55:46  *** scoop has quit IRC
3942019-06-22T23:55:49  *** jtimon has joined #bitcoin-core-dev
3952019-06-22T23:59:37  *** scoop has joined #bitcoin-core-dev