--- Day changed Tue Aug 16 2016 00:20 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 00:30 -!- rubensayshi [~ruben@82.201.93.169] has joined #bitcoin-core-dev 00:33 -!- laurentmt [~Thunderbi@80.215.234.93] has joined #bitcoin-core-dev 00:33 -!- laurentmt [~Thunderbi@80.215.234.93] has quit [Client Quit] 01:05 -!- JackH [~Jack@79-73-188-45.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev 01:10 < gmaxwell> I'm surprised no large miners are on 0.13rc yet. 01:11 < gmaxwell> (I know none aren't because I watched dozens of blocks go by today without picking up some pretty high fee CPFP transactions) 01:23 -!- mn3monic_ [~guido@176.9.68.68] has quit [Ping timeout: 264 seconds] 01:29 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 01:32 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 252 seconds] 01:34 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 265 seconds] 01:47 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 01:48 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 01:57 < Lightsword> gmaxwell, should I update to it in production? 01:59 < gmaxwell> I think you should. As far as we know it's mature and stable. I've been mining on it since before the RCs and haven't seen any issues. Obviously normal risks of new software apply, so you might want to keep a closer eye on it than normal. 02:00 < Lightsword> gmaxwell, are there any config differences that changes since 0.13 that I should set? 02:01 < gmaxwell> Some changes in the how block size limits are configured, mentioned in the release notes. I'm not recalling anything else that would be applicable to you, but I'll go through the release notes right now. 02:06 < sipa> Lightsword: actually, comments on the release notes are pretty welcome 02:06 < sipa> it's often hard to judge what is obvious and what is confusing to someone who hasn't followed all the changes in detail 02:19 < GitHub169> [bitcoin] sipa opened pull request #8519: [0.13] A few small improvements to the 0.13 release notes (0.13...relnotes-0.13) https://github.com/bitcoin/bitcoin/pull/8519 02:19 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Read error: Connection reset by peer] 02:20 < GitHub58> [bitcoin] laanwj opened pull request #8520: build: Remove check for `openssl/ec.h` (master...2016_08_remove_openssl_ech_check) https://github.com/bitcoin/bitcoin/pull/8520 02:23 -!- AaronvanW [~ewout@198pc231.sshunet.nl] has joined #bitcoin-core-dev 02:23 -!- AaronvanW [~ewout@198pc231.sshunet.nl] has quit [Changing host] 02:23 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 02:26 < GitHub37> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/bbd9740f534f...2c2d471e18f0 02:26 < GitHub37> bitcoin/master edb6cf1 instagibbs: remove no-longer-used InitError logic 02:26 < GitHub37> bitcoin/master 2c2d471 Wladimir J. van der Laan: Merge #8516: [trivial] remove no-longer-used InitError logic... 02:26 < GitHub26> [bitcoin] laanwj closed pull request #8516: [trivial] remove no-longer-used InitError logic (master...deadiniterr) https://github.com/bitcoin/bitcoin/pull/8516 02:31 < Lightsword> sipa, one thing that might be handy is to have a list of all miner relevant config optimizations somewhere 02:34 < Lightsword> gmaxwell, anything I might be missing here? https://gist.github.com/jameshilliard/ba6116f873066e794120e34f49ee5e63 02:35 < sipa> bytespersigop=1 exposes you to an attack with high-sigops transactions 02:35 < sipa> (but if that's ok for you, you can obviously set it, it doesn't hurt anyone else) 02:36 < Lightsword> sipa, ugh…I have that because sendrawtransaction doesn’t have an option like this https://github.com/bitcoin/bitcoin/pull/7533 02:36 < sipa> in 0.13 the meaning of bytespersigop changed; it doesn't cause rejection of transactions that exceed the bytes/sigop ratio; it merely requires a higher fee for them 02:36 < Lightsword> oh 02:38 < Lightsword> so I should be able to remove that and still send higher sigops transactions now? 02:38 < sipa> yes; they'll just be treated as if they were larger 02:39 < sipa> say a 200 byte transaction with 20 sigops... for fee and miner selection purposes it will be treated as if it was 400 bytes large 02:39 < sipa> (the default is -bytespersigop=20) 02:40 < sipa> may i ask why you need to send such transactions? 02:40 < Lightsword> some transactions with OP_RETURN’s it seemed were throwing sigops errors when I tried sending them 02:41 < Lightsword> they weren’t transactions I created, but was asked to mine for some company 02:41 < sipa> OP_RETURN shouldn't affect that... rather the opposite 02:41 < sipa> they increase the size without increasing sigops 02:41 < sipa> anyway, ok 02:42 < Lightsword> sipa, here’s an example https://blockchain.info/tx/5a3f68d824b75d2f659c545acbc395dc152b589264d301a40dd1d29858ed3c6a 02:42 < sipa> ah, raw multisig 02:43 < sipa> yes, that was the reason for changing the behaviour of -bytespersigop, because it accidentally killed some raw multisig transactions 02:43 < Lightsword> ok, so I’ll remove that then 02:44 < sipa> -enforcenodebloom was removed, it's always on now 02:44 < Lightsword> ok, removed that as well 02:55 -!- AureliusM [cb6ef215@gateway/web/freenode/ip.203.110.242.21] has joined #bitcoin-core-dev 02:56 -!- Ginnarr [~Ginnarr@unaffiliated/ginnarr] has joined #bitcoin-core-dev 03:05 < GitHub99> [bitcoin] laanwj opened pull request #8521: qa: Remove duplicate `hash160` implementation (master...2016_08_hash160_dupe) https://github.com/bitcoin/bitcoin/pull/8521 03:19 -!- mn3monic_ [~guido@176.9.68.68] has joined #bitcoin-core-dev 03:23 < GitHub136> [bitcoin] laanwj pushed 4 new commits to 0.13: https://github.com/bitcoin/bitcoin/compare/b52c67c4b188...4374f0ee35f8 03:23 < GitHub97> [bitcoin] laanwj closed pull request #8519: [0.13] A few small improvements to the 0.13 release notes (0.13...relnotes-0.13) https://github.com/bitcoin/bitcoin/pull/8519 03:23 < GitHub136> bitcoin/0.13 7f84015 Pieter Wuille: Inline mempool RPCs and feefilter into misc sections 03:23 < GitHub136> bitcoin/0.13 fe20b83 Pieter Wuille: Remove refactors from list of changes 03:23 < GitHub136> bitcoin/0.13 2f58589 Pieter Wuille: Mention dump/import support for HD wallets 03:26 < wumpus> it may help releasing 0.13.0, it makes sense for no one to mine (in a big operation) with an rc 03:27 < sipa> wumpus: parse failure 03:27 < wumpus> well I wouldn't use a rc to mine either 03:28 < wumpus> and just wait for the release 03:28 < sipa> well, me personally would like to see people from all parts of the ecosystem - including mingers - test the rc, to find potential problems with it 03:29 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-zufvamgzmcwprtqu] has joined #bitcoin-core-dev 03:29 < sipa> on the other hand, i can't really state "the rc is safe to mine with!", as that would imply it should be a release already 03:29 < sipa> s/mingers/miners/ 03:29 < wumpus> maybe they tested on small scale 03:30 < wumpus> "that would imply it should be a release already" maybe it should 03:31 < sipa> a few days won't matter 03:31 < wumpus> any reason to not tag rc3 as final right now? 03:32 < sipa> i know of no problems 03:32 < wumpus> it had almost no changes compared to rc2, so I don't think it needs as long testing as rc2 03:33 < sipa> #8490 ? 03:34 -!- Samdney [~Samdney@dyn-ant666999.hawo.ipv6.uni-erlangen.de] has joined #bitcoin-core-dev 03:34 < wumpus> needs rebase 03:44 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 03:47 < gmaxwell> Since, afaict, virtually no one in this space has reasonable qualification testing, if people don't mine on RCs we might as well not have them as far as mining is concerned. 03:48 < sipa> #8518 worries me, but shouldn't affect mainnet in 0.13.0 03:55 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 03:56 < gmaxwell> sipa: since there were segwit peers in his log that weren't disconnected, I don't see any reason to believe that it isn't just as it describes-- peers that were stalling the transfer. 03:58 < sipa> ah 03:58 < sipa> but it seems he is not making progress 03:59 < sipa> i think it's due to having multiple potential chains on top of his current state 04:03 -!- crudel [crudel@gateway/shell/fnordserver.eu/x-cusbjtggfmxanrue] has joined #bitcoin-core-dev 04:07 < MarcoFalke> gmaxwell: the peers will come in and go after 2 seconds. I have the Debug window open and it looks like a fifo queue of peers. 04:08 < MarcoFalke> Somewhat odd that no one reported similar problems, though. 04:24 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 250 seconds] 04:24 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 04:26 -!- paveljanik [~paveljani@79.98.72.216] has joined #bitcoin-core-dev 04:26 -!- paveljanik [~paveljani@79.98.72.216] has quit [Changing host] 04:26 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev 04:28 < MarcoFalke> Deleted peers.dat twice. On the first try it synced fine. On the second try I was back at the stalling problem. 04:29 -!- Ginnarr [~Ginnarr@unaffiliated/ginnarr] has quit [Quit: Textual IRC Client: www.textualapp.com] 04:30 < MarcoFalke> Could it be that we are populating the fetch window with headers and then expect the 0.13 peer to deliver a block in 2 seconds? 04:31 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 04:32 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Client Quit] 04:32 -!- cryptapus_ [~cryptapus@87.254.202.195] has joined #bitcoin-core-dev 04:32 -!- cryptapus_ [~cryptapus@87.254.202.195] has quit [Changing host] 04:32 -!- cryptapus_ [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 04:40 -!- cryptapus_ is now known as cryptapus 04:59 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 05:07 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving] 05:33 < sipa> NicolasDorier: 8295 used locks and a cachedhashesmap, no? 05:33 < NicolasDorier> yes, my mistake 05:33 < NicolasDorier> I checked your PR after, edited my comment 05:35 < sipa> ah, i see 05:36 < NicolasDorier> sipa: 8464 seems fine as well may make things easier as well for libconsensus stuff later 05:36 < NicolasDorier> uh no 05:36 < NicolasDorier> this one https://github.com/sipa/bitcoin/commits/noprecomputecachedhashes 05:37 < NicolasDorier> it is smaller diff as well 05:38 < NicolasDorier> I'm fine for merging my PR, but also fine if you make a new PR and squash those two commits together, I think your implementation is simpler, more efficient and will make my life easier for libconsensus later. 05:44 < NicolasDorier> sipa: yep, just reviewed it, now I would prefer you make a new PR which supersede mine with https://github.com/sipa/bitcoin/commits/noprecomputecachedhashes, you can squash the two commits as well. 05:47 < NicolasDorier> However I don't understand why std::vector> is needed and can't be just std::vector. The CachedHashes have the same life time as the vector 05:48 < sipa> NicolasDorier: resizing a vector changes the addresses 05:48 < sipa> by using an unique_ptr for each element, the cavhedhashes don't move 05:48 < sipa> ah 05:49 < sipa> we could just resize the vector to have block.vtx.size() entries 05:50 < NicolasDorier> sipa: well, in this case there is a bug in my PR ? I am using a map 05:50 < NicolasDorier> ah no 05:50 < NicolasDorier> I'm copying stuff 05:51 < sipa> indeed, and you do the lookup every time again 05:51 < sipa> i do it ahead of time 05:51 < sipa> each CScriptCheck gets a pointer to the CachedHashes it uses 05:51 < sipa> also, adding elements to a map does not invalidate pointers 05:52 < NicolasDorier> it does not relocate the elements as the vector ? 05:52 < sipa> indeed 05:53 < NicolasDorier> I slightly prefer a resize followed by std::vector instead of using a unique_ptr. Anyway, whatever you choose let me know when you do the PR. Squash my commit, I don't really care, easier to review. 05:54 < sipa> yes, i agree; reserve + no unique_ptr is better 05:55 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 05:57 -!- kadoban [~mud@unaffiliated/kadoban] has joined #bitcoin-core-dev 05:59 < NicolasDorier> sipa: Just a reminder, you were mentionning that you were OK with a HashCacheMap because it would be useful for later. I did not really followed why (something with signature aggregation if I remember), that's just reminder. 05:59 < sipa> NicolasDorier: yes, that's why i'm not strongly in favor of my own solution :) 06:00 < sipa> we'll need something like this anyway 06:00 < NicolasDorier> mmh 06:00 < sipa> doesn't mean we can't use this now 06:00 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 06:01 < NicolasDorier> well, whichever is fine for me. I still don't see far enough to see how the HashCacheMap will be useful, as how the signature aggregation will be implemented is still blurry in my mind. Both of them are fine to me, if you do a PR, will test and ACK as well. 06:02 < sipa> not HashCachedMap itself; but some mutable data structure that individual script checks can modify 06:03 < NicolasDorier> if so I think it is better to do it later with another class specially for that like a "TransactionContext" or something like that 06:04 < NicolasDorier> not a big deal to code when it will be needed 06:08 -!- MarcoFalke [~marco@2a02:778:100:ea01:2225:64ff:fe3b:d4ca] has quit [Ping timeout: 264 seconds] 06:15 < GitHub76> [bitcoin] sipa opened pull request #8524: Precompute sighashes (master...noprecomputecachedhashes) https://github.com/bitcoin/bitcoin/pull/8524 06:16 < sipa> NicolasDorier: i left you as author since you still wrote most of the code 06:26 -!- eratkat [~er4tt@95.215.44.99] has quit [Quit: Leaving] 06:33 < NicolasDorier> as you want, but well, except the big_transaction tests nothing will be really left in reality :D 06:33 < sipa> the tests are important :) 06:38 < sipa> NicolasDorier: split the commit into 2 06:38 < sipa> better now? 06:39 < NicolasDorier> why splitting ? 06:39 < NicolasDorier> ah you mean make a separate commit for the test only ? 06:39 < NicolasDorier> as you want, I don't really mind 06:48 -!- murch [~murch@p4FE3905D.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 06:57 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 07:02 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 07:12 -!- MarcoFalke [~marco@2a02:778:100:ea01:2225:64ff:fe3b:d4ca] has joined #bitcoin-core-dev 07:16 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 07:32 -!- jujumax [~jujumax@host75.190-224-145.telecom.net.ar] has joined #bitcoin-core-dev 07:37 -!- cryptapus_afk [~cryptapus@unaffiliated/cryptapus] has quit [Remote host closed the connection] 07:48 < sipa> it seems that the only versions on the network that would relay invalid witness txn are 0.10.x 07:49 < sipa> <=0.9 would not, due to nonstandard script 07:49 < sipa> >=0.11 would not, due to CLEANSTACK rule 07:50 < sipa> given that, could we just not bother with the double validation for witness txn, and special rules about not DoS scoring invalid witness txn for non-witness peers? 07:51 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev 07:56 -!- JZA [JZA@gateway/shell/elitebnc/x-dwofbiqpiramhbuh] has joined #bitcoin-core-dev 07:58 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 08:03 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 08:21 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 08:32 -!- rubensayshi [~ruben@82.201.93.169] has quit [Remote host closed the connection] 08:42 < GitHub8> [bitcoin] sipa opened pull request #8525: Do not store witness txn in rejection cache (master...nowitnessreject) https://github.com/bitcoin/bitcoin/pull/8525 08:47 -!- MarcoFalke [~marco@2a02:778:100:ea01:2225:64ff:fe3b:d4ca] has quit [Ping timeout: 264 seconds] 08:51 < GitHub50> [bitcoin] jl2012 opened pull request #8526: Make non-minimal OP_IF/NOTIF argument non-standard for P2WSH (master...minimalif) https://github.com/bitcoin/bitcoin/pull/8526 08:57 -!- harrymm [~wayne@37.58.59.75] has quit [Ping timeout: 265 seconds] 09:00 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 09:03 < GitHub26> [bitcoin] sipa opened pull request #8527: Take minRelayTxFee into account in FEEFILTER messages (master...clampfeefilter) https://github.com/bitcoin/bitcoin/pull/8527 09:05 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 09:06 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 09:15 -!- harrymm [~wayne@37.58.59.76] has joined #bitcoin-core-dev 09:19 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 09:19 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 09:22 -!- MarcoFalke [~marco@5.199.182.203] has joined #bitcoin-core-dev 09:23 -!- zooko [~user@23.31.82.211] has joined #bitcoin-core-dev 09:27 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 09:28 -!- zooko [~user@23.31.82.211] has quit [Read error: Connection reset by peer] 10:01 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 10:04 < kanzure> jonasschnelli: re: peer authentication bip, https://github.com/jonasschnelli/bips/pull/1 10:06 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 10:15 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 10:16 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 10:22 -!- zooko [~user@23.31.82.211] has joined #bitcoin-core-dev 10:23 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 240 seconds] 10:25 < Chris_Stewart_5> sipa: Is the hash type included in the DER signature 'total size' of the signature? 10:27 < arubi> Chris_Stewart_5, are you asking about the second byte after 0x30, or about IsValidSignatureEncoding() ? if former, no, if latter, yes 10:28 < sipa> what arubi said 10:29 < Chris_Stewart_5> arubi: That was exactly what i was asking about. Thanks :-) 10:31 < sipa> Chris_Stewart_5: the sighash type is something bitcoin specific 10:31 < sipa> so it's not part of the DER standard for encoding ECDSA signatures 10:31 < sipa> and the length part is from DER 10:32 < arubi> yw Chris_Stewart_5 :) 10:33 < Chris_Stewart_5> Yeah -- I was conflating the two. 10:35 -!- jujumax [~jujumax@host75.190-224-145.telecom.net.ar] has quit [Remote host closed the connection] 10:36 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Ping timeout: 252 seconds] 10:43 -!- zooko [~user@23.31.82.211] has quit [Ping timeout: 276 seconds] 10:44 -!- MarcoFalke [~marco@5.199.182.203] has left #bitcoin-core-dev [] 11:03 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 11:03 -!- whphhg_ [whphhg@gateway/vpn/mullvad/x-sqmjxdwfxfftelsw] has joined #bitcoin-core-dev 11:07 -!- whphhg [~whphhg@unaffiliated/whphhg] has quit [Ping timeout: 240 seconds] 11:08 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 11:10 < Chris_Stewart_5> Is this the function that was used to check encoding pre BIP66? 11:10 < Chris_Stewart_5> https://github.com/bitcoin/bitcoin/blob/master/src/script/interpreter.cpp#L185 11:11 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 11:13 -!- whphhg_ is now known as whphhg 11:14 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 11:14 < sipa> Chris_Stewart_5: also post BIP66 11:22 -!- JZA [JZA@gateway/shell/elitebnc/x-dwofbiqpiramhbuh] has quit [Excess Flood] 11:25 < instagibbs> sdaftuar, this comment refering to the reject filter? https://github.com/bitcoin/bitcoin/blob/master/qa/rpc-tests/p2p-segwit.py#L949 11:28 < sipa> instagibbs: i assume it is about the askfor logic 11:28 < sipa> which retries 11:31 < instagibbs> an announcement the second time works just fine on my end 11:37 -!- aalex [~aalex@64.187.177.58] has quit [Quit: Connection reset by beer] 11:38 -!- jujumax [~jujumax@host75.190-224-145.telecom.net.ar] has joined #bitcoin-core-dev 11:45 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev 11:58 -!- harrymm [~wayne@37.58.59.76] has quit [Ping timeout: 240 seconds] 12:04 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 12:09 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 12:11 < GitHub92> [bitcoin] instagibbs opened pull request #8528: Update p2p-segwit.py to reflect correct AskFor behavior (master...rejectsw) https://github.com/bitcoin/bitcoin/pull/8528 12:17 -!- harrymm [~wayne@223.204.250.103] has joined #bitcoin-core-dev 12:20 -!- Giszmo [~leo@2001:a61:32cf:d301:d12d:6d17:d34c:ed36] has joined #bitcoin-core-dev 12:42 < instagibbs> this is referring to the reject filter, right? https://github.com/bitcoin/bitcoin/blob/master/qa/rpc-tests/p2p-segwit.py#L294 12:42 < instagibbs> I'm trying to make an example of the segwit DoS issue, and found a case that I think should be catching it but isn't 12:42 < instagibbs> (to my reading anyways) 12:53 -!- JZA [JZA@gateway/shell/elitebnc/x-bepspuqyusiwnazv] has joined #bitcoin-core-dev 13:05 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 13:10 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 13:51 -!- Yogh [~Yogh@f36186.upc-f.chello.nl] has quit [Ping timeout: 265 seconds] 13:53 -!- Yogh [~Yogh@f36186.upc-f.chello.nl] has joined #bitcoin-core-dev 14:02 -!- Megaf [~quassel@unaffiliated/megaf] has joined #bitcoin-core-dev 14:07 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 14:11 -!- cryptapus [~cryptapus@jupiter.osmus.org] has joined #bitcoin-core-dev 14:11 -!- cryptapus [~cryptapus@jupiter.osmus.org] has quit [Changing host] 14:11 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 14:11 -!- zooko [~user@50.246.213.170] has joined #bitcoin-core-dev 14:12 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 14:21 -!- harrymm [~wayne@223.204.250.103] has quit [Ping timeout: 276 seconds] 14:37 -!- harrymm [~wayne@46.165.228.113] has joined #bitcoin-core-dev 14:46 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 265 seconds] 14:51 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has joined #bitcoin-core-dev 14:54 -!- cryptapus is now known as cryptapus_afk 15:03 -!- Megaf [~quassel@unaffiliated/megaf] has quit [Remote host closed the connection] 15:08 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 15:13 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 15:58 -!- murch1 [~murch@p4FE39453.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 15:58 -!- murch1 [~murch@p4FE39453.dip0.t-ipconnect.de] has quit [Client Quit] 15:59 -!- murch [~murch@p4FE3905D.dip0.t-ipconnect.de] has quit [Ping timeout: 244 seconds] 16:10 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 16:15 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 16:16 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 16:22 -!- harrymm [~wayne@46.165.228.113] has quit [Ping timeout: 252 seconds] 16:42 -!- harrymm [~wayne@178.162.199.116] has joined #bitcoin-core-dev 16:53 -!- jujumax [~jujumax@host75.190-224-145.telecom.net.ar] has quit [Remote host closed the connection] 16:54 -!- JZA [JZA@gateway/shell/elitebnc/x-bepspuqyusiwnazv] has quit [Excess Flood] 17:08 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 17:09 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 17:11 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 17:13 -!- Giszmo [~leo@2001:a61:32cf:d301:d12d:6d17:d34c:ed36] has quit [Ping timeout: 250 seconds] 17:16 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 17:20 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has quit [Quit: Leaving.] 17:21 -!- JZA [JZA@gateway/shell/elitebnc/x-hntxrhbikwqnmkrt] has joined #bitcoin-core-dev 17:40 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 17:41 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 17:55 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 240 seconds] 17:57 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 18:26 -!- JackH [~Jack@79-73-188-45.dynamic.dsl.as9105.com] has quit [Ping timeout: 252 seconds] 18:35 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-zufvamgzmcwprtqu] has quit [Quit: Connection closed for inactivity] 18:37 -!- Samdney [~Samdney@dyn-ant666999.hawo.ipv6.uni-erlangen.de] has quit [Ping timeout: 258 seconds] 18:55 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 18:56 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 19:33 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 19:33 -!- cryptapus_afk [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 240 seconds] 19:33 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 19:33 -!- cryptapus is now known as cryptapus_afk 19:34 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 19:44 -!- Samdney [~Samdney@dyn-ant666999.hawo.ipv6.uni-erlangen.de] has joined #bitcoin-core-dev 20:01 -!- Samdney [~Samdney@dyn-ant666999.hawo.ipv6.uni-erlangen.de] has quit [Ping timeout: 258 seconds] 20:03 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 20:04 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 20:04 -!- zooko [~user@50.246.213.170] has quit [Ping timeout: 252 seconds] 20:13 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 244 seconds] 20:16 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 258 seconds] 20:47 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 20:48 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 20:58 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 20:59 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 21:09 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 21:10 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 21:23 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 21:24 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 21:34 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 21:35 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 21:43 -!- kadoban [~mud@unaffiliated/kadoban] has quit [Quit: bye] 22:09 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 22:10 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 22:46 -!- wangchun [~wangchun@li414-193.members.linode.com] has quit [Quit: leaving] 22:47 -!- wangchun [~wangchun@li414-193.members.linode.com] has joined #bitcoin-core-dev 23:00 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 23:01 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 23:27 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 23:49 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]