--- Day changed Wed Jun 22 2016 00:00 -!- Irssi: Join to #bitcoin-core-dev was synced in 624 secs 00:00 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev 00:02 -!- fanquake [~Adium@unaffiliated/fanquake] has joined #bitcoin-core-dev 00:04 -!- spudowiar1 [~spudowiar@unaffiliated/spudowiar] has joined #bitcoin-core-dev 00:04 -!- Netsplit *.net <-> *.split quits: owowo, Eliel, Madars, jl2012, kanzure, Anduck, gmaxwell, spudowiar, dgenr8, e4xit 00:04 -!- jl2012_ is now known as jl2012 00:05 -!- Netsplit over, joins: dgenr8 00:14 -!- e4xit [~e4xit@cpc92302-cmbg19-2-0-cust1369.5-4.cable.virginm.net] has joined #bitcoin-core-dev 00:15 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 00:19 -!- gmaxwell_ [greg@mf4-xiph.osuosl.org] has quit [Changing host] 00:19 -!- gmaxwell_ [greg@wikimedia/KatWalsh/x-0001] has joined #bitcoin-core-dev 00:19 -!- gmaxwell_ is now known as gmaxwell 00:21 -!- MarcoFalke [~marco@host10-2.natpool.mwn.de] has joined #bitcoin-core-dev 00:28 < 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 00:44 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds] 00:47 < fanquake> wumpus Some issues that can be closed #7861 #7873 #7866 00:47 < fanquake> Also #6701 should have been closed by #7667 00:48 < fanquake> Possibly also #6702 00:49 -!- xiangfu [~xiangfu@58.135.95.134] has quit [Remote host closed the connection] 00:50 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has joined #bitcoin-core-dev 00:51 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has quit [Client Quit] 00:52 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 00:52 < fanquake> #7872 can also be closed. Not sure why this account has opened so many random/meaningless issues. 01:02 < MarcoFalke> done 01:05 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev 01:10 -!- JackH [~Jack@79-73-186-51.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev 01:13 < gmaxwell> Anyone have exact IsSuperMajority heights for BIP30/65/66 on mainnet and testnet handy, by any chance? 01:14 < btcdrak> gmaxwell BIP66 block 363724 according to https://bitcoin.stackexchange.com/questions/38436/when-did-bip66-switch-from-activation-to-enforcement 01:18 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has quit [Remote host closed the connection] 01:21 < btcdrak> gmaxwell: BIP65 was activated on block #388380 01:22 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 01:22 < btcdrak> luke-jr: maybe we should update the BIPs with activation blocks when they activate 01:22 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has joined #bitcoin-core-dev 01:27 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds] 01:32 < 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." 01:47 -!- Madars [~null@unaffiliated/madars] has joined #bitcoin-core-dev 01:48 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev 01:58 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Ping timeout: 276 seconds] 01:59 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 02:02 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds] 02:02 -!- rxatxoder [~rxatxoder@ip-89-239-24-145.mameradirychlost.cz] has joined #bitcoin-core-dev 02:05 < gmaxwell> uhh. is reindex broken on master for anyone else? 02:06 < gmaxwell> oh it's not broken. 02:06 < gmaxwell> it just looks funny now that it scans headers first. 02:06 < gmaxwell> hm. we might get bug reports on that. 02:07 -!- rxatxoder [~rxatxoder@ip-89-239-24-145.mameradirychlost.cz] has quit [Ping timeout: 260 seconds] 02:08 <@wumpus> those mrCertified issues are crazy, didn't notice them before, thanks for closing fanquake/MarcoFalke 02:18 < sipa> btcdrak: bips.md has more info 02:22 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev 02:31 < GitHub199> [bitcoin] laanwj pushed 1 new commit to 0.11: https://github.com/bitcoin/bitcoin/commit/0cd4fb6570f67d40891673bc8c41e473b9753c63 02:31 < GitHub199> bitcoin/0.11 0cd4fb6 Wladimir J. van der Laan: qt: Final translation update on 0.11 branch... 02:32 < gmaxwell> so the first point where if (block.nVersion >= 2 && IsSuperMajority(2, pindexPrev, consensusParams.nMajorityEnforceBlockUpgrade, consensusParams)) 02:35 < gmaxwell> is true is 224413, which seems to suggest that the BIP34 height in the chainparams is wrong? 02:37 < gmaxwell> nevermind. activated vs enforced. 02:37 <@wumpus> phew 02:38 < sipa> gmaxwell: what looks funny about it? 02:39 < sipa> gmaxwell: the chainparams value is the first point where it activated and never went to non-activated anymore 02:40 <@wumpus> maybe add a comment to prevent people panicking from this again in the future :) 02:41 < gmaxwell> I will. 02:41 < gmaxwell> I was in the process of making a patch to remove all the IsSuperMajority code, and replace with simple height checks. 02:52 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection] 02:53 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev 02:54 < gmaxwell> I think it's weird that we end up with network connections while reindexing. 02:59 <@wumpus> outgoing or incoming? 03:00 < gmaxwell> outgoing. 03:00 <@wumpus> in principle the network code is simply running while reindexing, it just doesn't request blocks nor transactions 03:00 <@wumpus> I don't think that's necessarily wrong 03:01 < gmaxwell> I'm probably only really noticing because I have debugging turned up and the invs are filling up my logs. 03:01 < gmaxwell> Is it useful to have connections up while reindexing? 03:01 < sipa> i guess it may make sense for addr relay 03:01 <@wumpus> no, but it also doesn't hurt, there doesn't need to be a strong coupling between network code and chain handling code 03:02 < sipa> we could extend the dont-request-blocks rule to dont-request-transactions too 03:02 <@wumpus> I think that's already the case? 03:02 < gmaxwell> doesn't appear to be requesting any. 03:02 < gmaxwell> The negatives I can think of: wastes network resources, might defeat "is it working" monitoring. Otherwise, I agree. 03:03 <@wumpus> there is also a paralellism aspect: there will already be connections to request blocks on when the reindexing finished 03:03 < gmaxwell> Thats a point. 03:03 <@wumpus> in any case there doesn't seem to be a strong reason to special-case this, so let's not 03:05 <@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... 03:05 < sipa> wumpus: unfortunately, there is a bug around that 03:05 < sipa> wumpus: we don't start requesting headers when reindex finishes 03:05 < sipa> so only when an inv for a new block arrives, actual sync continues after a reindex 03:05 < gmaxwell> We should probably release note that reindex may look inactive for a period of time at the beginning. 03:05 <@wumpus> that seems wrong 03:06 < sipa> we should fix it 03:06 < sipa> i'll file an issue if there is none already 03:06 < gmaxwell> indeed, but after 3 hours, an extra block delay is not the end of the world. :) 03:07 <@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 03:07 <@wumpus> so I suppose the +/- 10 minute delay is indeed not the end of the world 03:07 < 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. 03:07 <@wumpus> nah 03:08 < sipa> -really-reindex 03:08 < gmaxwell> --rebuild-state 03:08 < sipa> well we do have -reindex-chainstate now 03:08 < sipa> but -reindex itself is still useful when your block files are corrupted 03:08 <@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. 03:09 < sipa> of course 03:09 < gmaxwell> not yet, but in some near future where awesome improvements reduce the use for ever running it, of course. 03:09 < sipa> same with rescan 03:09 <@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 03:09 < sipa> at least the very common advice to fix random problems with a -rescan has died out 03:09 <@wumpus> if there was a purge-privatekeys option for the wallet I would want to rename it eveery release :p 03:10 < sipa> haha 03:10 < gmaxwell> okay. I won't argue for it, I was only motivated by the fact that many of the old reasons are gone. 03:10 < sipa> --steal-my-coins 03:10 < sipa> gmaxwell: do you have evidence of -reindex commonly being suggested for the wrong reasons? 03:10 < 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. 03:11 <@wumpus> the utxo backup fallback woud still be a good idea, we should aim to get it into 0.14 03:11 < 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. 03:11 < sipa> wumpus: agree 03:12 <@wumpus> gmaxwell: was that a guide on the wiki? if so it'd be easy to fix 03:12 <@wumpus> if not, we should probably contact the author 03:13 < gmaxwell> (also, for pruning to someday become a default option, we must reduce the incidence of reindex to ~0) 03:13 <@wumpus> do you have a link to that guide? 03:17 < gmaxwell> I thought I asked him, but I didn't. I asked now. 03:18 < 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 03:27 < fanquake> Was #6702 solved by #7667 ? 03:29 < fanquake> Can probably close #7724, sipa replied and it seems that the issue is user hardware. 03:34 < fanquake> #7735 Isn't going to happen any time soon, and can probably be closed. 03:37 < fanquake> #7979 can be closed. 03:44 <@wumpus> thanks, done 03:50 < fanquake> #7725 Looks closable, seems like the issue was related directory permissions. 03:51 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has quit [Remote host closed the connection] 03:52 < 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? 03:54 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has joined #bitcoin-core-dev 03:55 <@wumpus> agree 03:55 < sipa> fanquake: thanks a lot for going through those issues! 03:56 <@wumpus> https://github.com/bitcoin/bitcoin/issues/4095 is a qt issue, and a curious one at that, anyone ever managed to reproduce this? 03:56 <@wumpus> yes, thanks! 03:56 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has quit [Remote host closed the connection] 03:57 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has joined #bitcoin-core-dev 04:02 < fanquake> #5758 Seems to have gone stale, no followup replies. 04:02 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has joined #bitcoin-core-dev 04:02 < sipa> fanquake: closed 1.5 years ago? 04:02 <@wumpus> wrong number I think 04:03 < sipa> we need a checksum digit in PR numbers 04:03 < fanquake> Sorry, #5785 04:03 <@wumpus> <: 04:04 < sipa> ack on merging compact blocks? 04:05 < fanquake> #6472 && #7341 can probably be closed now that we've switched to Qt5.6.1 04:05 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has quit [Remote host closed the connection] 04:06 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has joined #bitcoin-core-dev 04:09 < fanquake> Can close #7834 - Changes to the macports portfile have been made upstream, and parallel builds are working ok normally. 04:14 < btcdrak> sipa: ack. 04:21 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 04:25 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Client Quit] 04:26 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 04:30 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has quit [Remote host closed the connection] 04:30 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has joined #bitcoin-core-dev 04:38 -!- Anduck_ is now known as Anduck 04:44 <@wumpus> I've been testing compact blocks on one of my ARM nodes for quite some time, no issues 04:46 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev 04:51 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has quit [Quit: Bye] 04:52 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds] 04:56 -!- robs [uid165609@gateway/web/irccloud.com/x-usmnbmyqstlnzfqx] has joined #bitcoin-core-dev 05:11 < instagibbs> I see no reason to block merging. Only nits/minor improvements left which can be taken on later. 05:20 <@wumpus> agree 05:20 <@wumpus> okay, hold on tight 05:20 * btcdrak drum roll 05:25 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 05:29 -!- You're now known as kanzure 05:31 < GitHub185> [bitcoin] laanwj pushed 19 new commits to master: https://github.com/bitcoin/bitcoin/compare/9e45ef1ef031...e9d76a161d30 05:31 < GitHub185> bitcoin/master 96806c3 Pieter Wuille: Stop trimming when mapTx is empty 05:31 < GitHub185> bitcoin/master 7c29ec9 Matt Corallo: If AcceptBlockHeader returns true, pindex will be set.... 05:31 < GitHub185> bitcoin/master cbda71c Matt Corallo: Move context-required checks from CheckBlockHeader to Contextual... 05:31 < GitHub25> [bitcoin] laanwj closed pull request #8068: Compact Blocks (master...udp) https://github.com/bitcoin/bitcoin/pull/8068 05:31 <@wumpus> ^^ 05:31 < fanquake> Woo 05:31 < instagibbs> \o/ 05:32 < btcdrak> oh man 05:32 < btcdrak> yis! 05:41 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 05:42 -!- shangzhou [uid156782@gateway/web/irccloud.com/x-efdjmtzvjiccuwlk] has joined #bitcoin-core-dev 05:42 < shangzhou> wow 05:51 < GitHub170> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/e9d76a161d30...9f1807af2422 05:51 < GitHub170> bitcoin/master b7bf037 Wladimir J. van der Laan: doc: Mention ARM executables in release process... 05:51 < GitHub170> bitcoin/master 05f64c9 Wladimir J. van der Laan: doc: Mention Linux ARM builds in release notes 05:51 < GitHub170> bitcoin/master 06f40ef Wladimir J. van der Laan: depends: Mention aarch64 as common cross-compile target 05:51 < 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 05:58 <@wumpus> is there any way to see (in the GUI or through RPC) if a wallet is BIP32? 06:15 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 06:23 -!- cryptapus_ [~cryptapus@66.119.84.15] has joined #bitcoin-core-dev 06:23 -!- cryptapus_ [~cryptapus@66.119.84.15] has quit [Changing host] 06:23 -!- cryptapus_ [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 06:27 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 260 seconds] 06:39 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 06:49 < 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 06:49 < sipa> so compact blocks won't work on test where segwit is already defined 06:49 < sipa> s/won't work/won't be used/ 06:52 <@wumpus> makes sense for the first version, being clear that it should not stay that way 06:53 < sipa> yes, and fixing it is trivial 06:53 < sipa> but i feel that's beyond the scope of segwit 06:53 < sipa> as that will at the very least testing how they interact in the real world 06:58 <@wumpus> yes 06:59 <@wumpus> though there is the risk that miners may see segwit as a step back, if its activation disables compact blocks 07:00 < sipa> we definitely need to have segwit+compactblock support defined and implement before picking a start time for segwit 07:01 < instagibbs> sipa, for 0.13 you mean? 07:01 < btcdrak> sipa: so step 1 is to merge in master, then step 2 work out the segwit+cb support, then step 3 set starttime? 07:01 < sipa> yes 07:01 <@wumpus> oh! yes that order makes sense 07:04 < instagibbs> cb doesn't matter for 0.12.2, so backport with activation can move forward regardless, right? 07:04 <@wumpus> right, cb doesn't matter for 0.12.2 07:05 < sipa> indeed, backport of segwit and definition of cb+segwit can happen in parallel 07:05 < sipa> when both are done, we can pick a start time 07:07 < btcdrak> neat :) 07:08 < btcdrak> so I assume after CB rebase, it's merge time? 07:09 < 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 07:09 < 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 07:09 < sipa> you can look at the merge commit in 7910 07:09 < sipa> but it's pretty big by now 07:10 < btcdrak> i thought we're not merging 7910, but the other cleaned up version? 07:10 < sipa> yes, of course 07:10 < sipa> but 8049 has been rebased constantly 07:12 < btcdrak> also I assume we need to reactivate/hf testnet? 07:12 < sipa> testnet activation is included in both 07:14 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has joined #bitcoin-core-dev 07:14 < sipa> but for example, #7935 introduced the concept of gbt_force (bip9 rollouts which the GBT client needs explicit support for) 07:15 -!- robs [uid165609@gateway/web/irccloud.com/x-usmnbmyqstlnzfqx] has quit [Quit: Connection closed for inactivity] 07:15 < sipa> in rebased segwit (#8149), the commit that adds GBT support for segwit also introduces the integration with gbt_force 07:15 < sipa> in the old segwit patch (#7910), that integration is completely hidden inside the merge commit with master 07:17 < sipa> other than that, i don't think waiting with merge makes much sense... 07:18 < sipa> looking at the merge commit in 7910 may make sense 07:18 -!- zooko [~user@2601:281:8000:8387:d0ec:becd:456:ad4d] has joined #bitcoin-core-dev 07:18 < sipa> (git show will show you all conflicts it resolved, but the format with double +/- signs is not so simple to read) 07:27 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Read error: Connection reset by peer] 07:28 < fanquake> sipa great work 07:29 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #bitcoin-core-dev 07:30 < 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 07:33 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev 07:33 -!- paveljanik [~paveljani@79-98-72-216.sys-data.com] has joined #bitcoin-core-dev 07:33 -!- paveljanik [~paveljani@79-98-72-216.sys-data.com] has quit [Changing host] 07:33 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev 07:38 -!- cryptapus_ [~cryptapus@unaffiliated/cryptapus] has quit [Quit: Konversation terminated!] 07:38 -!- cryptapus_ [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 07:39 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 07:44 < GitHub198> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/f3eebcf5158f...9adad33938ec 07:44 < GitHub198> bitcoin/0.12 ffff324 MarcoFalke: [doc] 0.12: prepare release notes 07:44 < 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 07:44 < GitHub198> bitcoin/0.12 9adad33 Wladimir J. van der Laan: Merge #8236: [doc] 0.12.2: prepare release notes... 07:48 -!- cryptapus_ is now known as cryptapus 07:48 -!- shangzhou [uid156782@gateway/web/irccloud.com/x-efdjmtzvjiccuwlk] has quit [Quit: Connection closed for inactivity] 07:53 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 07:54 -!- fanquake [~Adium@unaffiliated/fanquake] has quit [Quit: Leaving.] 07:55 -!- fanquake [~Adium@unaffiliated/fanquake] has joined #bitcoin-core-dev 07:57 < GitHub54> [bitcoin] laanwj opened pull request #8241: 0.13: Disable bad chain alerts (master...2016_06_alexit) https://github.com/bitcoin/bitcoin/pull/8241 08:09 -!- sturles_ [~sturles@ulrik.uio.no] has joined #bitcoin-core-dev 08:09 -!- sturles_ [~sturles@ulrik.uio.no] has quit [Changing host] 08:09 -!- sturles_ [~sturles@unaffiliated/sturles] has joined #bitcoin-core-dev 08:10 -!- ghtdak [~ghtdak@unaffiliated/ghtdak] has quit [Ping timeout: 244 seconds] 08:10 -!- sturles [~sturles@unaffiliated/sturles] has quit [Ping timeout: 244 seconds] 08:11 -!- ghtdak [~ghtdak@unaffiliated/ghtdak] has joined #bitcoin-core-dev 08:12 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 276 seconds] 08:29 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 08:43 -!- LeMiner [LeMiner@unaffiliated/leminer] has quit [Read error: Connection reset by peer] 08:59 -!- zooko [~user@2601:281:8000:8387:d0ec:becd:456:ad4d] has quit [Ping timeout: 250 seconds] 08:59 -!- LeMiner [LeMiner@unaffiliated/leminer] has joined #bitcoin-core-dev 09:12 -!- spudowiar1 is now known as spudowiar 09:47 -!- fanquake [~Adium@unaffiliated/fanquake] has quit [Quit: Leaving.] 10:03 < 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 10:04 -!- raedah [~x@172.56.42.64] has quit [Remote host closed the connection] 10:05 -!- raedah [~x@172.56.42.64] has joined #bitcoin-core-dev 10:08 -!- MarcoFalke [~marco@host10-2.natpool.mwn.de] has left #bitcoin-core-dev [] 10:12 -!- sturles_ is now known as sturles 10:27 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has joined #bitcoin-core-dev 10:37 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has quit [Quit: laurentmt] 10:45 -!- raedah [~x@172.56.42.64] has quit [Remote host closed the connection] 10:46 -!- raedah [~x@172.56.42.64] has joined #bitcoin-core-dev 11:33 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection] 11:34 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev 11:37 -!- spudowiar1 [~spudowiar@unaffiliated/spudowiar] has joined #bitcoin-core-dev 11:38 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Ping timeout: 246 seconds] 11:45 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds] 11:47 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev 11:51 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Ping timeout: 246 seconds] 11:58 -!- moli [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer] 11:58 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 12:27 -!- zooko [~user@c-73-229-199-227.hsd1.co.comcast.net] has joined #bitcoin-core-dev 12:48 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has quit [Quit: Bye] 12:57 -!- cryptapus_ [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 13:00 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 252 seconds] 13:03 -!- cryptapus_ [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 252 seconds] 13:11 -!- robs [uid165609@gateway/web/irccloud.com/x-xnishtvlzqpokmdu] has joined #bitcoin-core-dev 13:12 -!- spudowiar1 [~spudowiar@unaffiliated/spudowiar] has quit [Quit: Leaving.] 13:41 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 13:49 -!- harrymm [~wayne@104.237.91.245] has joined #bitcoin-core-dev 14:03 -!- kinlo [peter@unaffiliated/kinlo] has quit [Ping timeout: 246 seconds] 14:04 -!- kinlo [peter@unaffiliated/kinlo] has joined #bitcoin-core-dev 14:04 -!- cryptapus_afk is now known as cryptapus 14:12 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds] 14:15 -!- mkarrer [~mkarrer@48.red-83-47-111.dynamicip.rima-tde.net] has quit [Ping timeout: 240 seconds] 14:17 -!- GreenIsMyPepper_ is now known as GreenIsMyPepper 14:31 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 14:48 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev 14:50 -!- mkarrer [~mkarrer@48.red-83-47-111.dynamicip.rima-tde.net] has joined #bitcoin-core-dev 15:06 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 15:30 -!- justanotheruser is now known as justanothe[ATL] 15:31 -!- justanothe[ATL] is now known as justanothe[MIN] 15:40 -!- cryptapus is now known as cryptapus_afk 15:49 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 15:49 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Client Quit] 16:24 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Read error: Connection reset by peer] 16:31 -!- justanothe[MIN] is now known as justanotheruser 16:33 -!- afk11 [~afk11@109.255.154.81] has joined #bitcoin-core-dev 16:33 -!- afk11 [~afk11@109.255.154.81] has quit [Changing host] 16:33 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev 16:43 -!- xiangfu [~xiangfu@58.135.95.134] has joined #bitcoin-core-dev 16:56 -!- gabridome [~gabridome@host205-24-dynamic.51-79-r.retail.telecomitalia.it] has quit [Read error: No route to host] 16:57 -!- gabridome [~gabridome@host205-24-dynamic.51-79-r.retail.telecomitalia.it] has joined #bitcoin-core-dev 16:59 -!- lclc [~lclc@unaffiliated/lclc] has quit [Ping timeout: 244 seconds] 16:59 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev 17:00 -!- isis [~isis@abulafia.patternsinthevoid.net] has quit [Ping timeout: 244 seconds] 17:03 -!- isis [~isis@abulafia.patternsinthevoid.net] has joined #bitcoin-core-dev 17:25 -!- raedah [~x@172.56.42.64] has quit [Remote host closed the connection] 17:26 -!- raedah [~x@172.56.42.64] has joined #bitcoin-core-dev 17:35 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 17:42 -!- xiangfu [~xiangfu@58.135.95.134] has quit [Remote host closed the connection] 17:48 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving] 17:54 -!- Lauda [~Lauda@2001:41d0:52:a00::d36] has quit [Ping timeout: 250 seconds] 17:54 -!- Lauda [~Lauda@133.ip-92-222-169.eu] has joined #bitcoin-core-dev 17:55 -!- Taek [~quassel@2001:41d0:1:472e::] has quit [Ping timeout: 260 seconds] 17:55 -!- nsh [~lol@wikipedia/nsh] has quit [Ping timeout: 260 seconds] 17:55 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ijakbktlieyurclr] has quit [Quit: Connection closed for inactivity] 17:57 -!- Taek [~quassel@ks36119.kimsufi.com] has joined #bitcoin-core-dev 18:10 -!- nsh [~lol@wikipedia/nsh] has joined #bitcoin-core-dev 18:10 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 18:17 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev 18:19 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 18:27 -!- zooko [~user@c-73-229-199-227.hsd1.co.comcast.net] has quit [Ping timeout: 244 seconds] 19:05 -!- ClockCat [~CattieCat@2607:fcc8:9e44:2500:acf9:bb22:12f2:147e] has quit [Quit: Leaving] 19:10 -!- rallat [0819c419@gateway/web/freenode/ip.8.25.196.25] has joined #bitcoin-core-dev 19:11 -!- rallat [0819c419@gateway/web/freenode/ip.8.25.196.25] has quit [Client Quit] 19:35 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 19:43 -!- hsmiths [~hsmiths@cpe-76-174-26-91.socal.res.rr.com] has quit [Quit: END OF LINE] 19:45 < GitHub58> [bitcoin] dcousens opened pull request #8244: remove unnecessary LOCK(cs_main) (master...patch-1) https://github.com/bitcoin/bitcoin/pull/8244 19:46 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev 19:46 < dcousens> uh, I probably meant to ask about https://github.com/bitcoin/bitcoin/pull/8244 here, not #bitcoin-dev 19:49 -!- hsmiths [~hsmiths@cpe-76-174-26-91.socal.res.rr.com] has joined #bitcoin-core-dev 19:55 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Quit: ZNC 1.6.3 - http://znc.in] 19:56 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds] 20:02 -!- raedah [~x@172.56.42.64] has quit [Remote host closed the connection] 20:03 -!- raedah [~x@172.56.42.64] has joined #bitcoin-core-dev 20:28 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 264 seconds] 20:32 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 20:40 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 244 seconds] 20:42 -!- raedah [~x@172.56.42.64] has quit [Remote host closed the connection] 20:42 -!- raedah [~x@172.56.42.64] has joined #bitcoin-core-dev 20:53 -!- TomMc [~tom@gateway/vpn/privateinternetaccess/tommc] has joined #bitcoin-core-dev 21:14 -!- TomMc [~tom@gateway/vpn/privateinternetaccess/tommc] has quit [Ping timeout: 276 seconds] 21:19 -!- ClockCat [~CattieCat@2607:fcc8:9e44:2500:dd5f:8b0e:1991:ee42] has joined #bitcoin-core-dev 21:27 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Quit: leaving] 21:28 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev 21:48 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Remote host closed the connection] 21:54 -!- zooko [~user@2601:281:8000:8387:dc8f:d3d3:1b67:e9d5] has joined #bitcoin-core-dev 22:00 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds] 22:01 -!- kitty_ [475b7f9c@gateway/web/freenode/ip.71.91.127.156] has joined #bitcoin-core-dev 22:01 < kitty_> Hi I need help please 22:01 < kitty_> Does anyone here know how to contact the bitcoin core wallet support team 22:03 < kitty_> Is there a support team for bitcoin core wallet 22:17 < kitty_> is anyone here 22:29 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-pslndrogkrslcsnb] has quit [Quit: Connection closed for inactivity] 22:33 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev 22:35 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ziijwboxnvlvelpn] has joined #bitcoin-core-dev 22:36 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 22:43 < kitty_> is there anyone here that helps with bitcoin core wallet 22:48 -!- zooko [~user@2601:281:8000:8387:dc8f:d3d3:1b67:e9d5] has quit [Ping timeout: 250 seconds] 22:49 < jl2012> Just ask your question, or try #bitcoin 22:50 < kitty_> what do you mean #bitcoin 22:50 < kitty_> #bitcoin 23:23 -!- raedah [~x@172.56.42.64] has quit [Remote host closed the connection] 23:24 -!- raedah [~x@172.56.42.64] has joined #bitcoin-core-dev 23:27 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-geemdsblnimltmeq] has joined #bitcoin-core-dev 23:35 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Read error: Connection reset by peer] 23:35 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 23:41 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Read error: Connection reset by peer] 23:42 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 23:53 -!- kitty_ [475b7f9c@gateway/web/freenode/ip.71.91.127.156] has quit [Quit: Page closed] 23:55 -!- [b__b] [~b__b]@ec2-54-85-45-223.compute-1.amazonaws.com] has quit [Ping timeout: 276 seconds] 23:55 -!- [b__b] [~b__b]@ec2-54-85-45-223.compute-1.amazonaws.com] has joined #bitcoin-core-dev