12017-02-19T00:02:18  *** isle2983 has quit IRC
  22017-02-19T00:04:43  *** isle2983 has joined #bitcoin-core-dev
  32017-02-19T00:07:21  *** wasi has joined #bitcoin-core-dev
  42017-02-19T00:12:16  *** isle2983 has quit IRC
  52017-02-19T00:23:14  *** goksinen has quit IRC
  62017-02-19T00:45:51  *** handlex has joined #bitcoin-core-dev
  72017-02-19T00:49:15  *** handlex has quit IRC
  82017-02-19T01:01:38  *** aburan_ has quit IRC
  92017-02-19T01:02:53  *** Arvidt has quit IRC
 102017-02-19T01:08:06  *** aburan_ has joined #bitcoin-core-dev
 112017-02-19T01:08:47  *** Arvidt has joined #bitcoin-core-dev
 122017-02-19T01:46:15  *** AaronvanW has quit IRC
 132017-02-19T02:00:31  *** aburan_ has quit IRC
 142017-02-19T02:15:10  <bitcoin-git> [bitcoin] fanquake closed pull request #8660: txoutsbyaddress index (take 2) (master...cozz8) https://github.com/bitcoin/bitcoin/pull/8660
 152017-02-19T02:17:02  *** d9b4bef9 has quit IRC
 162017-02-19T02:18:08  *** d9b4bef9 has joined #bitcoin-core-dev
 172017-02-19T02:32:46  *** fanquake has joined #bitcoin-core-dev
 182017-02-19T02:33:18  <fanquake> cfields pushed my signed sigs up. Can try help debug gitian issues during today.
 192017-02-19T02:33:36  <fanquake> Also noticed that zlib doesn't currently build with osx depends builder
 202017-02-19T02:34:00  *** Ylbam has quit IRC
 212017-02-19T02:45:22  *** fanquake has quit IRC
 222017-02-19T03:02:09  <luke-jr> re "About Qt": we're using "About %1" now anyway, so the translation issue is presumably gone, and Qt might actually be worth promoting anyway; thinking perhaps what would be an improvement there is to add an "About Bitcoin" :p
 232017-02-19T03:10:08  <gmaxwell> luke-jr: It might be better to put the QT link though on the about bitcoin core page though.
 242017-02-19T03:10:19  <gmaxwell> the about qt thing is really uninteresting.
 252017-02-19T03:10:20  <luke-jr> hmm
 262017-02-19T03:10:49  <luke-jr> so the menu would have About Bitcoin Core and About Bitcoin; and the former's dialog have a link for About Qt?
 272017-02-19T03:13:49  <gmaxwell> I think that would be dandy. I dunno what about Bitcoin would say.
 282017-02-19T03:14:12  <gmaxwell> I think all this is kind of pointless, user use of bitcoin is dying because of sync resource requirements.
 292017-02-19T03:16:06  <luke-jr> true, better things to spend time on esp since the translation issue is basically fixed
 302017-02-19T03:22:27  *** chjj has quit IRC
 312017-02-19T03:24:58  *** fanquake has joined #bitcoin-core-dev
 322017-02-19T03:31:29  <gmaxwell> I'd be happy to ack a patch to improve the about messages but I think it's a waste of time to work on that.
 332017-02-19T03:37:15  *** moli_ has quit IRC
 342017-02-19T03:37:20  *** chjj has joined #bitcoin-core-dev
 352017-02-19T03:37:48  *** moli_ has joined #bitcoin-core-dev
 362017-02-19T03:39:15  *** moli_ has quit IRC
 372017-02-19T03:39:42  *** moli_ has joined #bitcoin-core-dev
 382017-02-19T03:51:40  *** Giszmo1 has quit IRC
 392017-02-19T04:23:58  *** JackH has quit IRC
 402017-02-19T04:24:15  *** moli_ has quit IRC
 412017-02-19T04:33:48  *** chris2000 has joined #bitcoin-core-dev
 422017-02-19T04:35:06  *** IRCFrEAK has joined #bitcoin-core-dev
 432017-02-19T04:36:40  *** chris200_ has quit IRC
 442017-02-19T04:37:32  *** goksinen has joined #bitcoin-core-dev
 452017-02-19T04:41:47  *** IRCFrEAK has left #bitcoin-core-dev
 462017-02-19T04:41:58  *** goksinen has quit IRC
 472017-02-19T04:48:27  *** chjj has quit IRC
 482017-02-19T04:50:15  <BlueMatt> <conman> do you understand the whitelist v addnode thing btw?
 492017-02-19T04:50:16  <BlueMatt> <conman> if I whitelist an IP address and addnode it, when I see it listed in the debug window it has the addnode'd IP there as not whitelisted
 502017-02-19T04:51:57  <gmaxwell> ugh, whitelist is not something conman should want for pratically anything. Addnode (in 0.14 at least) prevents banning, whitelisting adds to that near blindly and redundantly relaying transactions, which is not desirable for him, unless he's now become an armory developer. :P
 512017-02-19T04:52:51  <BlueMatt> yes, i figured, but also it is a strange thing that it doesnt whitelist for outbound
 522017-02-19T04:55:43  *** fengling has quit IRC
 532017-02-19T04:55:47  *** xiangfu_ has quit IRC
 542017-02-19T05:00:22  <BlueMatt> hum, yea, looks like addnode will only consider itself "connected" if IP:Port matches, not just IP, so if you, eg, addnode bidirectionally you're guaranteed to have two connections (unless the source uses 8333 for source port, which it wont)
 552017-02-19T05:00:24  <BlueMatt> afaict
 562017-02-19T05:01:30  <gmaxwell> yea, bidi results in two connections, I think I had believed there was no strong way to avoid it-- in any case, it's always been true.
 572017-02-19T05:02:03  <BlueMatt> i mean why do we only consider an addnode connected if its the same port?
 582017-02-19T05:02:07  <BlueMatt> might as well just filter by ip?
 592017-02-19T05:02:18  <gmaxwell> now I'm not sure why I was thinking it was hard to avoid. maybe just that being connected to the same IP is not the same as connecting to that IP due to the existance of NATs.
 602017-02-19T05:02:43  <BlueMatt> indeed, though if you addnode its probably fine
 612017-02-19T05:02:43  <gmaxwell> E.g. if you addnode my office, but have some random laptop at my office connected to you, you have not achieved your goal.
 622017-02-19T05:03:06  <gmaxwell> but perhaps it's close enough that the default should be to avoid the duplicate connection...
 632017-02-19T05:03:17  <BlueMatt> yes, that would be my vote
 642017-02-19T05:03:21  <gmaxwell> the other thing is that the addnode connection is privledged in ways that the inbound isn't.
 652017-02-19T05:04:04  <BlueMatt> true, but if the connection gets killed it'll re-open
 662017-02-19T05:04:16  <BlueMatt> possibly as -addnode
 672017-02-19T05:04:37  <BlueMatt> and we can do the same set-host-on-lookup thing we do for other connections and set the addnode flag if we find an applicable inbound connection
 682017-02-19T05:06:25  <gmaxwell> well as I said, inbound != addnode.  This would be much better with authentication keys, since you would know if it was who you thought it was.
 692017-02-19T05:07:02  <BlueMatt> yup, that
 702017-02-19T05:09:09  <gmaxwell> We could have some other kind of cookie based dedupe that worked more robustly.
 712017-02-19T05:09:36  <BlueMatt> true, though im no fan of encouraging more places where you can tie two nodes together as the same one
 722017-02-19T05:09:46  <BlueMatt> i know we have a few places with that and just added more, buttttt
 732017-02-19T05:11:23  <gmaxwell> well kinda hopeless, we should set a bar that we'd like to meet there. Like you shouldn't be able to correlate tor/ipv4+ipv6 as much as we can but otherwise we don't care. And especially shouldn't be able to correlate across restarts as much as we can.
 742017-02-19T05:11:34  <gmaxwell> the current informal method is not working well.
 752017-02-19T05:11:47  <BlueMatt> true
 762017-02-19T05:12:07  <gmaxwell> BlueMatt: and yea, we just added a _smoking hot_ identifier... so kinda moot. without a good framework we're just going to keep undermining ourselves while also missing good functionality.
 772017-02-19T05:12:12  <BlueMatt> i mean where all do we have that? double spend-based net splitting, compact blocks, addr stuff, what else?
 782017-02-19T05:12:32  <BlueMatt> i mean the compact block one is easy to split-by-netgroup
 792017-02-19T05:13:01  <gmaxwell> well lets ask the question, would we want to 'logically' behave like we had two mempools for ipv4 vs tor,  or just give up and say that the strongest property we try to achieve is unlinkablity across restarts?
 802017-02-19T05:13:22  <gmaxwell> Because thats the first choice there, if we're unwilling to do that then the best I think we can do is unlinkability across restarts.
 812017-02-19T05:13:25  <BlueMatt> heh, +/- saving mempool on disk :p
 822017-02-19T05:13:52  <gmaxwell> yea, well peers.dat is the big limitation on restarts right now, in fact. much more than mempool.
 832017-02-19T05:14:16  <BlueMatt> yea, ok
 842017-02-19T05:15:28  <BlueMatt> yea, its a shame keeping multiple peers.dat per-netgroup would kinda defeat the purpose of peers.dat :/
 852017-02-19T05:15:33  <gmaxwell> One of the open questions about mempool sync is do we want to make mempools convergent ... e.g. that you would switch to doublespends under some criteria.  Without that, I think our worst case synchronization bandwidth will always be quadratic.
 862017-02-19T05:16:21  <BlueMatt> yea, good question...i mean we could do some kind of lowest-hash metric, but that seems to amount to a not-by-fee-rbf
 872017-02-19T05:16:39  <BlueMatt> which also sucks, though i suppose the bw usage could be mitigated
 882017-02-19T05:16:59  <gmaxwell> BlueMatt: well the sorting criteria can be {fee,hash} which is basically what I menat by convergent.
 892017-02-19T05:17:07  <BlueMatt> yes, i assumed that
 902017-02-19T05:17:23  <gmaxwell> (or in particular, fee,H(salt,hash)  where salt is a random beacon to avoid being able to grind preferable txn.)
 912017-02-19T05:17:35  *** moli_ has joined #bitcoin-core-dev
 922017-02-19T05:17:50  <gmaxwell> and the fact that it's non-fee based replacement is actually not harmful... so long as the sync process rate limits itself.
 932017-02-19T05:18:03  <BlueMatt> random how? wouldnt it have to be network-wide? which would mean grindable
 942017-02-19T05:18:15  <BlueMatt> yesyes, generally agreed there
 952017-02-19T05:18:22  <gmaxwell> I think I can show that the bandwidth of that is polylog.
 962017-02-19T05:18:51  <gmaxwell> BlueMatt: e.g. using block hashes, so it would be network wide but your grindablity would be a finite window.
 972017-02-19T05:19:34  <BlueMatt> heh, well you only need to grind a lower hash...that shouldnt take you 10 minutes
 982017-02-19T05:20:46  <BlueMatt> anyway, just means an attacker can always create infinite amount of mempool divergence in a single tx, though they'd have to spend fee to actually put it in a higher-sync-rate-bucket
 992017-02-19T05:20:50  *** fengling has joined #bitcoin-core-dev
1002017-02-19T05:23:36  *** xiangfu has joined #bitcoin-core-dev
1012017-02-19T05:31:51  *** goksinen has joined #bitcoin-core-dev
1022017-02-19T05:35:05  *** asoltys has quit IRC
1032017-02-19T05:35:53  <BlueMatt> lol, recaptcha wasnt working so i tried the "audio version" and it just said "we're sorry, your computer may be sending automated queries, so we cannot process your request"
1042017-02-19T05:35:55  <BlueMatt> fuckers
1052017-02-19T05:36:18  *** goksinen has quit IRC
1062017-02-19T05:39:10  <gmaxwell> better than the google search captcha that just sends you really hard captchas and doesn't let you through no matter what.
1072017-02-19T05:39:24  <BlueMatt> thats what it was doing for the non-audio form, though
1082017-02-19T05:39:30  <BlueMatt> it just kept saying "try again"
1092017-02-19T05:40:12  <gmaxwell> yea, I think google does that intentionally on search... so perhaps they also do on recaptcha.
1102017-02-19T05:41:06  <BlueMatt> yea, likely, except they give it away if you try to switch to audio
1112017-02-19T05:42:06  <gmaxwell> Same shadowbanning BS that reddit does, so profoundly anti-social. The hope is to make spammers waste their time/money, and it ignores the people they harm when there is a false positive.
1122017-02-19T05:42:44  <BlueMatt> hum, im thinking its just straight up broken, doesnt work on a different browser/ip either
1132017-02-19T06:01:49  *** asoltys has joined #bitcoin-core-dev
1142017-02-19T06:19:01  *** d9b4bef9 has quit IRC
1152017-02-19T06:20:14  *** d9b4bef9 has joined #bitcoin-core-dev
1162017-02-19T06:20:54  *** harrymm has joined #bitcoin-core-dev
1172017-02-19T06:26:06  *** goksinen has joined #bitcoin-core-dev
1182017-02-19T06:27:19  *** aalex has joined #bitcoin-core-dev
1192017-02-19T06:30:18  *** goksinen has quit IRC
1202017-02-19T06:34:01  *** aalex has quit IRC
1212017-02-19T06:39:38  <achow101> cfields: I fixed the osx build. I finally fixed the fucking osx build. All I had to do was make a new base vm. it only took me the better part of the last 3-4 hours to figure out that vmbuilder has a bug and that I had a zombie vm screwing things up
1222017-02-19T06:53:08  *** jtimon has quit IRC
1232017-02-19T06:58:40  *** Victorsueca has quit IRC
1242017-02-19T07:20:20  *** goksinen has joined #bitcoin-core-dev
1252017-02-19T07:24:38  *** goksinen has quit IRC
1262017-02-19T08:08:02  *** Victorsueca has joined #bitcoin-core-dev
1272017-02-19T08:14:32  *** goksinen has joined #bitcoin-core-dev
1282017-02-19T08:18:58  *** goksinen has quit IRC
1292017-02-19T08:22:20  *** whphhg has joined #bitcoin-core-dev
1302017-02-19T08:23:44  *** Sosumi has joined #bitcoin-core-dev
1312017-02-19T08:44:27  *** Ylbam has joined #bitcoin-core-dev
1322017-02-19T08:57:59  *** murchandamus has quit IRC
1332017-02-19T09:00:44  *** murchandamus has joined #bitcoin-core-dev
1342017-02-19T09:04:12  *** murchandamus has quit IRC
1352017-02-19T09:06:18  *** pavel_ has joined #bitcoin-core-dev
1362017-02-19T09:07:04  *** murchandamus has joined #bitcoin-core-dev
1372017-02-19T09:08:47  *** goksinen has joined #bitcoin-core-dev
1382017-02-19T09:09:40  *** paveljanik has quit IRC
1392017-02-19T09:12:58  *** goksinen has quit IRC
1402017-02-19T09:13:38  *** lclc has quit IRC
1412017-02-19T10:01:34  *** goksinen has joined #bitcoin-core-dev
1422017-02-19T10:05:58  *** goksinen has quit IRC
1432017-02-19T10:11:02  *** lclc has joined #bitcoin-core-dev
1442017-02-19T10:17:05  *** AaronvanW has joined #bitcoin-core-dev
1452017-02-19T10:18:44  *** BitBully has joined #bitcoin-core-dev
1462017-02-19T10:21:21  *** BitBully has quit IRC
1472017-02-19T10:26:28  *** ChatSharp has joined #bitcoin-core-dev
1482017-02-19T10:29:31  *** ChatSharp has left #bitcoin-core-dev
1492017-02-19T11:00:27  *** chris200_ has joined #bitcoin-core-dev
1502017-02-19T11:02:58  *** chris2000 has quit IRC
1512017-02-19T11:10:09  *** Sosumi has quit IRC
1522017-02-19T11:10:26  *** Guyver2 has joined #bitcoin-core-dev
1532017-02-19T11:21:38  *** juscamarena has quit IRC
1542017-02-19T11:22:03  *** juscamarena has joined #bitcoin-core-dev
1552017-02-19T11:22:47  *** juscamarena has quit IRC
1562017-02-19T12:05:23  <wumpus> luke-jr: well I managed to screw up my base image, wouldn't be the first time, I do some optimizations to speed up the "upgrading operating system" step, I don't think there's any reason to dig deeper
1572017-02-19T12:05:41  <luke-jr> ah
1582017-02-19T12:05:55  <luke-jr> I just worry that the "rebuild base" solution is prone to malware getting in
1592017-02-19T12:06:04  <luke-jr> otoh, so is the updating step
1602017-02-19T12:06:05  <wumpus> if you feel like digging deeper I may be able to dig up my old base image and send it to you but I relaly don't have the time
1612017-02-19T12:06:38  <luke-jr> nah, probably not worth it all things considered
1622017-02-19T12:06:51  <luke-jr> if we weren't autoupdating, maybe, but we are
1632017-02-19T12:07:18  <wumpus> there's just no way to do this properly as long as we're not using a deterministically built OS for building
1642017-02-19T12:07:31  <luke-jr> right
1652017-02-19T12:09:07  <wumpus> I think it's more curious that making a new base image solved achow101 osx non-determinism - we have no reliance on the OS's build tools in that
1662017-02-19T12:09:13  <wumpus> at least I had three versions of gcc installed :)
1672017-02-19T12:09:30  <luke-jr> indeed
1682017-02-19T12:12:14  <wumpus> please just leave the "About Qt" link where it is, that's a common fixturefor all Qt programs and it's useful to be able to see what version of Qt is used for troubleshooting problems
1692017-02-19T12:12:49  <wumpus> there's no reason at all to remove it, it's not like we lack space in that menu and absolutely need to change something
1702017-02-19T12:14:01  <Arvidt> ) is  expired
1712017-02-19T12:14:02  <luke-jr> wumpus: the original reason I brought it up, was translators confusing it for "About Bitcoin-Qt". but that has since been resolved in other ways, so
1722017-02-19T12:14:38  <Arvidt> Wladimir J. van der Laan (Bitcoin Core binary release signing key) <laanwj@gmail.com> 01EA 5486 DE18 A882 D4C2  6845 90C8 019E 36C2 E964 is expired
1732017-02-19T12:14:58  <wumpus> no, it's been updated and bumped forward 2 years
1742017-02-19T12:15:22  <wumpus> try gpg --refresh-keys
1752017-02-19T12:15:56  * luke-jr wonders if this should be added to release announcements
1762017-02-19T12:16:33  <wumpus> that makes little sense, you could add arbitrary steps to release announcements to make the signature check out as ok
1772017-02-19T12:16:48  <wumpus> you can't trust any steps in it before you've verified the signature
1782017-02-19T12:16:51  <luke-jr> yes, but this one makes sense
1792017-02-19T12:17:10  <wumpus> it's not our job to explain people how to use gpg
1802017-02-19T12:18:57  *** fanquake has joined #bitcoin-core-dev
1812017-02-19T12:19:40  <wumpus> at least not in the release notes
1822017-02-19T12:20:10  <fanquake> I've still got the same issues even after re-building the base image. So I'm guessing I've somehow done that incorrectly..
1832017-02-19T12:20:29  <wumpus> I'm very surprised that the base image solved it for achow101
1842017-02-19T12:20:38  <wumpus> osx build hardly uses anything from the base image
1852017-02-19T12:21:07  <wumpus> we should check what the differences are
1862017-02-19T12:22:29  <fanquake> Looking at his new PR, it looks like the previous build was using the old version of Qt?
1872017-02-19T12:22:48  <fanquake> Actually, no.
1882017-02-19T12:23:31  <wumpus> I don't think so
1892017-02-19T12:25:26  <wumpus> normally would suggest "remove the gitian cache directories" but due to that switch, 0.14 uses new ones anyway
1902017-02-19T12:25:50  <wumpus> so it can't be using anything stale
1912017-02-19T12:26:10  <wumpus> your gitian-builder is up to date?
1922017-02-19T12:26:16  <fanquake> I might be missunderstanding, but why do the hashes for the same file change in his new PR?
1932017-02-19T12:26:24  <fanquake> Yes gitian-builder up to date.
1942017-02-19T12:26:48  <fanquake> Talking about something like native_mac_alias-1.1.0-f064d7cfd4c.tar.gz
1952017-02-19T12:27:58  <wumpus> curious. yes.
1962017-02-19T12:28:02  <fanquake> Same for cctools andbiplist.
1972017-02-19T12:28:12  <wumpus> not sure where those files come from. cfields?
1982017-02-19T12:28:31  <fanquake> That hasn't changed in depends recently as far as I remember. And those hashes don't even match the ones we have in depends anyways.
1992017-02-19T12:28:49  <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/7ff4a538a868...1f9e904f4556
2002017-02-19T12:28:50  <bitcoin-git> bitcoin/master 5c8fd50 Pieter Wuille: Avoid VLA in hash.h
2012017-02-19T12:28:50  <bitcoin-git> bitcoin/master 1f9e904 Wladimir J. van der Laan: Merge #9791: Avoid VLA in hash.h...
2022017-02-19T12:29:08  <bitcoin-git> [bitcoin] laanwj closed pull request #9791: Avoid VLA in hash.h (master...novla) https://github.com/bitcoin/bitcoin/pull/9791
2032017-02-19T12:29:13  <wumpus> maybe the gitian "tarballs are not deterministic" issue
2042017-02-19T12:29:31  <wumpus> eh GITHUB not gitian
2052017-02-19T12:29:53  <fanquake> except biplist comes from bitcucket
2062017-02-19T12:30:14  <fanquake> actually, from pypi.python.org
2072017-02-19T12:30:17  <wumpus> oh right, maybe bitbucket has that issue too, or has it now that github no longer has it, I don't know \
2082017-02-19T12:30:44  <wumpus> good catch though, that could very well be the reason
2092017-02-19T12:31:09  <wumpus> we'd need to find the old and new versions of those files and compare
2102017-02-19T12:31:24  <fanquake> They should still be in the /inputs folder
2112017-02-19T12:32:06  <wumpus> df26cbb976befd59ba20b73ee33676f22b6ed7aa1329e373307e0a21055f5a5a  ./cache/bitcoin-osx-0.13/x86_64-apple-darwin11/native_biplist/native_biplist-0.9-d766a97a608.tar.gz
2122017-02-19T12:32:06  <wumpus> ed6c2d2b2839164e592859f5eff62df7fedde9657c9e7a853720d0a768b8b756  ./cache/bitcoin-osx-0.14/x86_64-apple-darwin11/native_biplist/native_biplist-0.9-d766a97a608.tar.gz
2132017-02-19T12:32:26  <wumpus> those are mine. Both have different hash from achow101's new and old one
2142017-02-19T12:33:25  <wumpus> maybe they regenerate that file on every download?!
2152017-02-19T12:33:42  <fanquake> Surely we would have noticed if that we happening before now ?
2162017-02-19T12:33:59  <wumpus> for all the other downloaded dependencies we check the hash
2172017-02-19T12:34:07  <wumpus> apparently not for this one
2182017-02-19T12:34:42  <fanquake> https://github.com/bitcoin/bitcoin/blob/master/depends/packages/native_biplist.mk#L5
2192017-02-19T12:36:02  <fanquake> My cached biplist files don't even match yours or his..
2202017-02-19T12:36:05  *** str4d has joined #bitcoin-core-dev
2212017-02-19T12:37:07  <fanquake> Well, I even have a different file cached for 0.13 compared to you.
2222017-02-19T12:37:11  <fanquake> 490e9049e68ec8c7010be3cd19a6237e463d5115839c4cbccbb1dff1196129b4  native_biplist-0.9-1c39c8871c7.tar.gz
2232017-02-19T12:40:40  <wumpus> so my hypothesis of it changing every time isn't far off the mark, probably
2242017-02-19T12:40:53  <fanquake> Looking at my two asserts, my biplist files haven't changed between the two.
2252017-02-19T12:41:45  <fanquake> My other theory is something zlib related. Given it's new to our build.
2262017-02-19T12:42:03  <fanquake> It also doesn't compile using the depends system on OS X.
2272017-02-19T12:43:03  <wumpus> we should probably start by comparing the resulting files, it maybe some silly metadata thing too
2282017-02-19T12:43:53  <fanquake> Yes hopefully.
2292017-02-19T12:44:50  <fanquake> Something like #8373
2302017-02-19T12:44:52  <gribble> https://github.com/bitcoin/bitcoin/issues/8373 | Fix OSX non-deterministic dmg by theuni · Pull Request #8373 · bitcoin/bitcoin · GitHub
2312017-02-19T12:48:21  <wumpus> yes, like that one
2322017-02-19T12:54:26  *** AaronvanW has quit IRC
2332017-02-19T12:55:00  *** AaronvanW has joined #bitcoin-core-dev
2342017-02-19T12:57:19  *** Aaronvan_ has joined #bitcoin-core-dev
2352017-02-19T12:59:21  *** AaronvanW has quit IRC
2362017-02-19T13:05:39  <wumpus> fanquake: could you upload your  bitcoin-0.14.0-osx64.tar.gz somewhere?
2372017-02-19T13:06:22  <wumpus> I can't guarantee anything, I don't have the tooling to compare or analyze osx executables, but maybe I can find something obvious
2382017-02-19T13:14:24  <fanquake> wumpus probably. Sketchy internet at the moment. Will find a site.
2392017-02-19T13:16:57  <bitcoin-git> [bitcoin] kirit93 opened pull request #9798: Fix Issue #9775   (master...issue) https://github.com/bitcoin/bitcoin/pull/9798
2402017-02-19T13:19:50  <gmaxwell> uh. hey, so the release notes don't mention bumpfee.
2412017-02-19T13:20:08  <gmaxwell> thats like, a major feature, no? :P
2422017-02-19T13:21:14  <wumpus> yes
2432017-02-19T13:37:52  <gmaxwell> Relase notes make it sound like getinfo is hard-cut disabled in this version.
2442017-02-19T13:39:59  <gmaxwell> (I'm answering questions about the RC on reddit)
2452017-02-19T13:41:52  *** Aaronvan_ has quit IRC
2462017-02-19T13:47:59  *** Giszmo has joined #bitcoin-core-dev
2472017-02-19T13:56:51  *** Arvidt has left #bitcoin-core-dev
2482017-02-19T13:58:17  *** moli_ has quit IRC
2492017-02-19T14:11:05  *** wasi has quit IRC
2502017-02-19T14:11:24  <wumpus> well, it mentions that getinfo was deprecated, not that it was removed. But yeah I guess it could be clearer
2512017-02-19T14:11:29  *** wasi has joined #bitcoin-core-dev
2522017-02-19T14:13:24  <wumpus> I implemented getinfo client-side at some point (https://github.com/bitcoin/bitcoin/pull/8843) so that anyone using bitcoin-cli would hardly notice the command being removed from the server
2532017-02-19T14:14:08  <wumpus> but that only resulted in a big argument, so I gave up on it
2542017-02-19T14:16:11  <luke-jr> not the first time someone confused deprecated to mean removed
2552017-02-19T14:17:29  <wumpus> on the dev side getinfo was already deprecated for years, iti's just that this was never communicated on the RPC interface
2562017-02-19T14:18:31  *** fanquake has quit IRC
2572017-02-19T14:23:04  <achow101> wumpus: fanquake: I did delete gitian-builder and redownload it before making the base vm, so maybe that could be part of why the build was fixed, although I don't see why it should
2582017-02-19T14:24:16  <wumpus> achow101: yes, it's no longer possible to isolate what the cause of the problem was
2592017-02-19T14:24:40  <wumpus> although the same is not working for fan
2602017-02-19T14:24:45  <wumpus> fanquake
2612017-02-19T14:31:26  *** cdecker has quit IRC
2622017-02-19T14:31:33  <gmaxwell> I wonder if the next step there shouldn't be to disable getinfo but allow a config option to reenable it.  Another half measure would be to make the error field there always preface with a warning.
2632017-02-19T14:31:53  *** cdecker has joined #bitcoin-core-dev
2642017-02-19T14:51:03  <wumpus> I think the next major release we should just get rid of it
2652017-02-19T14:51:08  <wumpus> we've delayed that enough
2662017-02-19T14:51:44  *** chjj has joined #bitcoin-core-dev
2672017-02-19T14:52:09  <wumpus> announcing it in the release notes in strong language was a good start
2682017-02-19T14:52:27  <wumpus> and we provide *exactly* a table of how to get the information
2692017-02-19T14:54:41  <wumpus> no need to draw this out like the account deprectation, where it's not 100% clear what the replacement for some use cases
2702017-02-19T15:01:18  <da2ce7> if you decide now to remove it in the next version, state. "in version 0.15,  getinfo will be removed from bitcoin-core". :)
2712017-02-19T15:02:20  <wumpus> yes, would make sense to add that
2722017-02-19T15:02:27  <wumpus> also clears up that it is not removed yet
2732017-02-19T15:04:00  <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/1f9e904f4556...390a39bb5cf4
2742017-02-19T15:04:00  <bitcoin-git> bitcoin/master eb49101 Wladimir J. van der Laan: doc: Update manpages for master...
2752017-02-19T15:04:01  <bitcoin-git> bitcoin/master 390a39b Wladimir J. van der Laan: Merge #9795: doc: Update manpages for master (laanwj)...
2762017-02-19T15:04:18  <bitcoin-git> [bitcoin] laanwj closed pull request #9795: doc: Update manpages for master (laanwj) (master...Mf1602-docManMaster) https://github.com/bitcoin/bitcoin/pull/9795
2772017-02-19T15:05:52  *** AaronvanW has joined #bitcoin-core-dev
2782017-02-19T15:05:52  *** AaronvanW has joined #bitcoin-core-dev
2792017-02-19T15:22:36  <gmaxwell> wumpus: the problem with hard cuts like that is predictable people will just not upgrade their nodes when their software is incompatible, and in doing so harm the network.
2802017-02-19T15:22:50  <gmaxwell> especially since its super easy to just have never noticed a release note.
2812017-02-19T15:23:26  <gmaxwell> (not really trying to argue it out with you now, just defending why I'd even suggest such a thing)
2822017-02-19T15:45:49  *** asoltys has quit IRC
2832017-02-19T15:48:50  *** wasi has quit IRC
2842017-02-19T15:49:11  *** wasi has joined #bitcoin-core-dev
2852017-02-19T16:11:02  <achow101> wumpus: it's still non-deterministic :( I just ran gitian again and got my original results
2862017-02-19T16:38:58  *** harrymm has quit IRC
2872017-02-19T16:39:27  *** chjj has quit IRC
2882017-02-19T16:39:41  *** chjj has joined #bitcoin-core-dev
2892017-02-19T16:50:55  *** chjj has quit IRC
2902017-02-19T16:51:07  *** chjj has joined #bitcoin-core-dev
2912017-02-19T16:54:02  *** harrymm has joined #bitcoin-core-dev
2922017-02-19T16:58:22  *** afk11_ has joined #bitcoin-core-dev
2932017-02-19T17:00:33  *** afk11_ has quit IRC
2942017-02-19T17:01:14  *** afk11_ has joined #bitcoin-core-dev
2952017-02-19T17:01:16  *** afk11_ has quit IRC
2962017-02-19T17:02:47  *** afk11_ has joined #bitcoin-core-dev
2972017-02-19T17:04:39  *** afk11_ has quit IRC
2982017-02-19T17:05:13  *** afk11_ has joined #bitcoin-core-dev
2992017-02-19T17:05:29  *** afk11_ has quit IRC
3002017-02-19T17:05:55  *** afk11_ has joined #bitcoin-core-dev
3012017-02-19T17:06:20  *** afk11_ has quit IRC
3022017-02-19T17:06:35  *** afk11_ has joined #bitcoin-core-dev
3032017-02-19T17:07:02  *** d9b4bef9 has quit IRC
3042017-02-19T17:08:07  *** d9b4bef9 has joined #bitcoin-core-dev
3052017-02-19T17:11:52  *** afk11_ is now known as afk11
3062017-02-19T17:21:39  <gmaxwell> instagibbs: you're double counted in the contributor list
3072017-02-19T17:31:52  <bitcoin-git> [bitcoin] gubatron opened pull request #9801: Removed redundant parameter from mempool.PrioritiseTransaction (master...refactor-mempool-prioritisetx) https://github.com/bitcoin/bitcoin/pull/9801
3082017-02-19T17:34:34  *** Evel-Knievel has quit IRC
3092017-02-19T17:49:15  *** Evel-Knievel has joined #bitcoin-core-dev
3102017-02-19T17:58:55  *** moli_ has joined #bitcoin-core-dev
3112017-02-19T17:59:37  *** jtimon has joined #bitcoin-core-dev
3122017-02-19T18:04:04  <bitcoin-git> [bitcoin] dooglus opened pull request #9803: Fix typo in release notes. (0.14...patch-5) https://github.com/bitcoin/bitcoin/pull/9803
3132017-02-19T18:08:40  *** Evel-Knievel has quit IRC
3142017-02-19T18:21:58  *** moli_ has quit IRC
3152017-02-19T18:23:35  *** moli_ has joined #bitcoin-core-dev
3162017-02-19T18:25:40  *** lclc has quit IRC
3172017-02-19T18:28:47  *** Evel-Knievel has joined #bitcoin-core-dev
3182017-02-19T19:13:05  *** lclc has joined #bitcoin-core-dev
3192017-02-19T19:27:37  *** isle2983 has joined #bitcoin-core-dev
3202017-02-19T19:46:06  <bitcoin-git> [bitcoin] JeremyRubin opened pull request #9804: Fixes subscript 0 (&var[0]) where should use (var.data()) instead. (master...fix-subscript-0) https://github.com/bitcoin/bitcoin/pull/9804
3212017-02-19T19:48:51  *** bsm117532 has quit IRC
3222017-02-19T19:53:21  *** paveljanik has joined #bitcoin-core-dev
3232017-02-19T19:55:31  <achow101> cfields: I now have what appears to be a consistently inconsistent gitian build for osx. Each time I build it, it alternates between the hashes that everyone else has, and the hashes that fanquake and I have
3242017-02-19T19:56:04  <sipa> "consistently inconsistent"
3252017-02-19T19:57:36  *** chjj has quit IRC
3262017-02-19T20:11:04  <achow101> cfields: I put the two different assert files in different branches: https://github.com/achow101/gitian.sigs/tree/0.14.0rc1-match and https://github.com/achow101/gitian.sigs/tree/0.14.0rc1-mismatch the only difference between the two are the output files. everything else matches according to diff
3272017-02-19T20:36:49  *** harrymm has quit IRC
3282017-02-19T20:37:43  *** afk11 has quit IRC
3292017-02-19T20:38:13  *** afk11 has joined #bitcoin-core-dev
3302017-02-19T20:40:54  *** afk11 has quit IRC
3312017-02-19T20:42:15  *** afk11 has joined #bitcoin-core-dev
3322017-02-19T20:56:56  *** harrymm has joined #bitcoin-core-dev
3332017-02-19T21:13:07  <bitcoin-git> [bitcoin] petertodd opened pull request #9805: Add seed.btc.petertodd.org to mainnet DNS seeds (master...2017-02-add-pt-mainnet-seed) https://github.com/bitcoin/bitcoin/pull/9805
3342017-02-19T21:29:32  *** tunafizz has quit IRC
3352017-02-19T21:32:25  *** boab has joined #bitcoin-core-dev
3362017-02-19T21:33:29  <boab> Looking for readme on upgrade of core from 0.8.x to 0.10.x Help?
3372017-02-19T21:34:54  <gmaxwell> uh? why run such an old version as 0.10? I assume everyone has long forgotten about it, it's old and insecure.
3382017-02-19T21:35:31  <boab> Yep, good ppoint. My main mission is to get off of 0.8.x ... and how-to's please?
3392017-02-19T21:37:18  <gmaxwell> the blockchain files and wallets are all compatible. shut down, backup your wallet (for good measure), install 0.13.2.  start it.
3402017-02-19T21:37:46  <boab> Fantastic...that's all the assurance I needed. Just did not want to trash something in the process.
3412017-02-19T21:39:42  <sipa> make a backup of your wallet after shutting down 0.8 if you want to be sure
3422017-02-19T21:39:53  <sipa> (which you should have anyway)
3432017-02-19T21:42:31  <boab> Thanks mate. I used the [backup wallet] option from within 0.8 and have stored off site.
3442017-02-19T21:42:57  *** lclc has quit IRC
3452017-02-19T21:43:12  <luke-jr> need to backup the wallet before shutting down..
3462017-02-19T21:43:55  <boab> ?? I think that's right: I was running 0.8, used the GUI option to create a backup, and then have shut 0.8 down.
3472017-02-19T21:44:00  <luke-jr> sounds good
3482017-02-19T21:44:03  <sipa> sounds good
3492017-02-19T21:44:19  <boab> fingers crossed...about to fire up new core now...
3502017-02-19T21:46:42  <boab> Rock n roll! v013.2 seems to have read the wallet and blockchain and is happily syncing right now. Thanks for your hand-holding...much appreciated.
3512017-02-19T21:47:09  <gmaxwell> Great! congrats on joining the modern era!
3522017-02-19T21:47:47  <boab> heheh...respkt ur elders?
3532017-02-19T21:50:54  <sipa> boab: also, 0.14.0 will be released in a few weeks likely
3542017-02-19T21:53:32  *** boab has quit IRC
3552017-02-19T22:03:06  *** To7 has joined #bitcoin-core-dev
3562017-02-19T22:04:10  *** str4d has quit IRC
3572017-02-19T22:16:20  *** Guyver2 has quit IRC
3582017-02-19T22:30:03  *** grubles has joined #bitcoin-core-dev
3592017-02-19T23:03:31  *** cdecker has quit IRC
3602017-02-19T23:06:35  *** cdecker has joined #bitcoin-core-dev
3612017-02-19T23:21:27  *** isle2983 has quit IRC
3622017-02-19T23:33:10  *** isle2983 has joined #bitcoin-core-dev
3632017-02-19T23:48:18  *** waxwing has quit IRC