--- Log opened Fri Aug 10 00:00:35 2018 00:00 -!- Jmabsd [~jmabsd@pcd247152.netvigator.com] has quit [Ping timeout: 240 seconds] 00:02 -!- rootsudo [~textual@49.151.151.68] has joined #bitcoin-core-dev 00:05 -!- Jmabsd [~jmabsd@pcd247152.netvigator.com] has joined #bitcoin-core-dev 00:17 < sipa> Jmabsd: maybe 00:17 < sipa> you'll need to ask the system's creator :) 00:18 < Jmabsd> sipa: ah. easy peasy. what's this gmx.de email again. :)) 00:18 < sipa> i like to think of the scriptPubKey as the pubkey for a higher level cryptographic signature system called script 00:18 < Jmabsd> anyhow i guess that is a very rational understanding for the original motivation to the nomenclature. 00:19 < sipa> and the scriptSig is the signature to that scheme 00:19 < Jmabsd> ah! 00:19 < Jmabsd> ah interesting, makes sense! 00:19 < sipa> i have no idea if that's the name's origin, however 00:25 < Jmabsd> are we in a place today where you can assume that every relevant participant in the Bitcoin ecosystem will be fine with Bitcoin transactions with version = 2? 00:26 < Jmabsd> i'd guess so, though legacy seems to be version 1. i didn't check statistics for what's actually in blocks today. 00:44 < sipa> ? 00:47 < sipa> v2 was introduced by bip 112 00:49 < sipa> i'm not sure what you mean by "will be fine" 01:00 < Jmabsd> sipa: of what effect in the real world is the version number attached to _transactions_ 01:00 < Jmabsd> (BIP 112 relates to block version not tx version) 01:01 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:07 < sipa> Jmabsd: no, tx version 01:07 < sipa> Jmabsd: block version 2 was assigned a meaning in bip 34 01:08 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 01:09 < Jmabsd> sipa: ah, i can't find the word "version" allude to transaction version anywhere in BIP 112, what did I miss? sorry if this is too obvious, if so derp. 01:10 < sipa> bip 68 too 01:11 < sipa> bip 112 includes the text "transaction version less than 2" 01:11 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 01:11 < sipa> bip 68 includes "This specification defines the meaning of sequence numbers for transactions with an nVersion greater than or equal to 2 for which the rest of this specification relies on. 01:11 < sipa> " 01:13 < sipa> Jmabsd: i think your questions are probably better suited for bitcoin.stackexchange.com 01:14 < sipa> this channel is mostly about developmemt of the bitcoin core software 01:29 -!- itaseski [~itaseski@213.135.176.196] has joined #bitcoin-core-dev 01:42 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:383f:2670:fea3:68c2] has quit [Remote host closed the connection] 01:52 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 01:54 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 02:00 -!- rls [~rls@104.250.122.134] has quit [Remote host closed the connection] 02:08 -!- rls [~rls@104.250.122.134] has joined #bitcoin-core-dev 02:10 -!- rls [~rls@104.250.122.134] has quit [Read error: Connection reset by peer] 02:21 < jonasschnelli> should calculating the ecdh secret be done the secp256k1 sign or on the verify context? Or does it even matter? 02:21 -!- rootsudo [~textual@49.151.151.68] has quit [Ping timeout: 244 seconds] 02:21 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 02:30 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:5917:3426:1288:e72b] has joined #bitcoin-core-dev 02:34 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:5917:3426:1288:e72b] has quit [Ping timeout: 240 seconds] 02:35 -!- rls [~rls@2600:8800:4b80:ed60:541a:acad:7e12:67fe] has joined #bitcoin-core-dev 02:39 -!- rls [~rls@2600:8800:4b80:ed60:541a:acad:7e12:67fe] has quit [Ping timeout: 245 seconds] 02:42 -!- harrigan [~harrigan@skynet.skynet.ie] has joined #bitcoin-core-dev 02:45 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 02:46 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 02:47 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 02:48 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 02:51 -!- ryanofsky [russ@jumpy.yanofsky.org] has quit [Quit: ZNC 1.7.0 - https://znc.in] 02:52 -!- ryanofsky [russ@jumpy.yanofsky.org] has joined #bitcoin-core-dev 03:00 -!- rls [~rls@2600:8800:4b80:ed60:e068:fa7d:4286:37e4] has joined #bitcoin-core-dev 03:04 -!- rls [~rls@2600:8800:4b80:ed60:e068:fa7d:4286:37e4] has quit [Ping timeout: 240 seconds] 03:05 -!- rls [~rls@2600:8800:4b80:ed60:e068:fa7d:4286:37e4] has joined #bitcoin-core-dev 03:10 -!- rls [~rls@2600:8800:4b80:ed60:e068:fa7d:4286:37e4] has quit [Ping timeout: 260 seconds] 03:19 < ken2812221> I wonder why the linter failed? https://travis-ci.org/bitcoin/bitcoin/jobs/414449333 03:24 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:bd57:9a9c:18ba:7af5] has joined #bitcoin-core-dev 03:28 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:bd57:9a9c:18ba:7af5] has quit [Ping timeout: 240 seconds] 03:29 < aj> ken2812221: probably doesn't like the , in the template syntax? foo 03:33 < ken2812221> aj: thanks, might need to fix this linter bug. 03:41 -!- rls [~rls@ip98-171-84-127.ph.ph.cox.net] has joined #bitcoin-core-dev 03:46 -!- rls [~rls@ip98-171-84-127.ph.ph.cox.net] has quit [Ping timeout: 256 seconds] 03:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 03:49 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 04:14 < provoostenator> Re preciousblock RPC: "Treats a block as if it were received before others with the same work", what exactly is meant with "same work"? 04:17 < provoostenator> Is "work" defined as delta blockheight times current difficulty level? 04:43 -!- face [~face@80.72.82.160.coresnet.bg] has quit [Read error: Connection reset by peer] 04:48 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has quit [Quit: May the Shwartz be with you] 04:49 -!- michaelsdunn1 [~michaelsd@208.59.170.5] has joined #bitcoin-core-dev 04:51 -!- nodweber [~nodweber@unaffiliated/nodweber] has joined #bitcoin-core-dev 04:58 -!- nodweber [~nodweber@unaffiliated/nodweber] has quit [Quit: WeeChat 2.2] 04:59 -!- nodweber [~nodweber@unaffiliated/nodweber] has joined #bitcoin-core-dev 04:59 -!- nodweber [~nodweber@unaffiliated/nodweber] has quit [Client Quit] 04:59 -!- nodweber [~nodweber@unaffiliated/nodweber] has joined #bitcoin-core-dev 05:01 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 05:06 -!- promag [~promag@83.223.224.123] has joined #bitcoin-core-dev 05:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 05:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 05:54 -!- michaelsdunn1 [~michaelsd@208.59.170.5] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…] 06:21 -!- promag [~promag@83.223.224.123] has quit [Remote host closed the connection] 06:29 < instagibbs> provoostenator, blocks * difficulty level, or there abouts yes. So with a one block fork it will always select the one your preciousblocked 06:29 < provoostenator> instagibbs: thanks 06:47 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 06:48 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 06:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 07:00 -!- fnb_theory [~fnb_theor@138.68.70.40] has quit [Ping timeout: 265 seconds] 07:14 -!- Jmabsd [~jmabsd@pcd247152.netvigator.com] has quit [Ping timeout: 240 seconds] 07:25 -!- ExtraCrispy [~ExtraCris@185.9.18.150] has quit [Remote host closed the connection] 07:30 < gmaxwell> provoostenator: well not quite, because the forks could have different difficulty levels. 07:32 -!- var-g_ [~ayy@unaffiliated/var-g] has quit [Quit: WeeChat 2.1] 07:44 < provoostenator> So if the fork happened in the current difficulty period, then block height delta is all you need. But otherwise you need to take the surface area under difficulty x height chart. 07:48 < gmaxwell> right. 07:48 < gmaxwell> though thats kind of overcomplicating it. The software already tracks that 'area' for every block (by adding up the reverse of the targets). 07:49 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 07:49 < provoostenator> I know, I'm trying to visualize it. 07:49 < provoostenator> I know, I'm trying to visualize it. 07:58 -!- ken2812221 [~User@1.200.203.30] has quit [Ping timeout: 240 seconds] 08:08 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 08:39 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has quit [Read error: Connection reset by peer] 08:41 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 08:46 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has joined #bitcoin-core-dev 09:01 -!- jhfrontz [~Adium@50-193-59-58-static.hfc.comcastbusiness.net] has quit [Quit: Leaving.] 09:09 -!- rls [~rls@ip98-171-84-127.ph.ph.cox.net] has joined #bitcoin-core-dev 09:13 -!- rls [~rls@ip98-171-84-127.ph.ph.cox.net] has quit [Ping timeout: 256 seconds] 09:19 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Read error: Connection reset by peer] 09:19 -!- queip [~queip@unaffiliated/rezurus] has quit [Quit: bye, freenode] 09:26 < MarcoFalke> PSA: Don't merge to master until the travis issues are resolved. I just recently purged all caches to fix some issues and would like to avoid further cache corruption. 09:26 < MarcoFalke> https://www.traviscistatus.com/incidents/pxj3py3xzn14 09:51 -!- jhfrontz [~Adium@c-24-4-39-8.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 09:54 -!- jhfrontz [~Adium@c-24-4-39-8.hsd1.ca.comcast.net] has quit [Client Quit] 09:56 < provoostenator> I can use a sanity check on my reasoning in #13930 (bottom comment) by someone who thoroughly understands how blocks are connected and/or invalidated. 09:56 < gribble> https://github.com/bitcoin/bitcoin/issues/13930 | Better explain GetAncestor check for m_failed_blocks in AcceptBlockHeader by Sjors · Pull Request #13930 · bitcoin/bitcoin · GitHub 09:56 -!- jhfrontz [~Adium@c-24-4-39-8.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 10:21 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 10:22 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:d0b8:dede:3d3:52d3] has joined #bitcoin-core-dev 10:23 <@sdaftuar> provoostenator: that looks correct to me 10:26 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:d0b8:dede:3d3:52d3] has quit [Ping timeout: 265 seconds] 10:30 -!- jhfrontz [~Adium@c-24-4-39-8.hsd1.ca.comcast.net] has quit [Quit: Leaving.] 10:33 -!- setpill [~setpill@unaffiliated/setpill] has quit [Ping timeout: 256 seconds] 10:36 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 10:36 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:394f:9565:5009:f079] has joined #bitcoin-core-dev 10:36 -!- jhfrontz [~Adium@c-24-4-39-8.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 10:50 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:394f:9565:5009:f079] has quit [Ping timeout: 245 seconds] 10:53 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:8d03:4c2f:4ad9:a300] has joined #bitcoin-core-dev 10:55 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 10:59 -!- masonicb_ [~masonicbo@2600:8802:5501:17c0:1f:20d2:85fb:343c] has joined #bitcoin-core-dev 11:01 -!- masonicb_ [~masonicbo@2600:8802:5501:17c0:1f:20d2:85fb:343c] has quit [Client Quit] 11:01 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:8d03:4c2f:4ad9:a300] has quit [Ping timeout: 240 seconds] 11:16 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 11:21 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has quit [Ping timeout: 260 seconds] 11:23 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 11:26 -!- jhfrontz [~Adium@c-24-4-39-8.hsd1.ca.comcast.net] has quit [Quit: Leaving.] 11:28 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 11:30 -!- jhfrontz [~Adium@c-24-4-39-8.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 11:44 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 11:47 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 12:08 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.1] 12:14 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 12:17 -!- promag [~promag@83.223.226.3] has joined #bitcoin-core-dev 12:17 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #bitcoin-core-dev 12:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 12:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 12:30 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 12:30 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 12:32 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 12:46 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 12:47 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 12:51 -!- promag [~promag@83.223.226.3] has quit [Remote host closed the connection] 13:09 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 13:12 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 13:13 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 13:15 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 240 seconds] 13:17 -!- mode/#bitcoin-core-dev [-o sdaftuar] by sdaftuar 13:18 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer] 13:21 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Ping timeout: 244 seconds] 13:25 -!- grubles [~grubles@unaffiliated/grubles] has joined #bitcoin-core-dev 13:31 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 13:32 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 13:34 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 13:35 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 13:45 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #bitcoin-core-dev 13:46 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 13:48 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 13:52 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 13:53 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 13:58 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 13:58 -!- MrPaz [~PazPazPaz@84.39.112.91] has joined #bitcoin-core-dev 14:01 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 14:07 -!- jhfrontz [~Adium@c-24-4-39-8.hsd1.ca.comcast.net] has quit [Quit: Leaving.] 14:13 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 14:14 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 14:26 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 14:32 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 14:40 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 14:41 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 14:54 -!- Dizzle [~dizzle@108.171.182.16] has quit [Ping timeout: 244 seconds] 14:54 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 14:56 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 14:59 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 15:01 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 15:01 -!- itaseski [~itaseski@213.135.176.196] has quit [Ping timeout: 240 seconds] 15:18 -!- ken2812221 [~User@1.200.203.30] has joined #bitcoin-core-dev 15:39 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 15:40 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Quit: Leaving] 15:40 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 15:49 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 16:03 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Quit: Leaving] 16:10 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 16:16 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 16:42 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has quit [Ping timeout: 244 seconds] 16:54 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 17:05 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 17:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 17:06 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 17:06 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 17:07 -!- farmerwampum [~farmerwam@104.129.28.58] has quit [Ping timeout: 256 seconds] 17:20 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 17:26 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 17:30 -!- IGHOR [~quassel@93.178.216.72] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.] 17:33 -!- IGHOR [~quassel@93.178.216.72] has joined #bitcoin-core-dev 17:50 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [Ping timeout: 240 seconds] 17:55 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 17:55 -!- BashCo_ [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 18:02 -!- anome [~anome@unaffiliated/anome] has quit [] 18:17 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 18:20 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 18:47 < gmaxwell> [ot followup] ossifrage: Their blinking patent filings more or less confirm it was an intentional backdoor: http://i.blackhat.com/us-18/Thu-August-9/us-18-Domas-God-Mode-Unlocked-Hardware-Backdoors-In-x86-CPUs.pdf 18:47 -!- DylanM21 [~dm21@2601:404:c680:6ac0:2d69:b7ee:dc09:9e3c] has joined #bitcoin-core-dev 19:06 -!- Krellan_ [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 19:06 -!- Krellan_ [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Remote host closed the connection] 19:09 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Ping timeout: 240 seconds] 19:37 -!- DylanM21 [~dm21@2601:404:c680:6ac0:2d69:b7ee:dc09:9e3c] has quit [] 20:28 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 20:29 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 20:56 -!- MrPaz [~PazPazPaz@84.39.112.91] has quit [Ping timeout: 240 seconds] 21:07 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 21:08 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 21:16 -!- Jmabsd [~jmabsd@pcd247152.netvigator.com] has joined #bitcoin-core-dev 21:21 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 21:23 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 21:33 -!- phwalkr [~phwalkr@2001:1284:f022:523f:7035:946:8938:5fc6] has joined #bitcoin-core-dev 22:00 -!- Jaring [~www@58.26.105.162] has joined #bitcoin-core-dev 22:00 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 22:01 -!- Jaring [~www@58.26.105.162] has left #bitcoin-core-dev [] 22:02 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 22:09 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 22:12 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 23:19 -!- itaseski [~itaseski@213.135.176.202] has joined #bitcoin-core-dev --- Log closed Sat Aug 11 00:00:36 2018