--- Day changed Sat Oct 29 2016 00:02 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 00:03 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 00:29 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 260 seconds] 00:33 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev 00:51 -!- LeMiner [LeMiner@unaffiliated/leminer] has quit [Read error: Connection reset by peer] 01:22 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 02:03 -!- nibor [~nibor@185.9.34.66] has quit [Quit: Leaving] 02:34 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 245 seconds] 02:39 -!- Bi [~Bi@31-179-199-111.kamnet.pl] has joined #bitcoin-core-dev 02:47 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ofgqmlgnxyybecno] has joined #bitcoin-core-dev 02:59 < Bi> Guys, if I have a block with only the coinbase tx and one segwit tx. It takes sha256->sha256 on 64 bytes of data to calculate the witness' merkle - right? 02:59 < Bi> And the first 32 bytes are zero? 03:00 < Bi> While the other 32 bytes is sha256->sha256 of the raw segwit transaction? 03:01 < Bi> It seems very simple, but I must be doing something wrong, beacuse my merkle roots dont match the expected values 03:02 < Bi> Can someone please help me? 03:07 < Bi> Or maybe you could at leat tell me what is wtxid of this transaction: 01000000000101f15a2db447e8316e9f20073ab8bdeac53df1a53d415fbd41e73929699b889e7a0000000017160014fb459699ce9ca78de6d0790121dfb215883acb64ffffffff0100111024010000001976a914fb459699ce9ca78de6d0790121dfb215883acb6488ac02483045022100c5feadba5fbcc28afb940c7ee664bba81830f19a5407ae49cf75f565534b149702200a7c2b6b1b5846a37c434ffe0cae168d6b797de9087a21176f2c9ef6fa9f47aa014104b848ab6ac853cd 03:07 < Bi> 69baaa750c70eb352ebeadb07da0ff5bbd642cb285895ee43f2889dd12642ca0ff9b2489bd82d4d5ca287c4ebdf509f1bcd02d6fa720542e2900000000 03:08 < Bi> it is from this block: https://testnet.blockexplorer.com/block/0000000000000009fdda232a7dfb09682aeb35e04d1437b4ed6a08e9abb479e0 03:17 -!- rebroad [~rebroad@183.89.25.98] has quit [Ping timeout: 245 seconds] 03:34 < Victorsueca> Bi: your transaction is supposed to have 2 IDs, the txid as it has always been and the new wtxid 03:34 < Victorsueca> the txid should be sha256(sha256(original serialization format)) 03:35 < Victorsueca> the wtxid should be sha256(sha256(new serialization format with witness data)) 03:36 < Victorsueca> if your transaction does not have any witness data the txid and the wtxid should be the same 03:41 < Bi> Victorsueca, yes I know all of this 03:42 < Bi> Bu my merkle roots dont match :( 03:42 < Victorsueca> hmmmm 03:43 < Bi> If someone could give me the expected wtxid for the given raw transaction? 03:49 < Victorsueca> weird.... can't decode your hex string using decoderawtransaction 03:49 < Victorsueca> also tried blockchain.info transaction parses but I wouldn't be surprised if that failed anyway 03:50 < arubi> the transaction is fine 03:50 < Bi> This is segwit transaction 03:50 < Bi> it decodes properly here: http://n.bitcoin.ninja/checktx 03:50 < Bi> It is a real tx from testent block #895231 03:51 < Victorsueca> why does bitcoin-cli decoderawtransaction not work then? 03:51 < Bi> I dont know 03:51 < arubi> it works for me.. 03:52 < Bi> Make sure to remove all the spaces 03:52 < Victorsueca> ahhh yeah 03:52 < Bi> So what is its wtxid? 03:52 < Victorsueca> IRC added a line jump, forgot about that 03:54 < arubi> Bi, as reported by bitcoin-cli, it's 508e4409c2cdff3d08b54370147cf6bf4d328f8248e4c60941a528b4d0375159 . not sure how much that'll help you 03:54 < Bi> ok, thank you - I have the same one 03:54 -!- fengling [~fengling@106.114.12.78] has joined #bitcoin-core-dev 03:54 < Bi> But then it doesnt create a correct merkle hash 03:55 < Bi> if you look into this block: https://testnet.blockexplorer.com/block/0000000000000009fdda232a7dfb09682aeb35e04d1437b4ed6a08e9abb479e0 03:55 < arubi> I am 03:55 < Bi> ... it expects segwit merkle root of 554949ea7454928f42158d3554817f70c1fa8ba75e769faa58128ac05d333d28 03:56 < arubi> looks like it, right. hopefully the hash in the op_return output is actually reversed like you say.. I'm not sure 03:56 < Bi> and when you hash null hash (wtxid of coinbase) followed by this 508e4409c2cdff3d08b54370147cf6bf4d328f8248e4c60941a528b4d0375159 - I get something else 03:57 < Bi> I was trying swapping and not swapping - no success :( 03:58 < Victorsueca> Bi: here's your transaction in JSON format https://softnet.homenet.org/zerobin/?11d833ece4506b4e#IYNmeQ7+/uvT/uZUW6TbikcrQus5TJa8AJruObsa3bY= 03:58 < arubi> but what's in that return output is not just the wtxid merkle root 03:58 < Victorsueca> and here's your block in JSON https://softnet.homenet.org/zerobin/?4e1d5fd2c883f51c#BKcO0qKshmbruiyexoJltMZIMqf4p7OMbzch05rnkQA= 03:58 < Victorsueca> jus queried those from my node 03:58 < arubi> the merkle root is appended the witness reserved value and then hashed hash256 again 03:59 < Bi> oh? 03:59 < Bi> is it? 03:59 < arubi> at least that's what I gathered from bip141 03:59 < Bi> No, it says "A witness root hash is calculated with all those wtxid as leaves, in a way similar to the hashMerkleRoot in the block header." 03:59 < arubi> right, and then... 04:00 < arubi> Double-SHA256(witness root hash|witness reserved value 04:00 < arubi> ) 04:01 < Bi> right - thank you! 04:01 < Bi> this must be it 04:01 < arubi> also, pretty sure that at least with the wtxid I gave you, you /should/ reverse the bytes. and also treat the bytes like they are in the commitment hash 04:01 < arubi> (so not reversed like you pasted) 04:02 < Bi> yes, reversing I knew about 04:02 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 04:02 < Bi> Double-SHA256(witness root hash|witness reserved value) - was the part I missed 04:02 < Bi> thanks again 04:02 < arubi> cheers Bi 04:05 < Bi> Yes, it works no! 04:05 < Bi> Cheers 04:05 < arubi> yep, tried it too :) 04:05 < Bi> now* 04:15 -!- DigiByteDev [~JT2@n218250011174.netvigator.com] has quit [Quit: DigiByteDev] 04:17 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 04:30 -!- Bi [~Bi@31-179-199-111.kamnet.pl] has quit [Quit: Leaving] 04:30 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 250 seconds] 04:32 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 04:36 -!- JackH [~laptop@79-73-190-13.dynamic.dsl.as9105.com] has quit [Ping timeout: 265 seconds] 05:02 -!- fengling [~fengling@106.114.12.78] has quit [Ping timeout: 268 seconds] 05:10 -!- JackH [~laptop@37.157.48.150] has joined #bitcoin-core-dev 05:11 -!- dermoth [~thomas@dsl-66-36-159-136.mtl.aei.ca] has joined #bitcoin-core-dev 05:26 -!- molz is now known as moli 05:41 -!- fengling [~fengling@106.114.12.78] has joined #bitcoin-core-dev 06:04 -!- e4xit_ [~e4xit@cpc92302-cmbg19-2-0-cust1369.5-4.cable.virginm.net] has joined #bitcoin-core-dev 06:05 -!- e4xit [~e4xit@cpc92302-cmbg19-2-0-cust1369.5-4.cable.virginm.net] has quit [Ping timeout: 260 seconds] 06:05 -!- e4xit_ is now known as e4xit 06:17 -!- fengling [~fengling@106.114.12.78] has quit [Ping timeout: 268 seconds] 06:19 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 268 seconds] 06:23 -!- JackH [~laptop@37.157.48.150] has quit [Ping timeout: 250 seconds] 06:23 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev 06:23 -!- JackH [~laptop@37.157.48.150] has joined #bitcoin-core-dev 06:38 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds] 06:47 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 07:07 -!- tonikt [~tonikt@31-179-199-111.kamnet.pl] has joined #bitcoin-core-dev 07:13 -!- tonikt [~tonikt@31-179-199-111.kamnet.pl] has quit [Changing host] 07:13 -!- tonikt [~tonikt@unaffiliated/tonikt] has joined #bitcoin-core-dev 07:16 < tonikt> Is the presence of the witness root field (in the coinbase output) mandatory, after SEGWIT activation? 07:17 < tonikt> (assuming there are any segwit txs inside the block) 07:19 < tonikt> Sorry, I found it. It's the "unexpected-witness" code :) 07:29 -!- JackH [~laptop@37.157.48.150] has quit [Ping timeout: 250 seconds] 07:33 -!- rebroad [~rebroad@node-14s8.pool-118-173.dynamic.totbb.net] has joined #bitcoin-core-dev 07:49 -!- LeMiner [LeMiner@unaffiliated/leminer] has joined #bitcoin-core-dev 08:01 < sipa> tonikt: not, not mandatoy 08:03 < tonikt> sipa: I think it becomes mandatory, after the activation. 08:03 < tonikt> yes? 08:05 < tonikt> .. it would go to "if (!fHaveWitness) ..." in ContextualCheckBlock() 08:06 < tonikt> .. and then it would find a tx with segwit, and then it would return error "unexpected-witness" 08:19 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 250 seconds] 08:22 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 08:44 < Victorsueca> tonikt: non-segwit blocks are supposed to still be valid even after activation 09:05 < tonikt> Sure. I was just wondering, after the activation, whether I have to reject blocks without the segwit root 09:05 < tonikt> It seemed logical to reject them, but could not find that part of code 09:11 < sipa> tonikt: no, if no transaction contains a witness, there is no requirement for a witness commitment 09:12 < tonikt> yes - only if there is at least one witness transaction 09:12 < sipa> of course 09:12 < sipa> then it is mandatory 09:12 < tonikt> but I think it also counts coinbase transaction as a possible witness-type? 09:15 < tonikt> I have another, more high-level question... 09:15 < tonikt> I am on testnet network now and trying to sync up the chain and all my current peers are pre 0.13.0 09:16 < tonikt> And I am already on block #893669 09:16 < sipa> tonikt: the coinbase witness is not committed to anywhere excet by the commitment in the output 09:16 < tonikt> I should not be taking any block data from these peers, should I? 09:16 < sipa> tonikt: which means that if you don't have a commitment, you can just remove the coinbase witness 09:17 < sipa> without invalidating anything 09:17 < sipa> we only download blocks from witness peers, indeed 09:17 -!- dermoth [~thomas@dsl-66-36-159-136.mtl.aei.ca] has quit [Ping timeout: 260 seconds] 09:18 < tonikt> sipa: OK - that's interesting. I forgot that removing the witness from CB would not change txid, so it would still validate the block :) 09:19 < sipa> indeed 09:20 < sipa> if there is no witness commitment, it means that no tx has a witness 09:20 < sipa> including the coinbase 09:20 < tonikt> OK - all clear now 09:20 < tonikt> thanks 09:21 < tonikt> do you know any running testnet node where I could connect to fetch some segwith blocks? 09:21 < tonikt> all my peers are < 0.13.0 now :) 09:22 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 09:22 < sipa> use x9.seed.bitcoin.sipa.be 09:22 < sipa> eh, that's mainnet 09:23 < sipa> for testnet i think jonasschnelli's and petertodd's seed support filtering 09:23 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 09:23 < tonikt> if you have a running node, would you just give me an IP, please? 09:24 < sipa> 37.34.48.17 09:25 < tonikt> thank you! 09:48 -!- zooko [~user@73.93.141.24] has joined #bitcoin-core-dev 10:13 < BlueMatt> uhhhh, preferential peering is quite impressive... https://imgur.com/a/jwH7R 10:18 -!- echonaut1 [~echonaut@46.101.192.134] has quit [Remote host closed the connection] 10:19 -!- echonaut [~echonaut@46.101.192.134] has joined #bitcoin-core-dev 10:35 -!- LeMiner2 [LeMiner@5ED1AFBF.cm-7-2c.dynamic.ziggo.nl] has joined #bitcoin-core-dev 10:37 -!- JackH [~laptop@79-73-190-13.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev 10:38 -!- LeMiner [LeMiner@unaffiliated/leminer] has quit [Ping timeout: 260 seconds] 10:38 -!- LeMiner2 is now known as LeMiner 10:42 -!- kadoban [~mud@unaffiliated/kadoban] has joined #bitcoin-core-dev 10:44 < sipa> BlueMatt: 174 connections here 10:50 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds] 10:51 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 11:02 -!- tonikt [~tonikt@unaffiliated/tonikt] has quit [Quit: Leaving] 11:14 < Victorsueca> used to have 70-80 peers, I have 121 right now 11:18 < sipa> i temporarily increased my max connections 11:25 < BlueMatt> sipa: i had something like 250 on that node 11:26 < BlueMatt> (with some blacklisting of bad nodes) 11:27 -!- zooko [~user@73.93.141.24] has quit [Ping timeout: 245 seconds] 11:33 < sipa> seems my dns seed has a bug... it's using 400% cpu and is not responding to dns requests 11:34 < sipa> yay for multiple implementations 12:01 -!- dermoth [~thomas@dsl-66-36-159-136.mtl.aei.ca] has joined #bitcoin-core-dev 12:15 * btcdrak forks sipa 12:19 < sipa> fixed, i think 12:21 < sipa> jonasschnelli, petertodd, luke-jr: pushed a bugfix to bitcoin-seeder which could cause infinite loops in the dns handling thread 12:22 < luke-jr> sipa: I'm intentionally holding back my version for a little while just to avoid us all using the same code immediately 12:22 < luke-jr> is it an exploit, or am I probably okay? 12:22 < sipa> luke-jr: you're probably already stuck in an infinite loop 12:23 < sipa> is the 'DNS requests' number going up? 12:23 < luke-jr> CPU is 100% idle, so I doubt it? 12:23 < luke-jr> yes 12:23 < sipa> indeed, then i doubt it 12:23 < luke-jr> [16-10-29 19:23:24] 591/5717464 available (5713103 tried in 132614s, 3081 new, 1280 active), 4288200 banned; 1851875 DNS requests, 316442 db queries 12:23 < sipa> did you upgrade to have filtering support? 12:24 < luke-jr> -rw-r--r-- 1 bitcoinpool bitcoinpool 849M Oct 29 18:49 dnsseed.dat <-- is this right? O.o 12:24 < luke-jr> no 12:24 < luke-jr> (the size) 12:25 < sipa> with 11M addresses in your database, i guess yes 12:25 < sipa> the question is why do you have so many addresses in there 12:25 < sipa> i have 2.5M 12:26 < luke-jr> plaintext dump is only 117 MB 12:26 < sipa> the dump doesn't contain banned/terrible IPs 12:27 < luke-jr> would it matter that I dropped crawler threads to 20 for a long time? 12:27 < sipa> 160M -rw-rw-r-- 1 pw pw 160M Oct 29 12:27 dnsseed.dat 54M -rw-r--r-- 1 pw pw 54M Oct 29 12:27 dnsseed.dump 12:28 < sipa> it seems you're spending a huge amount of time retrying IPs that are gone 12:28 < sipa> your node needs 2 days to cycle through everything 12:28 < sipa> it's 15 minutes here 12:28 < luke-jr> :o 12:28 < luke-jr> I guess variety is worth the overhead? 12:29 < sipa> i would say so 12:29 < sipa> but i'd still like to understand why yours behaves so differently from mine 12:30 < luke-jr> only difference in mine from 11e935b72020607e5c3ce85a88209bc34e427a06 is REQUIRE_VERSION 70001 12:30 < luke-jr> ./dnsseed -h dnsseed.bitcoin.dashjr.org -n jun.dashjr.org -p 1053 -t 80 12:32 < luke-jr> sipa: some years ago, my server was blackholed semi-regularly for a while due to an upstream/backbone router hating the crawler's access patterns; could blackholing do it? 12:33 < luke-jr> ie, maybe it thinks all IPs are sometimes terrible 12:33 < sipa> you only have 591 good IPs 12:34 < sipa> i have 4000 12:34 < sipa> wow, only 3000 suddenly... perhaps due to being offline for a while as a result of that bug 12:34 < sipa> usually it's around 4000 12:39 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 260 seconds] 12:43 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev 12:54 -!- mkarrer [~mkarrer@128.red-83-47-106.dynamicip.rima-tde.net] has quit [] 13:04 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 250 seconds] 13:08 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev 13:18 -!- aalex [~aalex@64.187.177.58] has quit [Max SendQ exceeded] 13:19 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev 13:53 -!- moli [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer] 14:19 -!- juscamarena [~jus@47.148.176.74] has joined #bitcoin-core-dev 14:20 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 14:26 -!- AtashiCon [arnavion@unaffiliated/arnavion] has quit [Quit: AtashiCon] 14:41 -!- AtashiCon [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev 14:50 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 265 seconds] 14:50 -!- DigiByteDev [~JT2@n218250011174.netvigator.com] has joined #bitcoin-core-dev 14:50 -!- DigiByteDev [~JT2@n218250011174.netvigator.com] has quit [Client Quit] 14:52 -!- echonaut2 [~echonaut@46.101.192.134] has joined #bitcoin-core-dev 14:53 -!- echonaut [~echonaut@46.101.192.134] has quit [Remote host closed the connection] 14:53 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev 14:53 -!- echonaut [~echonaut@46.101.192.134] has joined #bitcoin-core-dev 14:54 -!- echonaut2 [~echonaut@46.101.192.134] has quit [Remote host closed the connection] 14:57 -!- JackH [~laptop@79-73-190-13.dynamic.dsl.as9105.com] has quit [Ping timeout: 244 seconds] 15:03 -!- PaulCapestany [~PaulCapes@2604:5500:17:2ea:70ff:a4d5:8d0d:8cf3] has quit [Read error: Connection reset by peer] 15:04 -!- PaulCapestany [~PaulCapes@2604:5500:17:2ea:543e:871d:cfcf:dda6] has joined #bitcoin-core-dev 15:06 -!- helo [~helo@unaffiliated/helo] has quit [Ping timeout: 245 seconds] 15:07 -!- helo [~helo@unaffiliated/helo] has joined #bitcoin-core-dev 15:09 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Read error: Connection reset by peer] 16:06 -!- cdecker [~quassel@2a02:aa16:1105:4a80:d552:a356:122b:b11d] has quit [Ping timeout: 260 seconds] 16:15 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 16:18 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 260 seconds] 16:23 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 16:25 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has quit [Remote host closed the connection] 16:26 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has joined #bitcoin-core-dev 16:26 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 260 seconds] 16:29 -!- rebroad [~rebroad@node-14s8.pool-118-173.dynamic.totbb.net] has quit [Ping timeout: 250 seconds] 16:41 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 245 seconds] 16:48 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 16:50 -!- fengling [~fengling@110.241.61.9] has joined #bitcoin-core-dev 16:59 -!- cryptapus_afk is now known as cryptapus 17:01 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 17:04 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 17:10 -!- fengling [~fengling@110.241.61.9] has quit [Ping timeout: 268 seconds] 17:15 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds] 17:43 -!- justan0theruser is now known as justanother|CHC 17:47 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-wahkdadkfteibdna] has quit [Quit: Connection closed for inactivity] 18:03 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 18:05 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Read error: Connection reset by peer] 18:06 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 245 seconds] 18:06 -!- cryptapus [~cryptapus@jupiter.osmus.org] has joined #bitcoin-core-dev 18:06 -!- cryptapus [~cryptapus@jupiter.osmus.org] has quit [Changing host] 18:06 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 18:06 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has joined #bitcoin-core-dev 18:25 -!- fengling [~fengling@110.249.253.246] has joined #bitcoin-core-dev 18:50 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ofgqmlgnxyybecno] has quit [Quit: Connection closed for inactivity] 18:54 -!- fengling [~fengling@110.249.253.246] has quit [Ping timeout: 268 seconds] 19:41 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 19:44 -!- justanother|CHC [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds] 20:58 -!- rebroad [~rebroad@1.46.236.157] has joined #bitcoin-core-dev 21:04 -!- cryptapus is now known as cryptapus_afk 21:13 -!- rebroad [~rebroad@1.46.236.157] has quit [Ping timeout: 250 seconds] 21:24 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 260 seconds] 21:26 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 21:28 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev 21:28 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 21:55 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 21:56 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 22:12 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has quit [Quit: Leaving.] 22:35 -!- juscamarena [~jus@47.148.176.74] has quit [Read error: Connection reset by peer] 22:36 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-ykxndtzmafgwcdny] has joined #bitcoin-core-dev 23:31 -!- wasi [~wasi@183.12.202.62.static.wline.lns.sme.cust.swisscom.ch] has joined #bitcoin-core-dev 23:33 -!- rebroad [~rebroad@1.46.236.157] has joined #bitcoin-core-dev