12016-06-22T00:03:25  *** xiangfu has joined #bitcoin-core-dev
  22016-06-22T00:10:07  *** raedah has quit IRC
  32016-06-22T00:11:18  *** raedah has joined #bitcoin-core-dev
  42016-06-22T00:14:17  *** alpalp has joined #bitcoin-core-dev
  52016-06-22T00:22:04  *** anchow101 has quit IRC
  62016-06-22T00:23:24  *** shesek has joined #bitcoin-core-dev
  72016-06-22T00:35:08  *** anchow101 has joined #bitcoin-core-dev
  82016-06-22T00:53:32  *** anchow101 has quit IRC
  92016-06-22T00:59:44  *** jl2012 has joined #bitcoin-core-dev
 102016-06-22T01:00:22  *** belcher has quit IRC
 112016-06-22T01:05:44  *** Ylbam has quit IRC
 122016-06-22T01:14:33  *** fengling has joined #bitcoin-core-dev
 132016-06-22T02:11:26  <jl2012> I talked to wangchun. F2pool has stopped setting the csv bit.
 142016-06-22T02:29:36  <phantomcircuit> jl2012: i dont think it matters the soft fork is locked in either way
 152016-06-22T02:29:46  <phantomcircuit> (i could be wrong here but im prettty sure im not)
 162016-06-22T02:30:32  *** alpalp has quit IRC
 172016-06-22T02:30:51  <gmaxwell> phantomcircuit: it doesn't.
 182016-06-22T02:31:01  *** achow101 has quit IRC
 192016-06-22T02:40:19  <btcdrak> jl2012: need to ask antpool to unset it also.
 202016-06-22T02:46:21  *** fanquake has joined #bitcoin-core-dev
 212016-06-22T02:56:47  *** go1111111 has quit IRC
 222016-06-22T02:57:02  *** raedah has quit IRC
 232016-06-22T02:57:33  <instagibbs> phantomcircuit, there is just some concern of blocks having bits set that a client wont understand
 242016-06-22T02:57:46  <instagibbs> alerts for no reason(more than we already have now)
 252016-06-22T02:58:05  *** raedah has joined #bitcoin-core-dev
 262016-06-22T03:01:33  *** thereum has joined #bitcoin-core-dev
 272016-06-22T03:09:11  *** TomMc has quit IRC
 282016-06-22T03:10:16  *** go1111111 has joined #bitcoin-core-dev
 292016-06-22T03:14:36  <btcdrak> yes. please see latest article on website
 302016-06-22T03:26:36  *** cjcj has quit IRC
 312016-06-22T04:05:53  *** thereum has quit IRC
 322016-06-22T04:58:46  *** fengling has quit IRC
 332016-06-22T05:17:58  *** paveljanik has quit IRC
 342016-06-22T05:21:26  *** Giszmo has quit IRC
 352016-06-22T05:51:16  *** ratoder has quit IRC
 362016-06-22T05:52:18  *** ratoder has joined #bitcoin-core-dev
 372016-06-22T06:00:48  *** fengling has joined #bitcoin-core-dev
 382016-06-22T06:46:50  *** gribble has quit IRC
 392016-06-22T06:46:54  *** jl2012_ has joined #bitcoin-core-dev
 402016-06-22T06:49:10  <GitHub53> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/8ccdac1f5f77...961893f26e5c
 412016-06-22T06:49:11  <GitHub53> bitcoin/master 3775ff9 Pieter Wuille: Enable mempool consistency checks in unit tests
 422016-06-22T06:49:11  <GitHub53> bitcoin/master 961893f Wladimir J. van der Laan: Merge #8222: Enable mempool consistency checks in unit tests...
 432016-06-22T06:49:15  <GitHub147> [bitcoin] laanwj closed pull request #8222: Enable mempool consistency checks in unit tests (master...unittestmempool) https://github.com/bitcoin/bitcoin/pull/8222
 442016-06-22T06:49:46  *** gmaxwell_ has joined #bitcoin-core-dev
 452016-06-22T06:49:51  *** Eliel_ has joined #bitcoin-core-dev
 462016-06-22T06:50:01  *** kanzure_ has joined #bitcoin-core-dev
 472016-06-22T06:50:14  *** Ylbam has joined #bitcoin-core-dev
 482016-06-22T06:50:35  <GitHub115> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/961893f26e5c...760a6c7cb2ea
 492016-06-22T06:50:35  <GitHub115> bitcoin/master b3e1348 Jonas Schnelli: [Qt] fix a bug where the SplashScreen will not be hidden during startup
 502016-06-22T06:50:36  <GitHub115> bitcoin/master 760a6c7 Wladimir J. van der Laan: Merge #8231: [Qt] fix a bug where the SplashScreen will not be hidden during startup...
 512016-06-22T06:50:39  <GitHub92> [bitcoin] laanwj closed pull request #8231: [Qt] fix a bug where the SplashScreen will not be hidden during startup (master...2016/06/qt_min_fix) https://github.com/bitcoin/bitcoin/pull/8231
 522016-06-22T06:52:00  *** Anduck_ has joined #bitcoin-core-dev
 532016-06-22T06:52:24  <GitHub180> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/760a6c7cb2ea...9e45ef1ef031
 542016-06-22T06:52:25  <GitHub180> bitcoin/master 4cbe05b Wladimir J. van der Laan: qt: Periodic transifex update...
 552016-06-22T06:52:25  <GitHub180> bitcoin/master 9e45ef1 Wladimir J. van der Laan: Merge #8234: qt: Periodic transifex update...
 562016-06-22T06:52:34  <GitHub197> [bitcoin] laanwj closed pull request #8234: qt: Periodic transifex update (master...2016_06_transifex_update) https://github.com/bitcoin/bitcoin/pull/8234
 572016-06-22T07:00:29  *** gribble has joined #bitcoin-core-dev
 582016-06-22T07:02:49  *** fanquake has joined #bitcoin-core-dev
 592016-06-22T07:04:15  *** spudowiar1 has joined #bitcoin-core-dev
 602016-06-22T07:04:44  *** jl2012 has quit IRC
 612016-06-22T07:04:45  *** owowo has quit IRC
 622016-06-22T07:04:45  *** spudowiar has quit IRC
 632016-06-22T07:04:45  *** dgenr8 has quit IRC
 642016-06-22T07:04:46  *** kanzure has quit IRC
 652016-06-22T07:04:46  *** Madars has quit IRC
 662016-06-22T07:04:46  *** e4xit has quit IRC
 672016-06-22T07:04:47  *** Eliel has quit IRC
 682016-06-22T07:04:47  *** Anduck has quit IRC
 692016-06-22T07:04:50  *** gmaxwell has quit IRC
 702016-06-22T07:04:51  *** jl2012_ is now known as jl2012
 712016-06-22T07:05:37  *** dgenr8 has joined #bitcoin-core-dev
 722016-06-22T07:14:47  *** e4xit has joined #bitcoin-core-dev
 732016-06-22T07:15:35  *** owowo has joined #bitcoin-core-dev
 742016-06-22T07:19:38  *** gmaxwell_ has quit IRC
 752016-06-22T07:19:38  *** gmaxwell_ has joined #bitcoin-core-dev
 762016-06-22T07:19:56  *** gmaxwell_ is now known as gmaxwell
 772016-06-22T07:21:28  *** MarcoFalke has joined #bitcoin-core-dev
 782016-06-22T07:28:38  <GitHub34> [bitcoin] MarcoFalke opened pull request #8236: [doc] 0.12.2: prepare release notes (0.12...Mf1606-docReleaseNotes) https://github.com/bitcoin/bitcoin/pull/8236
 792016-06-22T07:44:06  *** fengling has quit IRC
 802016-06-22T07:47:31  <fanquake> wumpus Some issues that can be closed #7861 #7873 #7866
 812016-06-22T07:47:48  <fanquake> Also #6701 should have been closed by #7667
 822016-06-22T07:48:41  <fanquake> Possibly also #6702
 832016-06-22T07:49:20  *** xiangfu has quit IRC
 842016-06-22T07:50:49  *** laurentmt has joined #bitcoin-core-dev
 852016-06-22T07:51:08  *** laurentmt has quit IRC
 862016-06-22T07:52:00  *** Guyver2 has joined #bitcoin-core-dev
 872016-06-22T07:52:20  <fanquake> #7872 can also be closed. Not sure why this account has opened so many random/meaningless issues.
 882016-06-22T08:02:55  <MarcoFalke> done
 892016-06-22T08:05:16  *** fengling has joined #bitcoin-core-dev
 902016-06-22T08:10:07  *** JackH has joined #bitcoin-core-dev
 912016-06-22T08:13:28  <gmaxwell> Anyone have exact IsSuperMajority heights for BIP30/65/66 on mainnet and testnet handy, by any chance?
 922016-06-22T08:14:35  <btcdrak> gmaxwell BIP66 block 363724 according to https://bitcoin.stackexchange.com/questions/38436/when-did-bip66-switch-from-activation-to-enforcement
 932016-06-22T08:18:49  *** ratoder has quit IRC
 942016-06-22T08:21:09  <btcdrak> gmaxwell: BIP65 was activated on block #388380
 952016-06-22T08:22:12  *** Guyver2 has quit IRC
 962016-06-22T08:22:21  <btcdrak> luke-jr: maybe we should update the BIPs with activation blocks when they activate
 972016-06-22T08:22:32  *** ratoder has joined #bitcoin-core-dev
 982016-06-22T08:27:06  *** fengling has quit IRC
 992016-06-22T08:32:38  <btcdrak> gmaxwell: do you mean BIP34? according to the BIP text "Block number 227,835 (timestamp 2013-03-24 15:49:13 GMT) was the last version 1 block."
1002016-06-22T08:47:45  *** Madars has joined #bitcoin-core-dev
1012016-06-22T08:48:16  *** fengling has joined #bitcoin-core-dev
1022016-06-22T08:58:51  *** Evel-Knievel has quit IRC
1032016-06-22T08:59:33  *** Evel-Knievel has joined #bitcoin-core-dev
1042016-06-22T09:02:06  *** fengling has quit IRC
1052016-06-22T09:02:44  *** rxatxoder has joined #bitcoin-core-dev
1062016-06-22T09:05:11  <gmaxwell> uhh. is reindex broken on master for anyone else?
1072016-06-22T09:06:06  <gmaxwell> oh it's not broken.
1082016-06-22T09:06:14  <gmaxwell> it just looks funny now that it scans headers first.
1092016-06-22T09:06:20  <gmaxwell> hm. we might get bug reports on that.
1102016-06-22T09:07:12  *** rxatxoder has quit IRC
1112016-06-22T09:08:16  <wumpus> those mrCertified issues are crazy, didn't notice them before, thanks for closing fanquake/MarcoFalke
1122016-06-22T09:18:00  <sipa> btcdrak: bips.md has more info
1132016-06-22T09:22:31  *** pedrobranco has joined #bitcoin-core-dev
1142016-06-22T09:31:14  <GitHub199> [bitcoin] laanwj pushed 1 new commit to 0.11: https://github.com/bitcoin/bitcoin/commit/0cd4fb6570f67d40891673bc8c41e473b9753c63
1152016-06-22T09:31:14  <GitHub199> bitcoin/0.11 0cd4fb6 Wladimir J. van der Laan: qt: Final translation update on 0.11 branch...
1162016-06-22T09:32:47  <gmaxwell> so the first point where     if (block.nVersion >= 2 && IsSuperMajority(2, pindexPrev, consensusParams.nMajorityEnforceBlockUpgrade, consensusParams))
1172016-06-22T09:35:02  <gmaxwell> is true is 224413, which seems to suggest that the BIP34 height in the chainparams is wrong?
1182016-06-22T09:37:01  <gmaxwell> nevermind. activated vs enforced.
1192016-06-22T09:37:37  <wumpus> phew
1202016-06-22T09:38:11  <sipa> gmaxwell: what looks funny about it?
1212016-06-22T09:39:23  <sipa> gmaxwell: the chainparams value is the first point where it activated and never went to non-activated anymore
1222016-06-22T09:40:53  <wumpus> maybe add a comment to prevent people panicking from this again in the future :)
1232016-06-22T09:41:07  <gmaxwell> I will.
1242016-06-22T09:41:49  <gmaxwell> I was in the process of making a patch to remove all the IsSuperMajority code, and replace with simple height checks.
1252016-06-22T09:52:53  *** pedrobranco has quit IRC
1262016-06-22T09:53:08  *** pedrobranco has joined #bitcoin-core-dev
1272016-06-22T09:54:55  <gmaxwell> I think it's weird that we end up with network connections while reindexing.
1282016-06-22T09:59:43  <wumpus> outgoing or incoming?
1292016-06-22T10:00:20  <gmaxwell> outgoing.
1302016-06-22T10:00:23  <wumpus> in principle the network code is simply running while reindexing, it just doesn't request blocks nor transactions
1312016-06-22T10:00:41  <wumpus> I don't think that's necessarily wrong
1322016-06-22T10:01:08  <gmaxwell> I'm probably only really noticing because I have debugging turned up and the invs are filling up my logs.
1332016-06-22T10:01:24  <gmaxwell> Is it useful to have connections up while reindexing?
1342016-06-22T10:01:40  <sipa> i guess it may make sense for addr relay
1352016-06-22T10:01:41  <wumpus> no, but it also doesn't hurt, there doesn't need to be a strong coupling between network code and chain handling code
1362016-06-22T10:02:11  <sipa> we could extend the dont-request-blocks rule to dont-request-transactions too
1372016-06-22T10:02:28  <wumpus> I think that's already the case?
1382016-06-22T10:02:35  <gmaxwell> doesn't appear to be requesting any.
1392016-06-22T10:02:40  <gmaxwell> The negatives I can think of: wastes network resources, might defeat "is it working" monitoring. Otherwise, I agree.
1402016-06-22T10:03:14  <wumpus> there is also a paralellism aspect: there will already be connections to request blocks on when the reindexing finished
1412016-06-22T10:03:48  <gmaxwell> Thats a point.
1422016-06-22T10:03:59  <wumpus> in any case there doesn't seem to be a strong reason to special-case this, so let's not
1432016-06-22T10:05:10  <wumpus> the amount of network resources 'wasted' during reindex must be negible compared to a running node, and if you really care about (say when benchmarking) that and want to do a pure reindex, pass -connect=0 and disable listening...
1442016-06-22T10:05:15  <sipa> wumpus: unfortunately, there is a bug around that
1452016-06-22T10:05:25  <sipa> wumpus: we don't start requesting headers when reindex finishes
1462016-06-22T10:05:47  <sipa> so only when an inv for a new block arrives, actual sync continues after a reindex
1472016-06-22T10:05:56  <gmaxwell> We should probably release note that reindex may look inactive for a period of time at the beginning.
1482016-06-22T10:05:57  <wumpus> that seems wrong
1492016-06-22T10:06:05  <sipa> we should fix it
1502016-06-22T10:06:16  <sipa> i'll file an issue if there is none already
1512016-06-22T10:06:16  <gmaxwell> indeed, but after 3 hours, an extra block delay is not the end of the world. :)
1522016-06-22T10:07:00  <wumpus> on the other hand reindex is just a tool to fix for broken databases, which unfortunately happen much more than they should, but it shouldn't be something people are doing day in day out
1532016-06-22T10:07:26  <wumpus> so I suppose the +/- 10 minute delay is indeed not the end of the world
1542016-06-22T10:07:41  <gmaxwell> I think that at some not far future version we should rename reindex to work around bad instructions on the internet that have people reindexing every time they see a shadow.
1552016-06-22T10:07:48  <wumpus> nah
1562016-06-22T10:08:14  <sipa> -really-reindex
1572016-06-22T10:08:25  <gmaxwell> --rebuild-state
1582016-06-22T10:08:28  <sipa> well we do have -reindex-chainstate now
1592016-06-22T10:08:43  <sipa> but -reindex itself is still useful when your block files are corrupted
1602016-06-22T10:08:54  <wumpus> for better or worse, there are many legitimate issues solved by a reindex, seems almost sadistic to break all kinds of well-meant guides on the internet. Even if it results in slightly more reindexes besing run all in all.
1612016-06-22T10:09:08  <sipa> of course
1622016-06-22T10:09:15  <gmaxwell> not yet, but in some near future where awesome improvements reduce the use for ever running it, of course.
1632016-06-22T10:09:22  <sipa> same with rescan
1642016-06-22T10:09:31  <wumpus> I'm not a fan of the rename-an-option-to-prevent-people-from-doing-it school if the option isn't a danger of monetary loss
1652016-06-22T10:09:45  <sipa> at least the very common advice to fix random problems with a -rescan has died out
1662016-06-22T10:09:52  <wumpus> if there was a purge-privatekeys option for the wallet I would want to rename it eveery release :p
1672016-06-22T10:10:04  <sipa> haha
1682016-06-22T10:10:12  <gmaxwell> okay. I won't argue for it, I was only motivated by the fact that many of the old reasons are gone.
1692016-06-22T10:10:12  <sipa> --steal-my-coins
1702016-06-22T10:10:37  <sipa> gmaxwell: do you have evidence of -reindex commonly being suggested for the wrong reasons?
1712016-06-22T10:10:46  <gmaxwell> E.g. someone in #bitcoin two days ago was exasperated while on day three of a reindex on an rpi3 that was totally unneeded.
1722016-06-22T10:11:24  <wumpus> the utxo backup fallback woud still be a good idea, we should aim to get it into 0.14
1732016-06-22T10:11:25  <gmaxwell> In that case, it was listed as a mandatory step for moving chainstate from x86 to rpi, suggested due non-portability that no longer exists.
1742016-06-22T10:11:31  <sipa> wumpus: agree
1752016-06-22T10:12:05  <wumpus> gmaxwell: was that a guide on the wiki? if so it'd be easy to fix
1762016-06-22T10:12:14  <wumpus> if not, we should probably contact the author
1772016-06-22T10:13:30  <gmaxwell> (also, for pruning to someday become a default option, we must reduce the incidence of reindex to ~0)
1782016-06-22T10:13:35  <wumpus> do you have a link to that guide?
1792016-06-22T10:17:01  <gmaxwell> I thought I asked him, but I didn't. I asked now.
1802016-06-22T10:18:27  <GitHub189> [bitcoin] fanquake opened pull request #8238: [WIP][depends] ZeroMQ 4.1.5 && ZMQ on Windows (master...depends-zeromq-4-1-5) https://github.com/bitcoin/bitcoin/pull/8238
1812016-06-22T10:27:16  <fanquake> Was #6702 solved by #7667 ?
1822016-06-22T10:29:26  <fanquake> Can probably close #7724, sipa replied and it seems that the issue is user hardware.
1832016-06-22T10:34:58  <fanquake> #7735 Isn't going to happen any time soon, and can probably be closed.
1842016-06-22T10:37:55  <fanquake> #7979 can be closed.
1852016-06-22T10:44:33  <wumpus> thanks, done
1862016-06-22T10:50:07  <fanquake> #7725 Looks closable, seems like the issue was related directory permissions.
1872016-06-22T10:51:31  *** ratoder has quit IRC
1882016-06-22T10:52:09  <fanquake> #7733 Could be closed as wontfix, as documentation was linked to elsewhere. Unless we need to follow up and add links to the README or something?
1892016-06-22T10:54:52  *** ratoder has joined #bitcoin-core-dev
1902016-06-22T10:55:33  <wumpus> agree
1912016-06-22T10:55:51  <sipa> fanquake: thanks a lot for going through those issues!
1922016-06-22T10:56:12  <wumpus> https://github.com/bitcoin/bitcoin/issues/4095 is a qt issue, and a curious one at that, anyone ever managed to reproduce this?
1932016-06-22T10:56:24  <wumpus> yes, thanks!
1942016-06-22T10:57:00  *** ratoder has quit IRC
1952016-06-22T10:57:38  *** ratoder has joined #bitcoin-core-dev
1962016-06-22T11:02:06  <fanquake> #5758 Seems to have gone stale, no followup replies.
1972016-06-22T11:02:11  *** Sosumi has joined #bitcoin-core-dev
1982016-06-22T11:02:46  <sipa> fanquake: closed 1.5 years ago?
1992016-06-22T11:02:55  <wumpus> wrong number I think
2002016-06-22T11:03:06  <sipa> we need a checksum digit in PR numbers
2012016-06-22T11:03:11  <fanquake> Sorry, #5785
2022016-06-22T11:03:12  <wumpus> <:
2032016-06-22T11:04:47  <sipa> ack on merging compact blocks?
2042016-06-22T11:05:32  <fanquake> #6472 && #7341 can probably be closed now that we've switched to Qt5.6.1
2052016-06-22T11:05:40  *** ratoder has quit IRC
2062016-06-22T11:06:06  *** ratoder has joined #bitcoin-core-dev
2072016-06-22T11:09:09  <fanquake> Can close #7834 - Changes to the macports portfile have been made upstream, and  parallel builds are working ok normally.
2082016-06-22T11:14:53  <btcdrak> sipa: ack.
2092016-06-22T11:21:32  *** cryptapus has joined #bitcoin-core-dev
2102016-06-22T11:25:41  *** cryptapus has quit IRC
2112016-06-22T11:26:11  *** cryptapus has joined #bitcoin-core-dev
2122016-06-22T11:30:30  *** ratoder has quit IRC
2132016-06-22T11:30:53  *** ratoder has joined #bitcoin-core-dev
2142016-06-22T11:38:38  *** Anduck_ is now known as Anduck
2152016-06-22T11:44:14  <wumpus> I've been testing compact blocks on one of my ARM nodes for quite some time, no issues
2162016-06-22T11:46:43  *** fengling has joined #bitcoin-core-dev
2172016-06-22T11:51:46  *** Sosumi has quit IRC
2182016-06-22T11:52:26  *** fengling has quit IRC
2192016-06-22T11:56:32  *** robs has joined #bitcoin-core-dev
2202016-06-22T12:11:22  <instagibbs> I see no reason to block merging. Only nits/minor improvements left which can be taken on later.
2212016-06-22T12:20:08  <wumpus> agree
2222016-06-22T12:20:15  <wumpus> okay, hold on tight
2232016-06-22T12:20:34  * btcdrak drum roll
2242016-06-22T12:25:12  *** Guyver2 has joined #bitcoin-core-dev
2252016-06-22T12:29:03  *** kanzure_ is now known as kanzure
2262016-06-22T12:31:04  <GitHub185> [bitcoin] laanwj pushed 19 new commits to master: https://github.com/bitcoin/bitcoin/compare/9e45ef1ef031...e9d76a161d30
2272016-06-22T12:31:05  <GitHub185> bitcoin/master 96806c3 Pieter Wuille: Stop trimming when mapTx is empty
2282016-06-22T12:31:05  <GitHub185> bitcoin/master 7c29ec9 Matt Corallo: If AcceptBlockHeader returns true, pindex will be set....
2292016-06-22T12:31:06  <GitHub185> bitcoin/master cbda71c Matt Corallo: Move context-required checks from CheckBlockHeader to Contextual...
2302016-06-22T12:31:13  <GitHub25> [bitcoin] laanwj closed pull request #8068: Compact Blocks (master...udp) https://github.com/bitcoin/bitcoin/pull/8068
2312016-06-22T12:31:19  <wumpus> ^^
2322016-06-22T12:31:24  <fanquake> Woo
2332016-06-22T12:31:29  <instagibbs> \o/
2342016-06-22T12:32:00  <btcdrak> oh man
2352016-06-22T12:32:04  <btcdrak> yis!
2362016-06-22T12:41:43  *** Guyver2 has quit IRC
2372016-06-22T12:42:30  *** shangzhou has joined #bitcoin-core-dev
2382016-06-22T12:42:44  <shangzhou> wow
2392016-06-22T12:51:44  <GitHub170> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/e9d76a161d30...9f1807af2422
2402016-06-22T12:51:45  <GitHub170> bitcoin/master b7bf037 Wladimir J. van der Laan: doc: Mention ARM executables in release process...
2412016-06-22T12:51:45  <GitHub170> bitcoin/master 05f64c9 Wladimir J. van der Laan: doc: Mention Linux ARM builds in release notes
2422016-06-22T12:51:46  <GitHub170> bitcoin/master 06f40ef Wladimir J. van der Laan: depends: Mention aarch64 as common cross-compile target
2432016-06-22T12:51:47  <GitHub183> [bitcoin] laanwj closed pull request #8233: Mention Linux ARM executables in release process and notes (master...2016_06_release_process_arm) https://github.com/bitcoin/bitcoin/pull/8233
2442016-06-22T12:58:20  <wumpus> is there any way to see (in the GUI or through RPC) if a wallet is BIP32?
2452016-06-22T13:15:56  *** Chris_Stewart_5 has joined #bitcoin-core-dev
2462016-06-22T13:23:37  *** cryptapus_ has joined #bitcoin-core-dev
2472016-06-22T13:23:54  *** cryptapus_ has joined #bitcoin-core-dev
2482016-06-22T13:27:22  *** cryptapus has quit IRC
2492016-06-22T13:39:03  *** TomMc has joined #bitcoin-core-dev
2502016-06-22T13:49:17  <sipa> i'm rebasing segwit on top of compact blocks; they'll be mutually exclusive until we define a means to negotiate witness-or-not in compact blocks
2512016-06-22T13:49:34  <sipa> so compact blocks won't work on test where segwit is already defined
2522016-06-22T13:49:41  <sipa> s/won't work/won't be used/
2532016-06-22T13:52:46  <wumpus> makes sense for the first version, being clear that it should not stay that way
2542016-06-22T13:53:03  <sipa> yes, and fixing it is trivial
2552016-06-22T13:53:11  <sipa> but i feel that's beyond the scope of segwit
2562016-06-22T13:53:36  <sipa> as that will at the very least testing how they interact in the real world
2572016-06-22T13:58:44  <wumpus> yes
2582016-06-22T13:59:38  <wumpus> though there is the risk that miners may see segwit as a step back, if its activation disables compact blocks
2592016-06-22T14:00:33  <sipa> we definitely need to have segwit+compactblock support defined and implement before picking a start time for segwit
2602016-06-22T14:01:19  <instagibbs> sipa, for 0.13 you mean?
2612016-06-22T14:01:32  <btcdrak> sipa: so step 1 is to merge in master, then step 2 work out the segwit+cb support, then step 3 set starttime?
2622016-06-22T14:01:42  <sipa> yes
2632016-06-22T14:01:51  <wumpus> oh! yes that order makes sense
2642016-06-22T14:04:38  <instagibbs> cb doesn't matter for 0.12.2, so backport with activation can move forward regardless, right?
2652016-06-22T14:04:56  <wumpus> right, cb doesn't matter for 0.12.2
2662016-06-22T14:05:32  <sipa> indeed, backport of segwit and definition of cb+segwit can happen in parallel
2672016-06-22T14:05:41  <sipa> when both are done, we can pick a start time
2682016-06-22T14:07:39  <btcdrak> neat :)
2692016-06-22T14:08:07  <btcdrak> so I assume after CB rebase, it's merge time?
2702016-06-22T14:09:02  <sipa> i'm unconfortable with the fact that the codebase since 7910 started and now has diverged so much that the recent changes and integration are not very transparent to review
2712016-06-22T14:09:22  <sipa> not so much that nobody has looked at them, but more that there isn't a good way to know whether you've seen everythong
2722016-06-22T14:09:34  <sipa> you can look at the merge commit in 7910
2732016-06-22T14:09:41  <sipa> but it's pretty big by now
2742016-06-22T14:10:13  <btcdrak> i thought we're not merging 7910, but the other cleaned up version?
2752016-06-22T14:10:36  <sipa> yes, of course
2762016-06-22T14:10:44  <sipa> but 8049 has been rebased constantly
2772016-06-22T14:12:20  <btcdrak> also I assume we need to reactivate/hf testnet?
2782016-06-22T14:12:44  <sipa> testnet activation is included in both
2792016-06-22T14:14:00  *** Sosumi has joined #bitcoin-core-dev
2802016-06-22T14:14:29  <sipa> but for example, #7935 introduced the concept of gbt_force (bip9 rollouts which the GBT client needs explicit support for)
2812016-06-22T14:15:21  *** robs has quit IRC
2822016-06-22T14:15:22  <sipa> in rebased segwit (#8149), the commit that adds GBT support for segwit also introduces the integration with gbt_force
2832016-06-22T14:15:46  <sipa> in the old segwit patch (#7910), that integration is completely hidden inside the merge commit with master
2842016-06-22T14:17:40  <sipa> other than that, i don't think waiting with merge makes much sense...
2852016-06-22T14:18:28  <sipa> looking at the merge commit in 7910 may make sense
2862016-06-22T14:18:41  *** zooko has joined #bitcoin-core-dev
2872016-06-22T14:18:53  <sipa> (git show will show you all conflicts it resolved, but the format with double +/- signs is not so simple to read)
2882016-06-22T14:27:42  *** gribble has quit IRC
2892016-06-22T14:28:28  <fanquake> sipa great work
2902016-06-22T14:29:06  *** Giszmo has joined #bitcoin-core-dev
2912016-06-22T14:30:50  <GitHub86> [bitcoin] laanwj opened pull request #8240: doc: Mention Windows XP end of support in release notes (master...2016_06_windows_xp) https://github.com/bitcoin/bitcoin/pull/8240
2922016-06-22T14:33:24  *** gribble has joined #bitcoin-core-dev
2932016-06-22T14:33:38  *** paveljanik has joined #bitcoin-core-dev
2942016-06-22T14:38:42  *** cryptapus_ has quit IRC
2952016-06-22T14:38:59  *** cryptapus_ has joined #bitcoin-core-dev
2962016-06-22T14:39:14  *** Guyver2 has joined #bitcoin-core-dev
2972016-06-22T14:44:32  <GitHub198> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/f3eebcf5158f...9adad33938ec
2982016-06-22T14:44:32  <GitHub198> bitcoin/0.12 ffff324 MarcoFalke: [doc] 0.12: prepare release notes
2992016-06-22T14:44:32  <GitHub192> [bitcoin] laanwj closed pull request #8236: [doc] 0.12.2: prepare release notes (0.12...Mf1606-docReleaseNotes) https://github.com/bitcoin/bitcoin/pull/8236
3002016-06-22T14:44:33  <GitHub198> bitcoin/0.12 9adad33 Wladimir J. van der Laan: Merge #8236: [doc] 0.12.2: prepare release notes...
3012016-06-22T14:48:11  *** cryptapus_ is now known as cryptapus
3022016-06-22T14:48:49  *** shangzhou has quit IRC
3032016-06-22T14:53:06  *** AaronvanW has joined #bitcoin-core-dev
3042016-06-22T14:54:00  *** fanquake has quit IRC
3052016-06-22T14:55:19  *** fanquake has joined #bitcoin-core-dev
3062016-06-22T14:57:09  <GitHub54> [bitcoin] laanwj opened pull request #8241: 0.13: Disable bad chain alerts (master...2016_06_alexit) https://github.com/bitcoin/bitcoin/pull/8241
3072016-06-22T15:09:40  *** sturles_ has joined #bitcoin-core-dev
3082016-06-22T15:09:40  *** sturles_ has joined #bitcoin-core-dev
3092016-06-22T15:10:31  *** ghtdak has quit IRC
3102016-06-22T15:10:46  *** sturles has quit IRC
3112016-06-22T15:11:01  *** ghtdak has joined #bitcoin-core-dev
3122016-06-22T15:12:36  *** Chris_Stewart_5 has quit IRC
3132016-06-22T15:29:43  *** Chris_Stewart_5 has joined #bitcoin-core-dev
3142016-06-22T15:43:24  *** LeMiner has quit IRC
3152016-06-22T15:59:33  *** zooko has quit IRC
3162016-06-22T15:59:57  *** LeMiner has joined #bitcoin-core-dev
3172016-06-22T16:12:58  *** spudowiar1 is now known as spudowiar
3182016-06-22T16:47:02  *** fanquake has quit IRC
3192016-06-22T17:03:27  <GitHub1> [bitcoin] paveljanik opened pull request #8242: Check if the macro PKG_PROG_PKG_CONFIG was expanded. (master...20160622_check_pkg-config) https://github.com/bitcoin/bitcoin/pull/8242
3202016-06-22T17:04:59  *** raedah has quit IRC
3212016-06-22T17:05:47  *** raedah has joined #bitcoin-core-dev
3222016-06-22T17:08:51  *** MarcoFalke has left #bitcoin-core-dev
3232016-06-22T17:12:43  *** sturles_ is now known as sturles
3242016-06-22T17:27:39  *** laurentmt has joined #bitcoin-core-dev
3252016-06-22T17:37:51  *** laurentmt has quit IRC
3262016-06-22T17:45:32  *** raedah has quit IRC
3272016-06-22T17:46:12  *** raedah has joined #bitcoin-core-dev
3282016-06-22T18:33:09  *** pedrobranco has quit IRC
3292016-06-22T18:34:33  *** pedrobranco has joined #bitcoin-core-dev
3302016-06-22T18:37:29  *** spudowiar1 has joined #bitcoin-core-dev
3312016-06-22T18:38:45  *** pedrobranco has quit IRC
3322016-06-22T18:45:28  *** Chris_Stewart_5 has quit IRC
3332016-06-22T18:47:32  *** pedrobranco has joined #bitcoin-core-dev
3342016-06-22T18:51:42  *** pedrobranco has quit IRC
3352016-06-22T18:58:12  *** moli has quit IRC
3362016-06-22T18:58:35  *** moli has joined #bitcoin-core-dev
3372016-06-22T19:27:39  *** zooko has joined #bitcoin-core-dev
3382016-06-22T19:48:34  *** Sosumi has quit IRC
3392016-06-22T19:57:51  *** cryptapus_ has joined #bitcoin-core-dev
3402016-06-22T20:00:49  *** cryptapus has quit IRC
3412016-06-22T20:03:34  *** cryptapus_ has quit IRC
3422016-06-22T20:11:53  *** robs has joined #bitcoin-core-dev
3432016-06-22T20:12:16  *** spudowiar1 has quit IRC
3442016-06-22T20:41:39  *** Chris_Stewart_5 has joined #bitcoin-core-dev
3452016-06-22T20:49:10  *** harrymm has joined #bitcoin-core-dev
3462016-06-22T21:03:18  *** kinlo has quit IRC
3472016-06-22T21:04:03  *** kinlo has joined #bitcoin-core-dev
3482016-06-22T21:04:28  *** cryptapus_afk is now known as cryptapus
3492016-06-22T21:12:45  *** Chris_Stewart_5 has quit IRC
3502016-06-22T21:15:04  *** mkarrer has quit IRC
3512016-06-22T21:17:38  *** GreenIsMyPepper_ is now known as GreenIsMyPepper
3522016-06-22T21:31:53  *** Chris_Stewart_5 has joined #bitcoin-core-dev
3532016-06-22T21:48:42  *** belcher has joined #bitcoin-core-dev
3542016-06-22T21:50:51  *** mkarrer has joined #bitcoin-core-dev
3552016-06-22T22:06:48  *** Guyver2 has quit IRC
3562016-06-22T22:30:44  *** justanotheruser is now known as justanothe[ATL]
3572016-06-22T22:31:34  *** justanothe[ATL] is now known as justanothe[MIN]
3582016-06-22T22:40:39  *** cryptapus is now known as cryptapus_afk
3592016-06-22T22:49:12  *** Guyver2 has joined #bitcoin-core-dev
3602016-06-22T23:24:14  *** afk11 has quit IRC
3612016-06-22T23:31:41  *** justanothe[MIN] is now known as justanotheruser
3622016-06-22T23:33:04  *** afk11 has joined #bitcoin-core-dev
3632016-06-22T23:33:04  *** afk11 has quit IRC
3642016-06-22T23:33:04  *** afk11 has joined #bitcoin-core-dev
3652016-06-22T23:43:25  *** xiangfu has joined #bitcoin-core-dev
3662016-06-22T23:56:17  *** gabridome has quit IRC
3672016-06-22T23:57:00  *** gabridome has joined #bitcoin-core-dev
3682016-06-22T23:59:02  *** lclc has quit IRC
3692016-06-22T23:59:12  *** lclc has joined #bitcoin-core-dev