--- Log opened Wed Dec 12 00:00:05 2018 --- Day changed Wed Dec 12 2018 00:00 -!- grubles [~grubles@unaffiliated/grubles] has joined #bitcoin-core-dev 00:02 < provoostenator> For signing stuff on your local machine (instead of inside the VM) and pushing to Github, this maybe useful: https://github.com/bitcoin-core/docs/issues/18#issue-292936112 00:10 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Ping timeout: 246 seconds] 00:15 -!- Krellan [~Krellan@2601:640:4000:a876:7482:2f62:4625:a69b] has joined #bitcoin-core-dev 00:15 -!- Krellan [~Krellan@2601:640:4000:a876:7482:2f62:4625:a69b] has quit [Remote host closed the connection] 00:18 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 00:20 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 00:20 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 00:20 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 00:20 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 00:20 < wumpus> provoostenator: I think the idea to use the gitian-builder from the branch you're building 00:21 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: No route to host] 00:22 < provoostenator> The currently instructions tell you to copy gitian-builder during the setup phase, but are unclear on what to do after. Always using the one from the release branch makes sense. 00:23 < provoostenator> Maybe it should do a diff against bitcoin/contrib/gitian-builder.py after it checks out the branch and then prompt the user. 00:24 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-jiyynovruuhpcytm] has joined #bitcoin-core-dev 00:24 < bitcoin-git> [bitcoin] hebasto closed pull request #14905: scripted-diff: Replace deprecated C headers (master...20181209-replace-c-headers) https://github.com/bitcoin/bitcoin/pull/14905 00:24 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-jiyynovruuhpcytm] has left #bitcoin-core-dev [] 00:32 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Remote host closed the connection] 00:57 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 01:06 -!- nelsonhb [~Instantbi@49.125.46.200] has joined #bitcoin-core-dev 01:09 -!- drexl [~drexl@185.244.212.60] has quit [Remote host closed the connection] 01:09 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-jcseezdagebsocsw] has joined #bitcoin-core-dev 01:09 < bitcoin-git> [bitcoin] Sjors opened pull request #14934: Descriptor expansion cache clarifications (master...2018/12/rename_m_script_arg) https://github.com/bitcoin/bitcoin/pull/14934 01:09 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-jcseezdagebsocsw] has left #bitcoin-core-dev [] 01:25 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:45 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:47 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev 01:49 < promag> hebasto: are you able to test #14573 in windows? 01:49 < gribble> https://github.com/bitcoin/bitcoin/issues/14573 | qt: Add Window menu by promag · Pull Request #14573 · bitcoin/bitcoin · GitHub 01:51 < hebasto> promag: unfortunately, no 01:51 < promag> ok ty 02:04 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev 02:14 < meshcollider> promag: I can test it on windows tomorrow 02:14 < promag> ok cool :) 02:14 < fanquake> meshcollider which version/s? 02:23 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 02:23 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 02:23 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 02:31 -!- shesek` [~shesek@141.226.218.112] has joined #bitcoin-core-dev 02:32 -!- shesek` [~shesek@141.226.218.112] has quit [Read error: Connection reset by peer] 02:32 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 268 seconds] 02:33 -!- shesek` [~shesek@141.226.218.112] has joined #bitcoin-core-dev 02:36 -!- shesek` [~shesek@141.226.218.112] has quit [Read error: Connection reset by peer] 02:37 -!- shesek` [~shesek@141.226.218.112] has joined #bitcoin-core-dev 02:39 < promag> well, regargding 14573, details on windows can be improved in a separate PR to avoid invalidating existing acks 02:40 < meshcollider> fanquake: windows 10 02:44 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:50 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 02:52 -!- shesek` [~shesek@141.226.218.112] has quit [Read error: Connection reset by peer] 02:53 -!- shesek` [~shesek@141.226.218.112] has joined #bitcoin-core-dev 02:55 -!- shesek` [~shesek@141.226.218.112] has quit [Read error: Connection reset by peer] 02:57 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 02:57 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 02:57 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 02:57 -!- miknotauro [~miknotaur@201.114.143.145] has quit [Ping timeout: 240 seconds] 03:21 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: No route to host] 03:22 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 03:22 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 03:22 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 03:28 < wumpus> what's with the appveyor failures? 03:29 < wumpus> oh nm, it's only on some PRs 03:29 < fanquake> more than usual? 03:29 < wumpus> no, I don't think so :< 03:29 < fanquake> Probably just need rebasing after a test fix? 03:34 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 03:35 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 03:35 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 03:35 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 03:53 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 03:54 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:02 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 04:10 < promag> wumpus: nothing related with #14670 right? 04:10 < gribble> https://github.com/bitcoin/bitcoin/issues/14670 | http: Fix HTTP server shutdown by promag · Pull Request #14670 · bitcoin/bitcoin · GitHub 04:10 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 04:10 < wumpus> promag: nope 04:10 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 04:10 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 04:10 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:15 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 04:16 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:21 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 04:22 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:25 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 04:29 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 04:30 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:33 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 04:34 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 04:34 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 04:34 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:35 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:38 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 04:39 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 04:39 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 04:39 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:42 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 04:43 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:46 < fanquake> wumpus I'm happy for 14909 to just go in without the other additions 04:47 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 04:49 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 04:49 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 04:49 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:50 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-zwdmuhivoynjmtpz] has joined #bitcoin-core-dev 04:50 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/ed2a2cebd362...96bde4f01f41 04:50 < bitcoin-git> bitcoin/master b7bee6a fanquake: doc: Update minimum required qt 04:50 < bitcoin-git> bitcoin/master 96bde4f Wladimir J. van der Laan: Merge #14909: doc: Update minimum required Qt... 04:50 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-zwdmuhivoynjmtpz] has left #bitcoin-core-dev [] 04:51 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-cswxktoqspkixfhu] has joined #bitcoin-core-dev 04:51 < bitcoin-git> [bitcoin] laanwj closed pull request #14909: doc: Update minimum required Qt (master...doc-qt-minimum-52) https://github.com/bitcoin/bitcoin/pull/14909 04:51 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-cswxktoqspkixfhu] has left #bitcoin-core-dev [] 04:56 < fanquake> wumpus also happy for #14701 to go in as is 04:56 < gribble> https://github.com/bitcoin/bitcoin/issues/14701 | build: Add CLIENT_VERSION_BUILD to CFBundleGetInfoString by fanquake · Pull Request #14701 · bitcoin/bitcoin · GitHub 04:57 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 05:01 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 05:02 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 05:07 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 05:09 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 05:22 < fanquake> Would be interested to know if there are many/any? users running Bitcoin-Core on Windows Vista. Could use some more input in #14922. 05:22 < gribble> https://github.com/bitcoin/bitcoin/issues/14922 | windows: Set _WIN32_WINNT to 0x0600 (Windows Vista) by ken2812221 · Pull Request #14922 · bitcoin/bitcoin · GitHub 05:23 < fanquake> The 0.17.0.1 release binaries "seem" to work on Vista, but Qt dropped official support in 5.6, so I'd assume it's only a matter of time before they stop working. 05:44 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-qhhziihcsygxinbf] has joined #bitcoin-core-dev 05:44 < bitcoin-git> [bitcoin] practicalswift opened pull request #14935: tests: Test for expected return values when calling functions returning a success code (master...test-return-values) https://github.com/bitcoin/bitcoin/pull/14935 05:44 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-qhhziihcsygxinbf] has left #bitcoin-core-dev [] 05:47 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev 05:48 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 05:51 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 05:55 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 05:55 < timothy> fanquake: Microsoft deprecated support for Vista more than 1 years ago 05:55 < timothy> do you REALLY want to run something like bitcoin on an unsupported OS? 05:55 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 05:56 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Read error: Connection reset by peer] 05:56 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 05:58 < fanquake> timothy nope, which is why I've suggested we increase our minimum supported version of Windows to Windows 7 in 0.18.0 06:00 -!- nelsonhb [~Instantbi@49.125.46.200] has quit [K-Lined] 06:02 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:03 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 06:03 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 06:03 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:09 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:09 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:17 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds] 06:18 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 06:22 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:22 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:30 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 06:30 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Client Quit] 06:30 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 06:36 -!- wxss [~user@81.92.202.29] has joined #bitcoin-core-dev 06:58 < promag> sipa: about #14565 06:58 < gribble> https://github.com/bitcoin/bitcoin/issues/14565 | Overhaul importmulti logic by sipa · Pull Request #14565 · bitcoin/bitcoin · GitHub 06:59 < promag> after this should it have support for "all or nothing" import? 07:02 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Read error: Connection reset by peer] 07:04 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 07:04 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 07:10 < provoostenator> I suggested in the comments to have a warning==error option, which would have that effect, at least for stuff we can detect in advance. 07:12 < provoostenator> No actually it would still be a per entry thing. 07:14 < promag> right 07:17 < promag> let me rephrase my question, after 14565, should we _add_ support for "all or nothing"? 07:19 < wumpus> fanquake: probably better to ask on twitter or reddit, but no, I don't think anyone is still using vista, it was extremely unpopular even at the time 07:20 < wumpus> +indeed, as timothy says, using an unsupported OS for bitcoin is kind of stupid 07:21 < wumpus> windows 7 is still used intentionally by some people (that dislike windows 10) so setting that as the baseline supported version would make sense, imo 07:22 < fanquake> wumpus fair enough. If you agree with my comments here, https://github.com/bitcoin/bitcoin/pull/14922#issuecomment-446585696, I'll add that to 0.18.0 and ask ken to update (including docs). 07:25 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-sypkheduqxjuyeoo] has joined #bitcoin-core-dev 07:25 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/96bde4f01f41...edc2822b9dc9 07:25 < bitcoin-git> bitcoin/master 8e20934 fanquake: build: Add CLIENT_VERSION_BUILD to CFBundleGetInfoString 07:25 < bitcoin-git> bitcoin/master edc2822 Wladimir J. van der Laan: Merge #14701: build: Add CLIENT_VERSION_BUILD to CFBundleGetInfoString... 07:25 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-sypkheduqxjuyeoo] has left #bitcoin-core-dev [] 07:26 < promag> looks like XP > vista 07:26 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-bedevxojbjknqeru] has joined #bitcoin-core-dev 07:26 < bitcoin-git> [bitcoin] laanwj closed pull request #14701: build: Add CLIENT_VERSION_BUILD to CFBundleGetInfoString (master...add-build-version-to-info-plist) https://github.com/bitcoin/bitcoin/pull/14701 07:26 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-bedevxojbjknqeru] has left #bitcoin-core-dev [] 07:27 < wumpus> fanquake: I agree 07:37 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #bitcoin-core-dev 07:40 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Client Quit] 07:53 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #bitcoin-core-dev 08:03 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 08:04 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 08:17 < promag> IMO #14914 is ready 08:17 < gribble> https://github.com/bitcoin/bitcoin/issues/14914 | Docs: Add nice table to files.md by emilengler · Pull Request #14914 · bitcoin/bitcoin · GitHub 08:20 -!- wxss_ [~user@89.238.150.154] has joined #bitcoin-core-dev 08:23 -!- wxss [~user@81.92.202.29] has quit [Ping timeout: 250 seconds] 08:29 -!- lopp [c0ab1d67@gateway/web/freenode/ip.192.171.29.103] has joined #bitcoin-core-dev 08:30 -!- Tralfaz [~none@c-73-221-225-225.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 08:31 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 08:31 -!- Tralfaz [~none@c-73-221-225-225.hsd1.wa.comcast.net] has quit [Max SendQ exceeded] 08:33 -!- Tralfaz [~none@c-73-221-225-225.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 08:33 -!- Tralfaz [~none@c-73-221-225-225.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 08:36 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 08:36 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 08:36 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 08:36 -!- Tralfaz [~none@104.248.145.220] has joined #bitcoin-core-dev 08:45 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 09:00 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-smdarlbennhqxzzj] has joined #bitcoin-core-dev 09:00 < bitcoin-git> [bitcoin] ken2812221 opened pull request #14937: travis: fix travis would always be green even if it fail (master...travis-fix-save-cache-2) https://github.com/bitcoin/bitcoin/pull/14937 09:00 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-smdarlbennhqxzzj] has left #bitcoin-core-dev [] 09:02 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-izevezdkisjgxlku] has joined #bitcoin-core-dev 09:02 < bitcoin-git> [bitcoin] Sjors opened pull request #14938: Support creating an empty wallet (master...2018/12/create-empty-wallet) https://github.com/bitcoin/bitcoin/pull/14938 09:02 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-izevezdkisjgxlku] has left #bitcoin-core-dev [] 09:03 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #bitcoin-core-dev 09:07 -!- Tralfaz [~none@104.248.145.220] has quit [Read error: Connection reset by peer] 09:07 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-dmqsvxpnjaqeupxz] has joined #bitcoin-core-dev 09:07 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/edc2822b9dc9...38fb1b40dfb3 09:07 < bitcoin-git> bitcoin/master 9b51b15 Emil Engler: Add nice table to files.md... 09:07 < bitcoin-git> bitcoin/master 38fb1b4 Wladimir J. van der Laan: Merge #14914: Docs: Add nice table to files.md... 09:07 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-dmqsvxpnjaqeupxz] has left #bitcoin-core-dev [] 09:07 -!- Tralfaz [~none@104.248.145.220] has joined #bitcoin-core-dev 09:08 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-lkyesjufqcnyarml] has joined #bitcoin-core-dev 09:08 < bitcoin-git> [bitcoin] laanwj closed pull request #14914: Docs: Add nice table to files.md (master...add-nice-table) https://github.com/bitcoin/bitcoin/pull/14914 09:08 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-lkyesjufqcnyarml] has left #bitcoin-core-dev [] 09:19 -!- Tralfaz [~none@104.248.145.220] has quit [Quit: Leaving] 09:20 -!- Tralfaz [~none@104.248.145.220] has joined #bitcoin-core-dev 09:27 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 09:35 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-cileysvdjgjhgxda] has joined #bitcoin-core-dev 09:35 < bitcoin-git> [bitcoin] lontivero opened pull request #14939: rpc: Add test_accept_unsigned flag to testmempoolaccept (master...TestAcceptanceForUnsignedTransactions) https://github.com/bitcoin/bitcoin/pull/14939 09:35 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-cileysvdjgjhgxda] has left #bitcoin-core-dev [] 09:36 -!- q-ask [c3b5a0af@gateway/web/freenode/ip.195.181.160.175] has joined #bitcoin-core-dev 09:37 -!- q-ask [c3b5a0af@gateway/web/freenode/ip.195.181.160.175] has left #bitcoin-core-dev [] 09:48 -!- Guest73299 [~meeeks@128-70-143-139.broadband.corbina.ru] has joined #bitcoin-core-dev 09:48 -!- Guest73299 [~meeeks@128-70-143-139.broadband.corbina.ru] has quit [Remote host closed the connection] 09:49 -!- Geekingfrog25 [~Geekingfr@181.170.158.142] has joined #bitcoin-core-dev 09:49 -!- Geekingfrog25 [~Geekingfr@181.170.158.142] has quit [Remote host closed the connection] 09:50 -!- millerti [~millerti@cpe-66-24-91-119.stny.res.rr.com] has joined #bitcoin-core-dev 09:53 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-rxfonmfgikbbtuog] has joined #bitcoin-core-dev 09:53 < bitcoin-git> [bitcoin] mrwhythat closed pull request #14476: RPC method 'encodescript' (master...encodescript-rpc) https://github.com/bitcoin/bitcoin/pull/14476 09:53 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-rxfonmfgikbbtuog] has left #bitcoin-core-dev [] 10:03 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [] 10:22 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds] 10:26 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 10:46 -!- wernie [5005411b@gateway/web/freenode/ip.80.5.65.27] has joined #bitcoin-core-dev 10:49 -!- timothy [~tredaelli@redhat/timothy] has quit [Remote host closed the connection] 10:50 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 10:51 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 10:52 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 10:53 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 10:56 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 10:58 -!- miknotauro [~miknotaur@201.114.143.145] has joined #bitcoin-core-dev 11:00 -!- wernie [5005411b@gateway/web/freenode/ip.80.5.65.27] has quit [Ping timeout: 256 seconds] 11:01 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 11:01 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 11:01 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 11:03 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 11:11 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 11:11 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 11:11 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 11:15 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 11:16 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 11:54 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection] 12:03 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 12:03 -!- sturles [~sturles@unaffiliated/sturles] has quit [Ping timeout: 252 seconds] 12:04 -!- sturles [~sturles@unaffiliated/sturles] has joined #bitcoin-core-dev 12:08 -!- miknotauro [~miknotaur@201.114.143.145] has quit [Ping timeout: 250 seconds] 12:10 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 12:11 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 12:12 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 12:25 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 12:25 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 12:30 -!- jarthur [~jarthur@2605:6000:1019:41ab:94b0:8ff6:5250:3d63] has joined #bitcoin-core-dev 12:49 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 12:52 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 12:54 -!- miknotauro [~miknotaur@201.114.143.145] has joined #bitcoin-core-dev 12:55 -!- spinza [~spin@155.93.246.187] has quit [Ping timeout: 250 seconds] 13:08 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 13:09 -!- jarthur [~jarthur@2605:6000:1019:41ab:94b0:8ff6:5250:3d63] has quit [] 13:09 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Quit: drexl] 13:29 -!- bitcoinjunior [~bitcoinju@87.101.92.84] has joined #bitcoin-core-dev 13:30 -!- miknotauro [~miknotaur@201.114.143.145] has quit [Ping timeout: 272 seconds] 13:39 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 13:45 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection] 13:46 -!- exekias6 [~exekias@pool-173-54-52-2.nwrknj.fios.verizon.net] has joined #bitcoin-core-dev 13:46 -!- exekias6 [~exekias@pool-173-54-52-2.nwrknj.fios.verizon.net] has quit [Read error: Connection reset by peer] 13:49 -!- wxss [~user@122.155.168.20] has joined #bitcoin-core-dev 13:49 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev 13:50 -!- wxss_ [~user@89.238.150.154] has quit [Read error: Connection reset by peer] 14:00 -!- wxss_ [~user@185.38.150.91] has joined #bitcoin-core-dev 14:03 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: No route to host] 14:03 -!- wxss [~user@122.155.168.20] has quit [Ping timeout: 250 seconds] 14:03 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 14:04 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 14:07 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 14:12 -!- miknotauro [~miknotaur@201.114.143.145] has joined #bitcoin-core-dev 14:15 -!- wxss_ [~user@185.38.150.91] has quit [Read error: Connection reset by peer] 14:16 -!- wxss [~user@172.83.40.195] has joined #bitcoin-core-dev 14:19 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:23 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 14:23 -!- karelb_ [sid316741@gateway/web/irccloud.com/x-dcvobpenhjmxaofi] has joined #bitcoin-core-dev 14:23 -!- moneyball_ [sid299869@gateway/web/irccloud.com/x-nirhrurltjcxspsy] has joined #bitcoin-core-dev 14:23 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection] 14:23 -!- Varunram_ [sid210151@gateway/web/irccloud.com/x-opoprpqfanjtzjgw] has joined #bitcoin-core-dev 14:23 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #bitcoin-core-dev 14:25 -!- dlb76_ [~dlb76@eth0.darkblue.ch] has joined #bitcoin-core-dev 14:27 < andytoshi> sipa: i'm confused by https://github.com/bitcoin/bitcoin/pull/13191 ... it seems the new SHA256D64 does not append the sha256 length/padding anywhere, so how can `ComputeMerkleRoot` be consensus-compatible with the old code? 14:28 < andytoshi> i assume i'm just being dumb/blind 14:28 < gmaxwell> andytoshi: the length/padding is hardcoded into it. 14:29 < gmaxwell> (because the length is fixed) 14:29 -!- Varunram [sid210151@gateway/web/irccloud.com/x-pwdvyxkhvmrevjvi] has quit [Ping timeout: 250 seconds] 14:29 -!- karelb [sid316741@gateway/web/irccloud.com/x-ixuhvjbhtkhozspu] has quit [Ping timeout: 250 seconds] 14:29 -!- dlb76 [~dlb76@unaffiliated/dlb76] has quit [Ping timeout: 250 seconds] 14:29 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 250 seconds] 14:29 -!- nsh [~lol@wikipedia/nsh] has quit [Ping timeout: 250 seconds] 14:29 -!- moneyball [sid299869@gateway/web/irccloud.com/x-jsvlwkbvveurxutb] has quit [Ping timeout: 250 seconds] 14:29 -!- rex4539 [~rex4539@2a02:587:3500:7f00:84f:de91:4853:57bf] has quit [Ping timeout: 250 seconds] 14:29 -!- Varunram_ is now known as Varunram 14:29 -!- moneyball_ is now known as moneyball 14:29 -!- karelb_ is now known as karelb 14:29 < andytoshi> isn't it 512 * `blocks` ? 14:29 -!- Randolf [~randolf@96.53.47.38] has joined #bitcoin-core-dev 14:29 < sipa> andytoshi: it can only hash 64-byte inputs 14:30 < gmaxwell> thats what the D64 means. 14:30 < andytoshi> what does the `blocks` argument mean then? 14:30 < sipa> andytoshi: the 'blocks' is how many double-SHA256-on-64-byte-inputs are being computed *in parallel* 14:30 < andytoshi> ah! 14:30 < andytoshi> thank yuo 14:30 < andytoshi> ah yeah, suddenly the code makes sense :P 14:31 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 14:33 < gmaxwell> the speedup in this code over boring code comes mostly from hardcoding the lengths and padding, and in doing so elimiating the related expander rounds. 14:33 < gmaxwell> (both from the 64 byte input and the 32byte inter-stage input) 14:33 < sipa> and from using SSE4/AVX2 to compute 4 or 8 of them in parallel 14:33 < gmaxwell> whered that patch using avx512 to do 16 in parallel go? :P 14:34 < andytoshi> ok. the reason i ask is that in Elements we are directly using sha2 midstates to get the same speedup (which ofc changes the hash function so is completely incompatible with bitcoin) 14:34 < andytoshi> and we're trying to rebase on #13191 and deciding the best course of action 14:34 < gribble> https://github.com/bitcoin/bitcoin/issues/13191 | Specialized double-SHA256 with 64 byte inputs with SSE4.1 and AVX2 by sipa · Pull Request #13191 · bitcoin/bitcoin · GitHub 14:34 < sipa> https://github.com/bitcoin/bitcoin/pull/13989/files 14:34 < gmaxwell> andytoshi: really? midstates, yuck. :P 14:35 < andytoshi> gmaxwell: yes, yuck :P 14:36 < gmaxwell> welp if you're not using SHA256D64 you can't use that code... it could be adapted to not include the length by changing some constants. 14:37 < andytoshi> yep, that's what i'm concluding. thanks. probably we'll just keep our hacky midstate code and switch to SHA256D64 at the next hf opportunity 14:37 -!- dlb76_ is now known as dlb76 14:37 -!- dlb76 [~dlb76@eth0.darkblue.ch] has quit [Changing host] 14:37 -!- dlb76 [~dlb76@unaffiliated/dlb76] has joined #bitcoin-core-dev 14:37 < gmaxwell> is what elements does SHA256D64 that just doesn't run the second compression function run? 14:37 < andytoshi> gmaxwell: correct 14:37 < gmaxwell> yes, then it could be adapted with some work. it would be somewhat faster than this code. 14:38 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:38 < andytoshi> hmm, ok, maybe it's worth doing that work. though i'm uncomfortable enough with our effectively-homebrew hash function already without trying to optimize it :) 14:39 < promag> should running with -wallet=xxx be an error if it's configured with --disable-wallet? 14:40 < gmaxwell> andytoshi: well fortunately if you get it wrong it probably just won't work. :P 14:40 < andytoshi> hehe, this is true 14:40 -!- nsh [~lol@wikipedia/nsh] has joined #bitcoin-core-dev 14:40 < gmaxwell> promag: hm in one sense, sure, but "I compiled differently and now I get an error on my config files" is not great. 14:41 < promag> right, because config file 14:41 < gmaxwell> promag: logging -wallet ignored due to ... is probably a reasonable middle ground, I dunno if we do that now. 14:59 < promag> is there a long call like waitforblock but that holds a wallet? 15:00 < sipa> i don't think so 15:03 < tryphe> gmaxwell, it would be similar to setting some mempool options along with a "blocksonly=1" line in the config. one could uncomment the single "blocksonly=1" line to have the mempool options take effect. similar to commenting/uncommenting a "disable-wallet=1" line while having wallet= set. 15:04 < tryphe> gmaxwell, uncomment=comment*, but you get the idea :) 15:04 < sipa> tryphe: the difference is that with --disable-wallet, the wallet related code isn't even compiled in, so there would naively not be anything that can recognize those wallet lines as something meaningful in other configurations 15:05 < tryphe> sipa, this is a good point 15:07 < gmaxwell> the reason in favor of erroring on non-sensible configs is because silently giving the user something different than what they asked for isn't nice, and they might bash their head against a wall trying to figure out why it doesn't work because they didn't notice the other parameter. 15:07 < gmaxwell> I generally prefer to log -- unless the interaction is one that if uncaught could cause funds loss. 15:08 < gmaxwell> they'll find the log sometime between the third and fourth hour of troubleshooting. :P 15:08 -!- wxss [~user@172.83.40.195] has quit [Quit: leaving] 15:16 -!- Tralfaz [~none@104.248.145.220] has quit [Ping timeout: 250 seconds] 15:19 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #bitcoin-core-dev 15:27 < promag> review beg #14641 15:27 < gribble> https://github.com/bitcoin/bitcoin/issues/14641 | rpc: Add min_conf option to fund transaction calls by promag · Pull Request #14641 · bitcoin/bitcoin · GitHub 15:28 -!- Randolf [~randolf@96.53.47.38] has quit [Quit: Leaving] 15:34 -!- jarthur [~jarthur@207.114.244.5] has quit [] 15:36 -!- bitcoinjunior [~bitcoinju@87.101.92.84] has quit [Ping timeout: 246 seconds] 15:39 < promag> gmaxwell: are you suggesting to not apply min_conf to ismine utxo? 15:41 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 15:41 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 15:42 -!- kmels [~kmels@190.14.131.146] has quit [Read error: Connection reset by peer] 15:42 -!- brianhoffman_ [~brianhoff@pool-72-83-155-130.washdc.fios.verizon.net] has joined #bitcoin-core-dev 15:42 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 15:45 -!- brianhoffman [~brianhoff@pool-72-83-155-130.washdc.fios.verizon.net] has quit [Ping timeout: 268 seconds] 15:45 -!- brianhoffman_ is now known as brianhoffman 15:46 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Ping timeout: 268 seconds] 15:48 -!- tryphe_ is now known as tryphe 16:10 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:26 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds] 16:32 -!- smaho [~smaho@2601:40a:8003:71a5:84c8:6f86:4c67:4c95] has joined #bitcoin-core-dev 16:35 -!- smaho [~smaho@2601:40a:8003:71a5:84c8:6f86:4c67:4c95] has quit [Client Quit] 16:41 -!- _cryptodesktop_i [~John@91.245.74.33] has joined #bitcoin-core-dev 16:53 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 16:53 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 16:54 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 16:54 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 17:01 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev 17:06 -!- miknotauro [~miknotaur@201.114.143.145] has quit [Ping timeout: 250 seconds] 17:15 -!- _cryptodesktop_i [~John@91.245.74.33] has quit [Ping timeout: 250 seconds] 17:22 -!- millerti [~millerti@cpe-66-24-91-119.stny.res.rr.com] has quit [Quit: Textual IRC Client: www.textualapp.com] 17:38 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection] 17:40 < gmaxwell> promag: maybe everywhere we should split min_conf into min_conf_trusted and min_conf_untrusted. Most wallet behaior defaults to 0,1. 17:41 < gmaxwell> (or more specifically, the coinselection code by default does something like, 6,6 and if that fails 1,1 and if that fails 0,1.) 17:46 -!- bitcoinjunior [~bitcoinju@87.101.92.84] has joined #bitcoin-core-dev 18:30 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 18:30 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Remote host closed the connection] 18:31 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 18:31 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev 18:32 < phantomcircuit> gmaxwell, what? 18:32 < phantomcircuit> of min_conf for our own transactions nvm 18:34 -!- DougieBot5000_ [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-core-dev 18:37 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Ping timeout: 244 seconds] 18:43 -!- DougieBot5000_ is now known as DougieBot5000 19:15 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Remote host closed the connection] 19:15 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev 19:15 -!- jonasschnelli [~jonasschn@unaffiliated/jonasschnelli] has quit [Ping timeout: 252 seconds] 19:17 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 19:22 -!- jonasschnelli [~jonasschn@2a01:4f8:172:10da::2] has joined #bitcoin-core-dev 19:25 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Read error: Connection reset by peer] 19:28 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev 19:28 -!- Netsplit *.net <-> *.split quits: lopp 19:38 -!- bitcoinjunior [~bitcoinju@87.101.92.84] has quit [Ping timeout: 250 seconds] 19:53 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 19:58 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 19:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 20:08 -!- miknotauro [~miknotaur@201.114.143.145] has joined #bitcoin-core-dev 20:20 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 20:31 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 20:42 -!- adam3us [~adam3us@unaffiliated/adam3us] has quit [Quit: QUIT] 20:44 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 20:46 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 20:48 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 20:48 -!- adam3us [~adam3us@unaffiliated/adam3us] has joined #bitcoin-core-dev 21:04 -!- EREVAN [~EREVAN@109.165.8.99] has joined #bitcoin-core-dev 21:04 -!- EREVAN is now known as Guest24281 21:05 -!- Guest24281 [~EREVAN@109.165.8.99] has quit [Remote host closed the connection] 21:05 -!- droark [~droark@c-24-21-203-195.hsd1.or.comcast.net] has joined #bitcoin-core-dev 21:18 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has quit [Remote host closed the connection] 21:23 < droark> Hi. I have a question. On mainnet, about how long does Core need to run before the fee estimation code is considered accurate? 21:23 < sipa> about twice as long as the delay you want to estimate for 21:26 -!- bitcoinsushi [~bitcoinju@87.101.92.100] has joined #bitcoin-core-dev 21:39 -!- nelsonhb [~Instantbi@49.124.42.114] has joined #bitcoin-core-dev 21:51 < droark> Thank you. 21:55 -!- midnightmagic [~midnightm@unaffiliated/midnightmagic] has quit [Ping timeout: 260 seconds] 22:01 < droark> Also, I seem to recall there being some reason why the code can't provide an estimate for TX insertion within one block. I can't remember it, though. Does it have to do with statistical variance? 22:01 < sipa> yes, the next block may be 1 second away 22:01 < sipa> no fee can give you a 95% chance of being included in that 22:03 < droark> Thanks. One last question for now. To clarify, when you say twice as long as the delay, do you mean actual time or # of blocks? I assume the latter but it sounds like I might be wrong. 22:04 < sipa> #blocks 22:04 < droark> Thanks. 22:07 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev 22:12 -!- midnightmagic [~midnightm@unaffiliated/midnightmagic] has joined #bitcoin-core-dev 22:14 -!- jonasschnelli [~jonasschn@2a01:4f8:172:10da::2] has quit [Changing host] 22:14 -!- jonasschnelli [~jonasschn@unaffiliated/jonasschnelli] has joined #bitcoin-core-dev 22:24 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 22:24 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 23:01 -!- Cory [~Cory@unaffiliated/cory] has quit [Ping timeout: 246 seconds] 23:07 -!- Pasha [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev 23:10 -!- CodeBlue1776 [~CodeBlue1@107-215-134-60.lightspeed.cicril.sbcglobal.net] has quit [Read error: Connection reset by peer] 23:10 -!- Pasha is now known as Cory 23:11 -!- CodeBlue1776 [~CodeBlue1@107-215-134-60.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 23:38 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 23:38 -!- shesek [~shesek@141.226.218.112] has joined #bitcoin-core-dev 23:38 -!- shesek [~shesek@141.226.218.112] has quit [Changing host] 23:38 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 23:49 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.3] 23:51 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 23:51 -!- BGL [eighty@75-149-171-58-Washington.hfc.comcastbusiness.net] has quit [Ping timeout: 250 seconds] 23:54 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 23:55 -!- bitcoinsushi [~bitcoinju@87.101.92.100] has quit [Ping timeout: 268 seconds] --- Log closed Thu Dec 13 00:00:50 2018