12017-01-27T00:10:08  *** lightningbot has joined #bitcoin-core-dev
  22017-01-27T00:13:18  <jtimon> another question about gitian, why are there signed and unsigned builds for win and osx in https://github.com/bitcoin-core/gitian.sigs ? (according to the guide it seems I should build and sign the unsigned ones)
  32017-01-27T00:13:51  <sipa> jtimon: because the signed ones require a key that is not public
  42017-01-27T00:14:11  <sipa> so people can build the unsigned one, compare results, then the person with the key can produce the detached signatures
  52017-01-27T00:14:26  <sipa> and then people can build the signed one from the earlier unsigned result plus downloaded detached signature
  62017-01-27T00:15:42  <gmaxwell> I am proud to work with people who come up with such slick procedures. :)
  72017-01-27T00:16:43  <jtimon> why do the signed ones require a key that's not public?
  82017-01-27T00:17:37  <gmaxwell> jtimon: signed in this case refers to the windows and apple code signing keys.
  92017-01-27T00:17:47  <gmaxwell> which are used to prevent ugly warning boxes on those OSes.
 102017-01-27T00:17:58  <gmaxwell> to anyone who pays the piper. :P
 112017-01-27T00:18:02  <jtimon> ohh, right
 122017-01-27T00:20:37  <jtimon> I'm having problems building osx, I think I did all well, https://0bin.net/paste/U+Sqgot+Xk0VO-kL#cQl5R4xNHgCBRNxC5IoHZd7aW-dPJKTNO2ghEPVm0rz
 132017-01-27T00:21:20  <sipa> jtimon: you don't have the MacOSX SDK
 142017-01-27T00:21:25  <sipa> tar: MacOSX10.11.sdk.tar.gz: Cannot stat: No such file or directory
 152017-01-27T00:22:14  <jtimon> oh, I thought it would download it by itself or something, I see
 162017-01-27T00:22:52  <sipa> no, it can't, license issues
 172017-01-27T00:23:10  <sipa> you need to register for an mac developer account, i think
 182017-01-27T00:23:37  <jtimon> I see, thanks again
 192017-01-27T00:29:02  *** aguycalled has quit IRC
 202017-01-27T00:29:50  *** AaronvanW has quit IRC
 212017-01-27T00:30:07  *** aguycalled has joined #bitcoin-core-dev
 222017-01-27T00:34:09  *** AaronvanW has joined #bitcoin-core-dev
 232017-01-27T00:34:29  *** aguycalled has quit IRC
 242017-01-27T00:38:40  *** AaronvanW has quit IRC
 252017-01-27T00:49:55  *** echonaut2 has quit IRC
 262017-01-27T00:50:07  *** echonaut has joined #bitcoin-core-dev
 272017-01-27T00:50:37  *** belcher has quit IRC
 282017-01-27T00:54:30  <michagogo> Yep
 292017-01-27T00:54:43  <michagogo> You need to log into developer.apple.com
 302017-01-27T00:54:57  <michagogo> (You don't need the $99 membership, a free account is enough)
 312017-01-27T00:55:27  <michagogo> Then you need to download Xcode, and pull out the SDK directory from within that
 322017-01-27T00:55:52  <michagogo> Unfortunately that can only be done (as of the last I heard) on a Mac
 332017-01-27T00:57:46  <luke-jr> michagogo: I posted some doc to the git repo with non-Mac instructions IIRC
 342017-01-27T00:58:07  <michagogo> Oh, really?
 352017-01-27T00:58:10  * michagogo looks
 362017-01-27T00:58:46  <sipa> luke-jr: is it included in the bitcoin repo?
 372017-01-27T00:58:49  <sipa> +core
 382017-01-27T00:59:08  *** abpa has quit IRC
 392017-01-27T00:59:10  <luke-jr> https://github.com/bitcoin/bitcoin/blob/master/doc/README_osx.md
 402017-01-27T00:59:12  <luke-jr> sipa: yes ^
 412017-01-27T00:59:22  <luke-jr> "Alternatively, you can use 7zip and SleuthKit to extract the files one by one. The script contrib/macdeploy/extract-osx-sdk.sh automates this. First ensure the dmg file is in the current directory, and then run the script. You may wish to delete the intermediate 5.hfs file and MacOSX10.11.sdk (the directory) when you've confirmed the extraction succeeded." …
 422017-01-27T00:59:59  <michagogo> Ah, yes
 432017-01-27T01:00:00  <michagogo> https://github.com/bitcoin/bitcoin/blob/master/contrib/macdeploy/extract-osx-sdk.sh
 442017-01-27T01:00:03  <michagogo> Nice!
 452017-01-27T01:01:33  <michagogo> August?
 462017-01-27T01:01:34  <sipa> luke-jr: ok, thanks
 472017-01-27T01:01:40  <michagogo> Wow, I've been out of the loop for a long time.
 482017-01-27T01:01:47  <sipa> luke-jr: i remember you finding this, but i wasn't aware it actually got pred
 492017-01-27T01:04:18  *** belcher has joined #bitcoin-core-dev
 502017-01-27T01:08:44  <bitcoin-git> [bitcoin] luke-jr opened pull request #9642: [Hardfork] Safe block size limit (master...bip-blksize) https://github.com/bitcoin/bitcoin/pull/9642
 512017-01-27T01:38:50  *** arubi has quit IRC
 522017-01-27T01:39:12  *** arubi has joined #bitcoin-core-dev
 532017-01-27T01:57:30  *** Ylbam has quit IRC
 542017-01-27T02:35:37  *** AaronvanW has joined #bitcoin-core-dev
 552017-01-27T02:40:09  *** AaronvanW has quit IRC
 562017-01-27T03:05:43  *** buddhaghosa has quit IRC
 572017-01-27T03:36:50  *** AaronvanW has joined #bitcoin-core-dev
 582017-01-27T03:41:39  *** AaronvanW has quit IRC
 592017-01-27T04:02:24  *** kyletorpey has joined #bitcoin-core-dev
 602017-01-27T04:02:39  *** chris200_ has joined #bitcoin-core-dev
 612017-01-27T04:05:29  *** chris2000 has quit IRC
 622017-01-27T04:21:23  *** PaulCape_ has quit IRC
 632017-01-27T04:34:44  *** PaulCapestany has joined #bitcoin-core-dev
 642017-01-27T04:37:34  *** AaronvanW has joined #bitcoin-core-dev
 652017-01-27T04:43:05  *** AaronvanW has quit IRC
 662017-01-27T04:44:50  *** shesek has quit IRC
 672017-01-27T04:59:59  *** chris2000 has joined #bitcoin-core-dev
 682017-01-27T05:00:07  *** dermoth has quit IRC
 692017-01-27T05:01:06  *** dermoth has joined #bitcoin-core-dev
 702017-01-27T05:02:47  *** chris200_ has quit IRC
 712017-01-27T05:39:03  *** neha___ has quit IRC
 722017-01-27T05:39:36  *** AaronvanW has joined #bitcoin-core-dev
 732017-01-27T05:40:56  *** chjj has quit IRC
 742017-01-27T05:43:16  *** moli_ has quit IRC
 752017-01-27T05:43:20  *** mol has joined #bitcoin-core-dev
 762017-01-27T05:43:49  *** AaronvanW has quit IRC
 772017-01-27T05:44:53  *** cannon-c has joined #bitcoin-core-dev
 782017-01-27T05:52:17  *** paveljanik has quit IRC
 792017-01-27T05:53:06  *** Cheeseo has joined #bitcoin-core-dev
 802017-01-27T05:55:43  *** RoyceX has quit IRC
 812017-01-27T05:56:56  *** paveljanik has joined #bitcoin-core-dev
 822017-01-27T05:56:56  *** paveljanik has joined #bitcoin-core-dev
 832017-01-27T06:01:05  *** paveljanik has quit IRC
 842017-01-27T06:19:56  *** Saucery has joined #bitcoin-core-dev
 852017-01-27T06:40:15  *** AaronvanW has joined #bitcoin-core-dev
 862017-01-27T06:44:50  *** AaronvanW has quit IRC
 872017-01-27T06:53:03  *** Ylbam has joined #bitcoin-core-dev
 882017-01-27T07:00:50  *** chjj has joined #bitcoin-core-dev
 892017-01-27T07:02:35  *** kyletorpey has quit IRC
 902017-01-27T07:20:39  *** aguycalled has joined #bitcoin-core-dev
 912017-01-27T07:26:16  *** zxzzt has quit IRC
 922017-01-27T07:26:20  *** sdaftuar has quit IRC
 932017-01-27T07:26:29  *** morcos has quit IRC
 942017-01-27T07:27:10  *** ryanofsky has quit IRC
 952017-01-27T07:28:15  *** zxzzt has joined #bitcoin-core-dev
 962017-01-27T07:28:15  *** sdaftuar has joined #bitcoin-core-dev
 972017-01-27T07:28:16  *** sdaftuar has joined #bitcoin-core-dev
 982017-01-27T07:28:34  *** morcos has joined #bitcoin-core-dev
 992017-01-27T07:32:55  *** testtesttest has quit IRC
1002017-01-27T07:39:42  *** jtimon has quit IRC
1012017-01-27T07:40:41  *** ryanofsky has joined #bitcoin-core-dev
1022017-01-27T07:40:58  *** AaronvanW has joined #bitcoin-core-dev
1032017-01-27T07:45:29  *** AaronvanW has quit IRC
1042017-01-27T07:54:40  *** kadoban has quit IRC
1052017-01-27T08:02:20  *** BashCo has quit IRC
1062017-01-27T08:18:25  <bitcoin-git> [bitcoin] kallewoof opened pull request #9643: [refactor] Remove using namespace <xxx> from wallet/ & util* (master...no-using-namespace-wallet-util) https://github.com/bitcoin/bitcoin/pull/9643
1072017-01-27T08:22:48  *** windsok has quit IRC
1082017-01-27T08:26:21  *** paveljanik has joined #bitcoin-core-dev
1092017-01-27T08:26:22  *** paveljanik has joined #bitcoin-core-dev
1102017-01-27T08:30:44  *** BashCo has joined #bitcoin-core-dev
1112017-01-27T08:31:22  *** aguycalled has quit IRC
1122017-01-27T08:32:47  *** Saucery has quit IRC
1132017-01-27T08:45:29  *** aguycalled has joined #bitcoin-core-dev
1142017-01-27T08:52:15  *** windsok has joined #bitcoin-core-dev
1152017-01-27T09:05:28  *** Guyver2 has joined #bitcoin-core-dev
1162017-01-27T09:09:55  <bitcoin-git> [bitcoin] kallewoof opened pull request #9644: [refactor] Remove using namespace <xxx> from src/ (master...no-using-namespace-src) https://github.com/bitcoin/bitcoin/pull/9644
1172017-01-27T09:23:04  <Eliel_> 25
1182017-01-27T09:25:26  *** jannes has joined #bitcoin-core-dev
1192017-01-27T09:36:16  *** e4xit has quit IRC
1202017-01-27T09:36:40  *** isle2983 has quit IRC
1212017-01-27T09:36:50  *** e4xit has joined #bitcoin-core-dev
1222017-01-27T09:36:54  *** cannon-c is now known as cannon-c_AFK
1232017-01-27T09:54:17  *** AaronvanW has joined #bitcoin-core-dev
1242017-01-27T09:54:17  *** AaronvanW has joined #bitcoin-core-dev
1252017-01-27T10:02:35  *** cannon-c_AFK is now known as cannon-c
1262017-01-27T10:17:14  *** Guyver2 has quit IRC
1272017-01-27T10:31:28  *** rgrant has joined #bitcoin-core-dev
1282017-01-27T10:34:51  <rgrant> can someone point me at the function that backfills local blockchain blocks to include witness data if user upgrades to a segwit full node after segwit activation?
1292017-01-27T10:53:43  <rgrant> it looks like BLOCK_OPT_WITNESS stores some activation data for the block, but it also looks like this is not queried to see if backfill is necessary.  i could also use some help tracking down what happens if a segwit-capable node only finds itself connected to non-segwit nodes while receiving a block.
1302017-01-27T11:10:11  *** frabrunelle has quit IRC
1312017-01-27T11:13:37  *** laurentmt has joined #bitcoin-core-dev
1322017-01-27T11:18:01  *** laurentmt has quit IRC
1332017-01-27T11:18:20  *** frabrunelle has joined #bitcoin-core-dev
1342017-01-27T11:22:43  *** paveljanik has quit IRC
1352017-01-27T11:30:48  *** gradient_ has joined #bitcoin-core-dev
1362017-01-27T11:32:32  *** gradient_ has quit IRC
1372017-01-27T11:33:10  *** gradientskier has joined #bitcoin-core-dev
1382017-01-27T11:36:23  *** gradientskier has quit IRC
1392017-01-27T11:42:45  *** waxwing has quit IRC
1402017-01-27T11:54:00  *** rafalcpp has quit IRC
1412017-01-27T12:13:09  *** isle2983 has joined #bitcoin-core-dev
1422017-01-27T12:27:14  *** cannon-c has quit IRC
1432017-01-27T12:34:16  *** BashCo has quit IRC
1442017-01-27T12:34:53  *** BashCo has joined #bitcoin-core-dev
1452017-01-27T12:41:48  *** aguycalled has quit IRC
1462017-01-27T12:56:52  *** face has quit IRC
1472017-01-27T13:03:00  *** waxwing has joined #bitcoin-core-dev
1482017-01-27T13:17:57  <sdaftuar> rgrant: see RewindBlockIndex, in validation.cpp (assuming you're looking at master)
1492017-01-27T13:27:59  <sdaftuar> rgrant: after segwit activates, segwit-capable nodes will only attempt to download blocks from segwit-capable peers (which is why 0.13.1 introduced outbound peering logic that would specifically seek out segwit-capable peers)
1502017-01-27T13:36:31  *** JackH has quit IRC
1512017-01-27T13:47:43  <rgrant> sdaftuar: thx!  it does use BLOCK_OPT_WITNESS, too.  not sure how i missed that in my search.
1522017-01-27T14:40:05  *** windsok has quit IRC
1532017-01-27T14:44:25  *** aguycalled has joined #bitcoin-core-dev
1542017-01-27T14:59:01  *** d9b4bef9 has quit IRC
1552017-01-27T15:00:08  *** d9b4bef9 has joined #bitcoin-core-dev
1562017-01-27T15:08:15  *** windsok has joined #bitcoin-core-dev
1572017-01-27T15:15:00  *** oven has quit IRC
1582017-01-27T15:16:59  *** oven has joined #bitcoin-core-dev
1592017-01-27T15:18:00  <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/9b4d2673b775...d9e4d1d9fbd9
1602017-01-27T15:18:00  <bitcoin-git> bitcoin/master 04b8773 Jonas Schnelli: [Qt] fix transaction details output-index to reflect vout index
1612017-01-27T15:18:01  <bitcoin-git> bitcoin/master d9e4d1d Wladimir J. van der Laan: Merge #9637: [Qt] fix transaction details output-index to reflect vout index...
1622017-01-27T15:18:20  <bitcoin-git> [bitcoin] laanwj closed pull request #9637: [Qt] fix transaction details output-index to reflect vout index (master...2017/01/qt_vout) https://github.com/bitcoin/bitcoin/pull/9637
1632017-01-27T15:24:10  *** rgrant has left #bitcoin-core-dev
1642017-01-27T15:28:04  *** kadoban has joined #bitcoin-core-dev
1652017-01-27T15:33:39  <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/d9e4d1d9fbd9...a7ea2f8fdbe9
1662017-01-27T15:33:39  <bitcoin-git> bitcoin/master fab035f MarcoFalke: qa: Actually test assertions in pruning.py...
1672017-01-27T15:33:40  <bitcoin-git> bitcoin/master a7ea2f8 Wladimir J. van der Laan: Merge #9638: qa: Actually test assertions in pruning.py...
1682017-01-27T15:33:56  <bitcoin-git> [bitcoin] laanwj closed pull request #9638: qa: Actually test assertions in pruning.py (master...Mf1701-qaPruning_try) https://github.com/bitcoin/bitcoin/pull/9638
1692017-01-27T16:41:14  *** neha__ has joined #bitcoin-core-dev
1702017-01-27T16:46:09  *** jtimon has joined #bitcoin-core-dev
1712017-01-27T16:46:25  *** aguycall_ has joined #bitcoin-core-dev
1722017-01-27T16:46:52  *** aguycalled has quit IRC
1732017-01-27T16:52:06  *** BashCo has quit IRC
1742017-01-27T16:55:10  *** jtimon has quit IRC
1752017-01-27T16:57:22  *** windsok has quit IRC
1762017-01-27T16:57:23  *** abpa has joined #bitcoin-core-dev
1772017-01-27T17:19:03  *** BashCo has joined #bitcoin-core-dev
1782017-01-27T17:28:10  *** windsok has joined #bitcoin-core-dev
1792017-01-27T17:51:32  *** jtimon has joined #bitcoin-core-dev
1802017-01-27T18:27:19  *** oven has quit IRC
1812017-01-27T19:09:22  *** instagibbs has joined #bitcoin-core-dev
1822017-01-27T20:00:27  *** Guyver2 has joined #bitcoin-core-dev
1832017-01-27T20:07:03  <luke-jr> is anyone else working on #9493? (I wish github let us self-assign stuff..)
1842017-01-27T20:07:05  <gribble> https://github.com/bitcoin/bitcoin/issues/9493 | event_set_mem_functions is not available on all libevents · Issue #9493 · bitcoin/bitcoin · GitHub
1852017-01-27T20:11:44  *** waxwing has quit IRC
1862017-01-27T20:16:04  *** Kexkey has joined #bitcoin-core-dev
1872017-01-27T20:19:47  <BlueMatt> luke-jr: looks like not? its either you or cfields probably
1882017-01-27T20:19:53  *** norotartagen has quit IRC
1892017-01-27T20:20:22  <cfields> luke-jr: last i looked you had a fix for it?
1902017-01-27T20:20:56  *** norotartagen has joined #bitcoin-core-dev
1912017-01-27T20:21:33  <cfields> yea, i assumed that define was all it took. If there's more to it, i'm happy to take a look
1922017-01-27T20:32:10  <luke-jr> it's probably not difficult, just didn't want to step on any toes
1932017-01-27T20:33:12  <luke-jr> just gotta figure out how to indicate a skipped test I guess
1942017-01-27T20:47:46  *** Kexkey has quit IRC
1952017-01-27T20:51:40  *** AaronvanW has quit IRC
1962017-01-27T20:51:44  *** aguycall_ is now known as aguycalled
1972017-01-27T20:52:16  *** AaronvanW has joined #bitcoin-core-dev
1982017-01-27T20:56:29  *** AaronvanW has quit IRC
1992017-01-27T21:04:49  *** abpa has quit IRC
2002017-01-27T21:17:36  *** Kexkey_ has joined #bitcoin-core-dev
2012017-01-27T21:21:03  *** Guyver2 has quit IRC
2022017-01-27T21:23:05  *** Guyver2 has joined #bitcoin-core-dev
2032017-01-27T21:36:57  *** waxwing has joined #bitcoin-core-dev
2042017-01-27T21:48:10  *** Kexkey_ has quit IRC
2052017-01-27T21:52:46  *** AaronvanW has joined #bitcoin-core-dev
2062017-01-27T21:52:46  *** AaronvanW has joined #bitcoin-core-dev
2072017-01-27T21:57:09  *** AaronvanW has quit IRC
2082017-01-27T21:58:44  *** aguycalled has quit IRC
2092017-01-27T21:59:11  *** aguycalled has joined #bitcoin-core-dev
2102017-01-27T22:07:47  <BlueMatt> cfields: what do you want to do about hSocket?
2112017-01-27T22:08:01  <cfields> BlueMatt: races, you mean?
2122017-01-27T22:08:04  <BlueMatt> yes
2132017-01-27T22:08:12  <BlueMatt> well "races"
2142017-01-27T22:08:16  <BlueMatt> not that they actually are, but....
2152017-01-27T22:08:29  <cfields> well, concurrent access
2162017-01-27T22:09:29  <cfields> BlueMatt: going forward, it'll all be contained to one thread. So again, it's just a matter of what we do for 0.14
2172017-01-27T22:09:44  <BlueMatt> it will?
2182017-01-27T22:09:50  <cfields> sec, taking a look. iirc it's mostly just disconnection that's problematic?
2192017-01-27T22:09:51  <BlueMatt> oh, you mean CloseSocketDisconnect will be? yea, ok
2202017-01-27T22:10:05  <BlueMatt> its entirely only CloseSocketDisconnect thats problematic, iirc
2212017-01-27T22:11:22  <cfields> oh, and optimistic sends
2222017-01-27T22:12:33  *** aguycalled has quit IRC
2232017-01-27T22:13:13  *** aguycalled has joined #bitcoin-core-dev
2242017-01-27T22:13:45  <cfields> BlueMatt: with my async refactors, CloseSocketDisconnect always happens on the sockethandler thread, the others just set fDisconnect
2252017-01-27T22:14:07  <BlueMatt> yea, ok, that sounds like what we /should/ do....but what about 0.14?
2262017-01-27T22:14:08  <cfields> i wonder if we could do a simplified version of that for 0.14
2272017-01-27T22:14:14  <BlueMatt> I havent looked, can we do that easily in 14?
2282017-01-27T22:15:38  <cfields> uhmm, just looking at it quickly, it seems so
2292017-01-27T22:16:11  <gmaxwell> if the behavior involved doesn't block, add a lock and move on.
2302017-01-27T22:16:44  <BlueMatt> gmaxwell: might as well fix it right, though
2312017-01-27T22:18:34  <cfields> BlueMatt: i think we'll still need a lock for the optimistic send :(
2322017-01-27T22:18:46  <BlueMatt> oh valid point, yea, likely
2332017-01-27T22:19:03  <BlueMatt> has anyone ever figured out how much optimistic send saves us?
2342017-01-27T22:19:17  <BlueMatt> like, notifying the other thread and having it do the send is like a few extra syscalls
2352017-01-27T22:19:18  <BlueMatt> so what
2362017-01-27T22:21:08  <cfields> BlueMatt: i think the only downside is you can end up at the tail of the sendqueue for that loop as opposed to sending immediately
2372017-01-27T22:21:27  <BlueMatt> "meh" ?
2382017-01-27T22:21:32  <cfields> but with the locks cleaned up now, i doubt there's much consequence there
2392017-01-27T22:21:45  <BlueMatt> oh, true, without the lock cleanups that would've been hell
2402017-01-27T22:21:54  <cfields> BlueMatt: well i think that could've been substantial before, with a long hold on the send lock
2412017-01-27T22:21:57  <BlueMatt> but, alright, lets call that a 0.15 optimization and just add a lock for 0.14?
2422017-01-27T22:22:32  <cfields> BlueMatt: yes, afraid so :(
2432017-01-27T22:22:42  <BlueMatt> ok, well shouldnt be a big deal
2442017-01-27T22:23:07  <BlueMatt> if your send() is blocking, you have bigger problems :p
2452017-01-27T22:23:33  <cfields> heh
2462017-01-27T22:23:52  <cfields> true i suppose. Scope can basically be limited to send/recv/close, right?
2472017-01-27T22:24:04  <BlueMatt> I'd hope so?
2482017-01-27T22:24:16  <BlueMatt> I havent looked in a while
2492017-01-27T22:24:49  <cfields> mm, worth looking at select/fd_set's safety guarantees
2502017-01-27T22:25:17  <cfields> BlueMatt: heh, hint taken. I'll work up a patch for discussion.
2512017-01-27T22:25:24  <BlueMatt> are we close()ing in CloseSocketDisconnect, or just disconnect()?
2522017-01-27T22:25:29  <BlueMatt> sorry, wasnt a hint, just saying
2532017-01-27T22:26:23  <BlueMatt> oh, hum, we are
2542017-01-27T22:26:24  <BlueMatt> yea, that sucks
2552017-01-27T22:26:32  <cfields> close/closesocket
2562017-01-27T22:28:00  <BlueMatt> cfields: ouch, yea, then maybe we do need the full patch now, then
2572017-01-27T22:28:14  <BlueMatt> to avoid calling CloseSocketDisconnect on any thread but ThreadSocketHandler
2582017-01-27T22:28:47  <BlueMatt> hum...orrrr...no, because select will just return and we'll still get the lock when we recv or send?
2592017-01-27T22:28:57  <BlueMatt> i mean i guess it should be fine, but might prefer not to?
2602017-01-27T22:29:46  *** aguycall_ has joined #bitcoin-core-dev
2612017-01-27T22:29:48  *** aguycalled has quit IRC
2622017-01-27T22:40:14  <cfields> BlueMatt: just for the sake of covering all angles... this concurrent access isn't new, right? much more likely maybe, but i'm pretty sure this has always been the case
2632017-01-27T22:41:59  <BlueMatt> yes, I believe this is very, very, very old
2642017-01-27T22:42:11  <BlueMatt> but havent gone back to make sure
2652017-01-27T23:04:19  *** molz_ has joined #bitcoin-core-dev
2662017-01-27T23:06:41  *** mol has quit IRC
2672017-01-27T23:09:33  *** molz_ has quit IRC
2682017-01-27T23:09:55  *** molz_ has joined #bitcoin-core-dev
2692017-01-27T23:10:27  *** AaronvanW has joined #bitcoin-core-dev
2702017-01-27T23:14:13  *** gradientskier has joined #bitcoin-core-dev
2712017-01-27T23:16:49  *** AaronvanW has quit IRC
2722017-01-27T23:52:26  *** Guyver2 has quit IRC
2732017-01-27T23:59:26  *** aguycall_ has quit IRC