--- Log opened Fri Oct 26 00:00:47 2018
00:10 -!- jarthur [~jarthur@2605:6000:1019:41ab:b0cc:7566:f321:320] has quit []
00:15 < promag> Could backport #12842 to 0.17?
00:15 < gribble> https://github.com/bitcoin/bitcoin/issues/12842 | Prevent concurrent savemempool by promag · Pull Request #12842 · bitcoin/bitcoin · GitHub
00:43 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has quit [Ping timeout: 264 seconds]
00:50 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has joined #bitcoin-core-dev
01:02 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 245 seconds]
01:05 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev
01:08 -!- phwalkr [~phwalkr@192.32.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
01:08 -!- phwalkr [~phwalkr@192.32.61.94.rev.vodafone.pt] has quit [Client Quit]
01:19 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
01:23 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has quit [Ping timeout: 246 seconds]
01:27 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev
01:36 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev
01:45 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Read error: Connection reset by peer]
01:46 -!- fenrus020 [~fenrus02@softbank126042050102.bbtec.net] has joined #bitcoin-core-dev
01:46 < fenrus020> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
01:46 < fenrus020> I thought you guys might be interested in this blog by freenode staff member Bryan kloeri Ostergaard https://bryanostergaard.com/
01:47 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
01:47 -!- fenrus020 [~fenrus02@softbank126042050102.bbtec.net] has quit [Remote host closed the connection]
01:52 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
01:53 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
01:55 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-fgvphpvlmzjalsbf] has joined #bitcoin-core-dev
01:55 < bitcoin-git> [bitcoin] merland opened pull request #14583: docs: Textual improvements in build docs (master...proof-read-build-docs) https://github.com/bitcoin/bitcoin/pull/14583
01:55 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-fgvphpvlmzjalsbf] has left #bitcoin-core-dev []
01:58 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
01:59 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
02:03 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
02:04 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
02:32 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
02:36 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
02:40 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
02:40 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
02:41 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
02:42 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
02:47 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
02:47 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
02:53 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
02:55 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
02:55 < promag> I think #14518 is ready and could be backport
02:55 < gribble> https://github.com/bitcoin/bitcoin/issues/14518 | rpc: Always throw in getblockstats if -txindex is required by promag · Pull Request #14518 · bitcoin/bitcoin · GitHub
02:56 < wumpus> let's first get 0.17.0.1 out of the door
02:56 < promag> I also think #14561 is mergeable
02:56 < gribble> https://github.com/bitcoin/bitcoin/issues/14561 | Remove fs::relative call and fix listwalletdir tests by promag · Pull Request #14561 · bitcoin/bitcoin · GitHub
02:56 < promag> wumpus: +1 just letting you know
02:57 < wumpus> yes, thank you
03:01 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
03:02 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
03:02 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
03:02 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
03:02 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-lsbkzqfuxbkvjlpd] has joined #bitcoin-core-dev
03:02 < bitcoin-git> [bitcoin] laanwj closed pull request #14576: Release 0.17.0.1 (0.17...2018_10_release_0.17.0.1) https://github.com/bitcoin/bitcoin/pull/14576
03:02 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-lsbkzqfuxbkvjlpd] has left #bitcoin-core-dev []
03:02 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:02 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: No route to host]
03:02 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
03:03 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
03:03 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
03:03 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
03:05 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
03:05 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
03:05 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
03:11 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
03:11 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
03:13 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
03:14 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
03:18 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
03:19 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
03:22 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
03:23 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
03:23 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has quit [Ping timeout: 246 seconds]
03:30 -!- dcousens [~dcousens@124.182.9.76] has quit [Ping timeout: 240 seconds]
03:31 -!- dcousens [~dcousens@124.182.9.76] has joined #bitcoin-core-dev
03:36 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Ping timeout: 256 seconds]
03:38 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev
03:40 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
03:41 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
03:49 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
03:50 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
04:00 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev
04:07 < wumpus>  * [new tag]                                                                           v0.17.0.1 -> v0.17.0.1
04:12 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
04:12 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
04:12 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
04:12 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
04:21 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-tmnahlrhzypoptnf] has joined #bitcoin-core-dev
04:21 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/754a00d55f30...9d4541508b98
04:21 < bitcoin-git> bitcoin/master 3be209d João Barbosa: rpc: Always throw in getblockstats if -txindex is required...
04:21 < bitcoin-git> bitcoin/master 9d45415 Wladimir J. van der Laan: Merge #14518: rpc: Always throw in getblockstats if -txindex is required...
04:21 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-tmnahlrhzypoptnf] has left #bitcoin-core-dev []
04:23 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-enwwisbnqztunrsc] has joined #bitcoin-core-dev
04:23 < bitcoin-git> [bitcoin] laanwj closed pull request #14518: rpc: Always throw in getblockstats if -txindex is required (master...2018-10-getblockstats) https://github.com/bitcoin/bitcoin/pull/14518
04:23 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-enwwisbnqztunrsc] has left #bitcoin-core-dev []
04:26 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-zdvrqgsdormxgzsq] has joined #bitcoin-core-dev
04:26 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/9d4541508b98...d50c996a147d
04:26 < bitcoin-git> bitcoin/master ed2e183 João Barbosa: Remove fs::relative call and fix listwalletdir tests...
04:26 < bitcoin-git> bitcoin/master d50c996 Wladimir J. van der Laan: Merge #14561: Remove fs::relative call and fix listwalletdir tests...
04:26 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-zdvrqgsdormxgzsq] has left #bitcoin-core-dev []
04:27 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
04:27 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-thzzqkrliqhxqbgk] has joined #bitcoin-core-dev
04:27 < bitcoin-git> [bitcoin] laanwj closed pull request #14561: Remove fs::relative call and fix listwalletdir tests (master...2018-10-fix-listwalletdir) https://github.com/bitcoin/bitcoin/pull/14561
04:27 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-thzzqkrliqhxqbgk] has left #bitcoin-core-dev []
04:28 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
04:30 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Read error: Connection reset by peer]
04:31 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
04:35 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
04:35 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
04:36 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
04:36 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
04:38 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
04:38 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
04:44 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
04:44 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
04:45 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
04:45 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
04:45 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has quit [Ping timeout: 250 seconds]
04:47 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
04:47 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-tkaruwqkqzcerjtc] has joined #bitcoin-core-dev
04:47 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/d50c996a147d...ae85c8d28bee
04:47 < bitcoin-git> bitcoin/master fbaccbf Chun Kuan Lee: build: Fix Qt link order for Windows build
04:47 < bitcoin-git> bitcoin/master ae85c8d MarcoFalke: Merge #14568: build: Fix Qt link order for Windows build...
04:47 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-tkaruwqkqzcerjtc] has left #bitcoin-core-dev []
04:48 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
04:48 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
04:48 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
04:49 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-pswiestssvkfibrk] has joined #bitcoin-core-dev
04:49 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #14568: build: Fix Qt link order for Windows build (master...win-qt-fix) https://github.com/bitcoin/bitcoin/pull/14568
04:49 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-pswiestssvkfibrk] has left #bitcoin-core-dev []
04:52 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-crlmmqgmavomatiq] has joined #bitcoin-core-dev
04:52 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/ae85c8d28bee...f4e4ea1ceecf
04:52 < bitcoin-git> bitcoin/master 3387bb0 Chun Kuan Lee: travis: avoid timeout without saving caches, also enable all qt
04:52 < bitcoin-git> bitcoin/master f4e4ea1 MarcoFalke: Merge #13515: travis: Enable qt for all jobs...
04:52 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-crlmmqgmavomatiq] has left #bitcoin-core-dev []
04:53 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-skauffgxgjlgnpkl] has joined #bitcoin-core-dev
04:53 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #13515: travis: Enable qt for all jobs (master...travis_qt) https://github.com/bitcoin/bitcoin/pull/13515
04:53 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-skauffgxgjlgnpkl] has left #bitcoin-core-dev []
04:54 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 252 seconds]
04:59 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
05:03 -!- TheRec [~toto@drupal.org/user/146860/view] has quit []
05:09 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has joined #bitcoin-core-dev
05:16 < harding> For 0.17.0.1, a few questions related to what changes I might need to make to BitcoinCore.org for it: (1) is only the MacOS binary going to be added to /bin/bitcoin-core-0.17.0.1/ or will there be .0.1 versions for all platforms?  (2) Are there going to be release notes for it?  (3) Do we want a blog post about it on the home page?
05:16 -!- TheRec [~toto@84-72-172-174.dclient.hispeed.ch] has joined #bitcoin-core-dev
05:16 -!- TheRec [~toto@84-72-172-174.dclient.hispeed.ch] has quit [Changing host]
05:16 -!- TheRec [~toto@drupal.org/user/146860/view] has joined #bitcoin-core-dev
05:16 -!- hebasto [~hebasto@95.164.65.194] has quit [Read error: Connection reset by peer]
05:17 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev
05:18 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
05:19 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
05:19 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
05:21 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
05:21 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
05:23 < wumpus> harding: (1) there will be a 0.17.0.1 version for all platforms, I think that's most convenient as that allows following the normal release process. I also think that's what we did before in these cases?
05:24 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has quit [Ping timeout: 252 seconds]
05:25 < wumpus> harding: (2) the release notes are here, it's really short: https://github.com/bitcoin/bitcoin/blob/0.17/doc/release-notes.md
05:26 < wumpus> harding: (3) I think a blog post is not worth doing, this is just a minor fixup that affects a small part of users it seems
05:27 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
05:29 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
05:29 < harding> wumpus: that's what I remember being done for all the other 0.*.*.1 releases, and it's easiest for the website if there are release notes because, as you say, it's the same release process.  It is possible (and pretty easy) to have binaries split across two directories on both BitcoinCore.org and Bitcoin.org as we both use the same mechanism to allow for easy changes in the filenames across releases, so let me know if you ever do 
05:29 < harding> need to do a partial release.
05:29 < harding> wumpus: thanks!  That's everything I needed to know.  I'll get a PR up.
05:30 -!- laurentmt [~Thunderbi@185.242.6.5] has joined #bitcoin-core-dev
05:32 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
05:32 < wumpus> harding: I also remember that, to not confuse users, we've once used the 0.x.y release notes for 0.x.y.1, and just added the mention of the fix
05:33 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
05:33 < wumpus> otherwise it's like "wow this is supposed to be a major release but it changes nothing"
05:33 < wumpus> might be something for the web site at least; but good to know the binary situation works for you, will go ahead with that then
05:37 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Read error: Connection reset by peer]
05:37 < harding> wumpus: if users being confused is a concern and it's ok with everyone, I can just add a sentence on the website version of the release notes that says, "Otherwise this software is identical to [0.17.0](/link/to/0.17.0/release/notes)".
05:38 < wumpus> harding: yes, that would help I think!
05:39 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
05:40 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
05:41 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
05:42 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
05:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
05:49 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
05:50 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
05:50 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
05:50 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
05:54 -!- laurentmt [~Thunderbi@185.242.6.5] has quit [Quit: laurentmt]
05:57 < promag>  jonasschnelli: please take a look at #14573 
05:57 < gribble> https://github.com/bitcoin/bitcoin/issues/14573 | qt: Add Wallet and Window menus by promag · Pull Request #14573 · bitcoin/bitcoin · GitHub
05:57 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds]
06:01 < promag> BTW in #14573 the address book dialogs are moved as discussed in last week meeting
06:01 < gribble> https://github.com/bitcoin/bitcoin/issues/14573 | qt: Add Wallet and Window menus by promag · Pull Request #14573 · bitcoin/bitcoin · GitHub
06:06 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has quit [Read error: Connection reset by peer]
06:06 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has joined #bitcoin-core-dev
06:09 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #bitcoin-core-dev
06:10 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
06:11 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
06:11 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
06:11 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
06:15 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
06:16 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
06:17 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
06:19 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds]
06:25 < jonasschnelli> promag: will do
06:25 < promag> thanks, it's pretty small
06:30 < promag> scantxoutset should be scanutxoset?
06:46 -!- timothy [~tredaelli@redhat/timothy] has quit [Remote host closed the connection]
06:46 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev
06:48 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
06:49 -!- timothy [~tredaelli@redhat/timothy] has quit [Client Quit]
06:49 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
06:49 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
06:49 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
06:56 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev
06:56 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
06:58 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
06:58 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
06:58 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
06:58 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
07:01 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has quit [Ping timeout: 260 seconds]
07:02 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
07:02 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/]
07:05 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
07:05 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
07:05 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
07:05 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
07:07 < harding> promag: I assume it's named to correspond to gettxoutsetinfo.
07:09 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
07:10 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
07:10 < promag> harding: makes sense
07:10 < promag> gettxoutsetinfo should be getutxosetinfo? :P
07:10 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
07:13 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
07:13 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
07:13 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
07:16 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
07:22 < instagibbs> promag, bitcoind doesn't track stxo so no info to give ;P
07:22 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
07:22 < instagibbs> I do find that the most impossible rpc command to remember/type out
07:23 < andytoshi> wumpus: the rust-bitcoinrpc crate has a huge dep tree that has all sorts of borderline-unstable stuff written by "webscale" people. i would not trust it
07:24 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-ojyyrdjphcbqnkcn] has joined #bitcoin-core-dev
07:24 < bitcoin-git> [bitcoin] ken2812221 closed pull request #13827: [WIP] depends: Add native_nsis to support unicode (master...depends-nsis) https://github.com/bitcoin/bitcoin/pull/13827
07:24 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-ojyyrdjphcbqnkcn] has left #bitcoin-core-dev []
07:24 < andytoshi> rust-jsonrpc is better but it's still not where i want it to be. afaik there is no HTTP client library for rust that doesn't have a bad dependency story. we would need to write our own to do bitcoin-cli in rust.
07:25 < andytoshi> OTOH, if somebody were to do that work it'd be generally very useful
07:26 < wumpus> andytoshi: interesting—yes such a outgrowth of dependencies shouldn't be necessary for a little tool like that
07:26 < wumpus> it's not bad to have deps, but…I certainly get your point
07:28 < wumpus> promag: I also *always* by definition, forget the name of that command
07:29 < andytoshi> wumpus: at blockstream we have functionary software written in rust, and the HTTP stuff is literally 50% of our dep tree (and has caused 100% of our dependency-related trouble). if we were using the latest version of hyper the tree size would double again, so it'd be 75% of our dep tree. and it's exactly the kind of stuff that is hard to vet and tends to be written by incautious people
07:29 < wumpus> the other long RPC I have no trouble with, like signrawtransaction with wallet, but that utxo statistics command darn how was it called again
07:29 < andytoshi> so sure, not bad to have deps, but i think in this case it's a problem
07:31 < promag> instagibbs: lol
07:32 < wumpus> andytoshi: so 'hyper' is the root of the tree of trouble, so to say?
07:32 < andytoshi> yep
07:33 < promag> provoostenator: ken2812221: hebasto: please test #14123, ty!
07:33 < andytoshi> FWIW you can disable all of its connection management stuff (and with it most of the dep tree) .. but there's no replacement for it, you'd have to write all that yourself, and then you might as well just rewrite the whole thing
07:33 < gribble> https://github.com/bitcoin/bitcoin/issues/14123 | gui: Add GUIUtil::bringToFront by promag · Pull Request #14123 · bitcoin/bitcoin · GitHub
07:33 < wumpus> I might have a look at it :)
07:34 < wumpus> it's absolutely overkill for a RPC client, I was happy not to need hyper for my c-lightning RPC wrapper
07:34 < hebasto> promag: doing now :)
07:34 < andytoshi> wumpus: awesome :) i've been thinking about writing a simple single-threaded "template-based HTTP" client for a while, and slowly add things to it as needed. i think that could be done with almost no deps and have a very small code footprint
07:34 < andytoshi> but i haven't had the time
07:37 -!- TheHoliestRoger_ is now known as TheHoliestRoger
07:39 -!- no_input_found [no_input_f@gateway/vpn/privateinternetaccess/noinputfound/x-24977668] has joined #bitcoin-core-dev
07:40 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #bitcoin-core-dev
07:50 -!- dqx [~dqx@unaffiliated/dqx] has quit [Quit: .]
07:51 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
07:52 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
07:52 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
07:52 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
08:09 < e4xit> why was BIP 159 allocated service bit 10 rather than then next freely available bit (5)? Were those bits previously allocated but not used, or something else?
08:09 < luke-jr> service bits aren't really allocated (perhaps they should be?), just claimed
08:10 < e4xit> ok, so would be simply a decision made by jonasschnelli then
08:11 < luke-jr> there was probably discussion here, but at the end of the day, yes
08:11 < e4xit> thanks
08:15 < luke-jr> note that some high bits are typically perceived as temporary/testing/adhoc usage
08:15 < luke-jr> eg, the full RBF bit
08:17 < jonasschnelli> I used bit 10 because other non bitcoin (core) stuff did use the below ones.
08:22 < e4xit> ok thanks jonas. I thought that was likely the case but I couldn't find much (core) documentation detailing what might be using them, which makes sense now... 
08:23 < luke-jr> I only have 0-4,10,26 documented (or visible on the network in any notable count)
08:25 < luke-jr> BIP 158 seems to use bit 6
08:27 < luke-jr> bit 5 was allocated in BIP 149, but obviously n/a
08:27  * luke-jr updates https://luke.dashjr.org/programs/bitcoin/files/charts/services.html for bit 6
08:30 < luke-jr> I wonder when we should start retiring the segwit service bit
08:30 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds]
08:32 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
08:41 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-klavzouqdoejvrkd] has joined #bitcoin-core-dev
08:41 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #14534: Enable flake8 rule E225 which checks for missing whitespace around op… (master...flake8-fix-E225) https://github.com/bitcoin/bitcoin/pull/14534
08:41 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-klavzouqdoejvrkd] has left #bitcoin-core-dev []
08:42 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 272 seconds]
08:50 < e4xit> thank luke-jr 
08:51 < e4xit> *thanks
08:53 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
08:54 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
08:54 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
08:54 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
08:57 < wumpus> right, you can just try to claim your favourite bit in your BIP
08:57 < wumpus> you don't need to explain why you picked it
08:58 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds]
08:58 < wumpus> although yes what luke-jr says, the higher bit are considered special purpose for temporary or experimental things, I think that's written in a BIP somewhere
08:59 < wumpus> luke-jr: I think retiring that bit needs a BIP in itself
09:00 < wumpus> (e.g. with your time planning, when to stop setting and/or interpreting it, as other software will need that too)
09:02 < wumpus> and there will have to be a period before it can be reused for other things
09:02 < luke-jr> nah, software can just decide when it's no longer worth filtering for (and instead handling the occasional "bad" peer), and then software can decide when it's no longer useful to set
09:02 < luke-jr> doesn't have to be coordinated
09:02 < wumpus> well, I think it makes sense to coordinate this
09:03 < wumpus> even if at least to get discussion about it, write down what it takes to retire a service bit (it's the first time isn't it?)
09:04 < wumpus> also it gives future BIPs that want to use that bit something to refer to, that they can reclaim it
09:04 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
09:05 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
09:05 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
09:05 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
09:16 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 272 seconds]
09:17 -!- queip [~queip@unaffiliated/rezurus] has quit [Quit: bye, freenode]
09:24 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev
09:30 -!- Sinclai__ [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has quit [Ping timeout: 246 seconds]
09:34  * esotericnonsense scrolls up. lol.
09:35 < esotericnonsense> my project for learning some rust, was http. this explains why I am chasing my tail.
09:41 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection]
09:42 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev
10:00 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-gzodmcyalqkeheyl] has joined #bitcoin-core-dev
10:00 < bitcoin-git> [bitcoin] practicalswift opened pull request #14585: Don't rely on locale dependent functions in base_blob<BITS>::SetHex(...) (uint256), DecodeBase58(...), ParseMoney(...) and ParseHex(...) (master...no-locale-surprises-please) https://github.com/bitcoin/bitcoin/pull/14585
10:00 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-gzodmcyalqkeheyl] has left #bitcoin-core-dev []
10:18 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev
10:24 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
10:25 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
10:25 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
10:27 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 252 seconds]
10:30 -!- lukedashjr is now known as luke-jr
10:37 -!- Tralfaz [~none@185.156.175.59] has joined #bitcoin-core-dev
10:57 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 240 seconds]
10:58 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
10:58 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Ping timeout: 245 seconds]
11:06 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-core-dev
11:07 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!]
11:18 -!- rhavar [uid237883@gateway/web/irccloud.com/x-iayzpuidxldlrtue] has joined #bitcoin-core-dev
11:26 < gmaxwell> Is there a reason we can't have the wallet sync status _never_ tell people that it is "X years behind" and instead say that it is synced up to date x/y/z? The foo years behind thing seems to frequently cause people to think that it will take years to finish the sync.
11:41 -!- oshithemoto [5576bd0c@gateway/web/freenode/ip.85.118.189.12] has joined #bitcoin-core-dev
11:42 < oshithemoto> Anyone here who coded a bitcoin wallet in VB.NET? 
11:44 < sipa> oshithemoto: off topic here
11:50 < oshithemoto> offtopic? isn´t this the developer channel?
11:51 < jarthur> Specifically Bitcoin Core development. #bitcoin-dev or #bitcoin may be better suited.
11:51 < oshithemoto> ok thx!
11:53 -!- shinohai_ is now known as shinohai
11:57 < oshithemoto> maybe offtopic but are here ppl from the good old Sub7 Crew? 
11:59 < sipa> yes, offtopic
12:06 < oshithemoto> no one is writting here, just like idling here? gg I am an old developer, i did some decentraliced stuff bevor bitcoin, cordinated ddos attacs and i hope to find some old crew member, it was not sub7 crew but some of the ppl from this crew can help me find my old crew members I think one of them is satoshi nakamoto. his "old" nickname was "oso", he was a hacker and our crew name was #ratpack and he told my about a decen
12:07 < sipa> oshithemoto: please go away
12:08 < sipa> this channel is about discussing development on the Bitcoin Core software; you're welcome to idle or discuss relevant topics, but those don't include other Bitcoin clients, and certainly not trojan horse software
12:09 < oshithemoto> he told me about a new decentraliced system called "the bitnetwork" in 2002, so he was developing it, I search him now for 6 years, maybe someone of here knows him, pls contact me thx
12:09 < oshithemoto> that´s it sorry ;)
12:09 < sipa> noted.
12:12 -!- oshithemoto [5576bd0c@gateway/web/freenode/ip.85.118.189.12] has quit [Quit: Page closed]
12:16 -!- reallll [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev
12:19 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 252 seconds]
12:20 -!- reallll is now known as belcher_
12:26 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Read error: Connection reset by peer]
12:27 -!- bitconner [~conner@136.24.75.121] has joined #bitcoin-core-dev
12:28 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #bitcoin-core-dev
12:42 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection]
12:44 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
12:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
12:49 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds]
12:52 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Remote host closed the connection]
12:52 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev
12:55 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
12:59 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 244 seconds]
13:10 -!- Guest12812 [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Ping timeout: 245 seconds]
13:20 -!- dx25 [~dx25@97-119-102-240.omah.qwest.net] has joined #bitcoin-core-dev
13:21 -!- dx25 [~dx25@97-119-102-240.omah.qwest.net] has left #bitcoin-core-dev []
13:22 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Read error: Connection reset by peer]
13:30 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev
13:44 < phantomcircuit> gmaxwell, i dont see a reason to change that
13:44 < phantomcircuit> it's definitely confusing as is
13:46 < gwillen> phantomcircuit: a reason not to change, rather? :-)
13:49 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
13:51 < phantomcircuit> gwillen, yeah
13:51 < phantomcircuit> there was a "not" in there
13:51 < phantomcircuit> seems it stayed in my head
13:52 < gwillen> safest place for it really
13:56 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
13:56 -!- instagibbs [~instagibb@pool-100-15-135-248.washdc.fios.verizon.net] has quit [Ping timeout: 252 seconds]
13:58 -!- Tralfaz [~none@185.156.175.59] has quit [Remote host closed the connection]
13:59 -!- Tralfaz [~none@185.156.175.59] has joined #bitcoin-core-dev
13:59 -!- Tralfaz [~none@185.156.175.59] has quit [Remote host closed the connection]
14:00 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
14:03 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
14:10 -!- jarthur [~jarthur@207.114.244.5] has quit []
14:20 -!- roasbeef_ is now known as roasbeef
14:31 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
14:32 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
14:33 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev
14:33 -!- schmidty is now known as Guest63027
14:34 < wumpus> gmaxwell: it used to be like that a long time ago, "X" years behind was apparantly seen as an improvement
14:34 < wumpus> gmaxwell: I... don't know, it seems we're circularly revisiting the same ideas over and over
14:35 < gmaxwell> Any chance you can refer me to the discussion where "X years behind" was proposed an improvement?
14:35 < wumpus> someone claims that something is better UI so that gets implemented, then someone else calls somethinge else again
14:35 < wumpus> we're never going to make progress without someone with an actual clue in this 
14:35 < wumpus> no, I don't know, must be in git history somewhere...
14:36 < gmaxwell> I'm not speculating here, there is a continual stream of users who think that it will take years to sync. E.g. example I ran into today: https://bitcoin.stackexchange.com/questions/71147/bitcoin-core-delay-in-synching
14:36 < gmaxwell> I can go pull some other examples up if you'd like to see them.
14:36 < wumpus> I really don't know, I'm sick and tired of this tbh
14:36 < gmaxwell> Then quit the project wumpus.
14:37 < wumpus> yes
14:38 < wumpus> you wouldn't believe how many times the progress display was redesigined, in a way someone found better, but of course, it results in other people complaining
14:39 < sipa> whatever we do, people are always going to complain about something
14:39 < wumpus> I'm sorry.. I'm having trouble with this
14:39 < midnightmagic> And then some of us will complain about people complaining!
14:40 < gmaxwell> There isn't anyone even really complaining on this, just a regular stream of confused people.
14:40 < gmaxwell> I asked specifically to avoid looping on it.
14:40 < wumpus> I try to be helpful, I really try to do what is useful, what are good choices that help people, but it's never okay
14:40 < midnightmagic> wumpus: Don't quit. We love you man! You're a longer-term-thinking moderate, which means it's harder for people to find a reason to hate you.
14:41 < gmaxwell> No one did anything wrong with this.  It just turns out presenting a long delay to users is fundimentally hard because user easily get anxious and worry that it isn't working.
14:41 < wumpus> midnightmagic: believe me, I don't want to! 
14:41 < sipa> i think the real problem is that syncing is slow :)
14:41 < wumpus> midnightmagic: it's just that after years it feels a bit repetitive, that's all
14:41 < midnightmagic> (external) people like arguing about shed colours, man, it's only avoidable if nobody engages them.
14:42 < sipa> for many people it's a fundamentally inconvenient interface, but we're constrained in how to improve that
14:42 < midnightmagic> wumpus: Super repetitive. And I don't even contribute code to the repo..!
14:42 < wumpus> I just wish... someone with UI design experience would get involved, and make a good descsion based on human psychology on this, and we'll just stick with that
14:43 < sipa> wumpus: that'd be great
14:43 < midnightmagic> Those people are all working for games companies.
14:43 < wumpus> but that never happens
14:43 < wumpus> yep
14:43 < sipa> and yeah... please don't quit; but if you need a break...
14:44 < midnightmagic> People don't want to get their hands dirty building bitcoin because they worry that if they make a mistake, someone will blame them for millions of $$ lost. And the people who overcome that are philosophically-minded people who jump off that cliff anyway and hope Miles back at the base camp packed their parachute properly. :)
14:44 < gmaxwell> wumpus: it doesn't work that way in any case. You can put all the expirence in the world, and sometimes you're going to find that people get confused, so you tweak it a bit. It's not a big deal.  Sometimes it's all fine, and then the language educational materials use changes, and people end up confused and things have to change to respond, etc.
14:45 < gwillen> wumpus: FWIW that's not even how it works in commercial software
14:45 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
14:45 < wumpus> but we can't keep doing 'someone complains about this! let's change it again'
14:45 < gwillen> over there you get promoted for making big changes pointlessly
14:45 < gwillen> so they do it even more frequently
14:46 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
14:46 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
14:46 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
14:46 < gwillen> they are supposed to have UX people, but it's not like the UX people don't also get promoted for making big changes
14:46 < sipa> wumpus: just because someone complains doesn't mean it needs to change
14:46 < gwillen> *shrugs* I think churn is a fact of life in software
14:46 < sipa> but it may be worthwhile to look at why it was changed in the past
14:47 < wumpus> midnightmagic: it's painful to overcome, I agree
14:47 < gmaxwell> sipa: thats why I was asking instead of just opening a PR, to get context.
14:47 < midnightmagic> Yeah, sick people like me on them. I'll change the topic to POWER hardware, and they'll go off and buy a Blackbird and forget they had a complaint at all! :)
14:48 < gmaxwell> [I certantly remember this stuff being changed before, not that particular behavior but the opening message]
14:48 < midnightmagic> wumpus: You could do the Linus thing and take up extensive and heavy drinking for a couple decades.
14:48 < gwillen> look at it this way, we know more now than we did then, so we're more likely to make the right choice now than we were then :-)
14:48 < wumpus> gmaxwell: yes... I think at a deeper level it's something like 'people only pay attention to the GUI to complain about something'
14:49 < wumpus> midnightmagic: I don't like shouting at people :p
14:49 < gmaxwell> https://github.com/bitcoin/bitcoin/commit/24cde0b7d1ad014ffca5d0af896bc50b30e5ddcd
14:49 < gmaxwell> is where the 'x years behind' language was added.
14:50 < midnightmagic> wumpus: hehe I was about to say, just kidding, the fact you haven't means IMO you're ahead of where Linus was.
14:50 < wumpus> gmaxwell: it might even be that I didn't even find it a very good idea at the time
14:50 < gmaxwell> Prior to that it gave a height behind, with numbers based off peers starting height claims.
14:50 < gmaxwell> IIRC we also had some issue with malicious/broken peers at the time giving bogus starting heights.
14:51 < gmaxwell> I agree that the blocks based behind is pretty opaque and unhelpful to users, and obviously the old behavior of relying on peers claimed heights is not a good one.
14:52 < sipa> it looks like that PR is just introducing a better estimation algorithm, without any reasons for the particular UI chosen
14:52 < wumpus> midnightmagic: I guess one thing I am good at is keeping the project together despite all the controversy and hostility from outside
14:53 < gmaxwell> What I was thinking of doing was replacing the 'foo behind' language with a 'Synced up to yyyy-mm-dd' or similar, with a rational that it would not be realistically possible to mistake that for a 'how long it will take to sync'  (Omg it's going to take 2018 years to sync! :P )
14:53 < wumpus> gmaxwell: oh it moved from blocks behind?
14:53 < gmaxwell> wumpus: yes
14:53 < wumpus> gmaxwell: I thought it showed a date first, as you proposed
14:53 < sipa> gmaxwell: sounds very reasonable to me
14:53 < gmaxwell> Not as far as I can tell from the history. There might have been a branch at some point that did?
14:54 < wumpus> yes it might have been a proposal then at the time, which didn't make it?
14:54 < wumpus> people chose the N days behind
14:55 < gmaxwell> most of the PR discussion is about the progress estimation.
14:55 < gmaxwell> it originally gave it in days, and before it went in you changed it to use more human-ish units at schildbach's request.
14:55 < gmaxwell> But I don't see any discussion of anything but a 'behind'.
14:55 < gmaxwell> The prior behavior was N blocks behind.
14:56 < wumpus> ok
14:56 < gwillen> gmaxwell: if you wanted to include time-in-past, perhaps less confusing would be "synced blocks through $DATE (XX units ago)"
14:57 < wumpus> I'm happy if people can agree on something
14:57 < gwillen> I imagine that would less tempt people to imagine that it will take XX units to sync.
14:57 < wumpus> please don't make this another bikeshedding thing
14:57  * sipa forcibly volunteers gwillen to suggest an improvement
14:57 < gwillen> but just a bare "through $DATE" obviously presents no possible confusion.
14:58 < gwillen> for the record I have no preference and will express no opinion on the final outcome, I only offer an option for cleverer people than me to consider :-)
14:58 < gmaxwell> gwillen: I think any AGO is going to trigger the same 'it'll take this long to finish' confusion. Is there an important reason for the ago?
14:58 < sipa> i think anything with an actual date will be less confusing
14:58 < gwillen> gmaxwell: nope, just avoid making me do mental math :-)
14:58 < gmaxwell> I think the date is useful, in the sense of the wallet will show transactions made up until DATE.
14:58 < gwillen> but I guess there's no actual reason to _care_ how long ago it was
14:58 < gmaxwell> But how is ago useful? it doesn't tell you when it will finish. right
14:58 < gwillen> right, date is actually more useful if I want to know "will it include a particular tx"
14:59 < gmaxwell> Basically I think people want to know two things: When it will finish, and (dim second) when is it current through.
14:59 < wumpus> gwillen: that's a good point
14:59 < wumpus> gwillen: it's actually *useful*
14:59 < gwillen> *nods*
14:59 < gwillen> yeah, on reflection it is mostly _fun and entertaining_ to see how long ago it's synced through
15:00 < gwillen> which is maybe not a good reason
15:00 < wumpus> we've left fun and entertaining long ago, it's deadly serious now
15:00 < gwillen> yeah
15:03 < midnightmagic> Everybody likes watching speed meters. "Verifying X utxo/sec, complexity measure Y". And a little running graph. With blinking lights. Where's that guy who was trying to do chain visualization in OpenGL anyway..
15:03  * midnightmagic ducks and runs away
15:05 < gmaxwell> sipa: I agree with your earlier point that the sync taking a long time is the real issue.
15:06 < gwillen> honestly for my own purposes, the most important innovation in progress technology was the "XX percent per second" meter
15:06 < gwillen> that's really all I look at now when doing IBD
15:10 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
15:10 < gmaxwell> gwillen: what I think from talking to people they do is dimiss that it's-not-in-sync dialog, then they just see "XX years behind" and at least some portion of them mistake it for an ETA.
15:11 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
15:11 < gwillen> ahhhh, right, that appears in the status bar which is normally covered by the dialog to start
15:11 < gwillen> *nods*
15:11 < gmaxwell> I dunno what percentage, probably small, but enough that I see a confused user every couple of months.
15:11 < wumpus> midnightmagic: hah we've had ideas like that xD it would have been fun at some point in time
15:11 < gwillen> so perhaps the status bar should include an _actual_ ETA? if it doesn't already? (I forget what it says and I don't have a client in IBD to check)
15:12 < wumpus> midnightmagic: now it's more like making a joke at a funeral I guess
15:12 < gwillen> (or percent synced, or whatever the most important thing is from the dialog they just dismissed)
15:12 < gmaxwell> I was particularly frustrated today because I encountered yet another one where they got a long reply given them a 10 step procedure to stop using bitcoin core, which never even mentioned they were confused about progress. (certantly not the first time I've seen that happen).
15:12 < gwillen> (I just never dismiss the dialog until sync is complete because I don't know how to get it back, or whether you can get it back)
15:13 < gmaxwell> gwillen: you click on the 'xx behind' text to get it back.
15:13 < gwillen> ahhhh
15:14 < wumpus> not even the fancy new progress dialog helped :-(
15:14 < gmaxwell> Oh I'm sure it helps.
15:14 < wumpus> people were confused about progress, so that overlay was added, but ... it's all the same
15:15 < gmaxwell> Though it also could use some improvements, the choice in bold text is weird.  IIRC it was supposted to get fixed before the release but it wasn't.
15:15 < wumpus> yess of course they just want to attack bitcoin core
15:15 < wumpus> we're the enemy after all
15:15 < gmaxwell> and/or just the blind leading the blind
15:16 < wumpus> it doesn't matter, whatever your politics, either bitcoin is destroying the world, or well otherwise there's always infighting between implementation
15:16 < wumpus> it's good that everyone is so mature about it
15:17 < sipa> wumpus: i find the twitter mute button incredibly useful
15:18 < gmaxwell> I find not loading twitter useful. :P
15:18 < wumpus> yea :/
15:18 < gmaxwell> that popup thing is kind of mesmerizing.... click, hide, click, hide.
15:19 < wumpus> reddit is so much better 
15:20 < wumpus> yes I think that's kind of neat !
15:20 < gmaxwell> An alternative would be to make the XX behind just show the ETA and a "(click for details)".  Though I'm not sure what it shoudl display when the ETA isn't available.
15:24 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
15:24 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
15:25 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
15:34 -!- keer4n [~keer4n@132.178.207.4] has joined #bitcoin-core-dev
15:37 < gmaxwell> gwillen: researching user reports, the percent per hour thing also seems to be confusing in non-initial sync.
15:38 -!- rhavar [uid237883@gateway/web/irccloud.com/x-iayzpuidxldlrtue] has quit [Quit: Connection closed for inactivity]
15:38 < gwillen> interesting
15:38 < gwillen> I guess that makes sense, after IBD you're not probably thinking in terms of "percent of entire blockchain downloaded"
15:38 < gmaxwell> because it seems to report percentage of the whole chain always.
15:38 < gwillen> well, it's not clear what else it would report
15:38 < gwillen> "percent of the amount of blockchain that was missing when I started up most recently" maybe?
15:39 < gmaxwell> Thats probably what its being interperted as in any case.
15:39 < gwillen> my user model is hopelessly contaminated with already knowing what's going on, so it makes perfect sense to _me_
15:39 < gmaxwell> here is an example: https://bitcoin.stackexchange.com/questions/65056/unacceptably-slow-bitcoin-sync
15:39 < gmaxwell> "Bitcoin core is currently 15 hours behind as I'm writing this and the piph (progress increase per hour) is at a STUPIDLY low speed. There are 95 blocks left but it says its going up 0.04% per hour."
15:40 < gwillen> I mean, it's also maybe worth considering that some users will have less useful input than others
15:40 < gwillen> "Bitcoin core is also apparently using 50% of my disk which is not true. An application was using 12mb/s of disk and it was only using about 20% of the disk total. Bitcoin core however is using 3mb/s and is using 50%"
15:40 < gwillen> I can't even parse what this sentence is attempting to communicate.
15:40 < sipa> gwillen: I/O bandwidth grap?
15:41 < gmaxwell> gwillen: absolutely, but actually the percentage per hour is pretty inexplicable when talking about syncing 0.0002% of the chain. :P
15:41 < gmaxwell> I mean in those cases the number won't even show anything useful. 
15:41 < gwillen> yeah, it's weird to be sure, I guess my machine syncs fast enough that I don't run into such tiny numbers for more than a few seconds
15:41 < gmaxwell> gwillen: regarding that sentence, I think he edited his question.
15:42 < gwillen> he did edit it, I just cannot for the life of me figure out what the edit it _saying_.
15:42 < gmaxwell> gwillen: likely he only had one stuck peer up or whatever.. and probably it was done by the time he was through posting.
15:43 < gmaxwell> gwillen: it's some IO meter thing, who knows what.
15:43 < gmaxwell> The comment I think its basically saying "there is a lot of random IO"
15:43 < gmaxwell> e.g. 50% "utilization" but only 3MB/s.
15:44 < gmaxwell> In any case, I've found three people conused by the percentage thing. That was just the most clear (lol, I suppose) of them.
15:44 < gwillen> yeah, *nodnods*
15:44 < gmaxwell> I don't see anyone confused about the ETA thing.
15:47 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
15:47 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
15:47 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
15:47 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
15:51 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:52 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
15:52 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
15:54 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
15:56 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
15:56 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
15:56 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
16:11 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
16:12 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
16:12 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
16:12 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
16:13 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
16:20 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
16:21 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
16:21 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
16:21 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
16:33 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev
16:51 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
16:51 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
16:51 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
16:51 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
16:52 < gwillen> I assume no, because nobody uses OS X but me: has anybody run the various sanitizers on OS X?
16:53 < gwillen> it seems like they don't build here, due to -fsanitize being passed to the compiler but not the linker
16:53 < gwillen> I can easily one-off fix this just to run them on my own change, but I am afraid to dive in to fix it properly
16:57 < gwillen> oh, it's weirder than that
16:57 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Read error: Connection reset by peer]
16:57 < gwillen> we're passing -fsanitize to libtool, which is dropping it on the floor and not passing it to the linker
16:58 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
17:00 < wumpus> leave it to libtool to do things like that
17:01 < gmaxwell> leave it to OSX's toolchain to do things like that. :P
17:01 < sipa> https://wiki.gentoo.org/wiki/AddressSanitizer/Problems
17:02 < gwillen> it;s weird, it's passing through -fstack-protector-all
17:02 < gwillen> even though it does not appear to be documented to do that
17:02 < sipa> i assume that they're just using a libtool that's sufficiently old to not know about asan
17:02 < wumpus> nah I have similar experiences with libtool on other platforms just for different things, it has a really bizarre filter
17:02 < sipa> wait
17:02 < sipa> that patch linked that fixes it in libtool upstream is dated july 24th 2018
17:03 < gwillen> I'm on a mac, my libtool may never be updated
17:03 < gwillen> it's probably fixed for other people :-)
17:03 < gmaxwell> sipa: that doesn't make much sense, since it's worked elsewhere for forever.
17:03 < sipa> gwillen: i assume that our depends environment builds libtool from scratch'
17:04 < gmaxwell> (possible everywhere was just patching libtool and we don't)
17:04 < wumpus> gwillen: yes I'm sure a newer libtool will fix this
17:04 < wumpus> they only let through compile options they know about for some strange reason
17:04 < gwillen> let's see if homebrew has libtool, that can't possibly go wrong
17:04 < sipa> gmaxwell: nvm, i'm stupid and looking at the wrong commit
17:05 < wumpus> which would be okay, I guess, if they warned instead of silently ignoring
17:05 < sipa> wumpus: i guess they want to filter what goes to linker, what to compiler, what to other things, ...?
17:05 < sipa> and sometimes guess wrong?
17:06 < sipa> not knowing it has to go to multiple of them
17:06 < wumpus> sipa: it's gcc that does that
17:06 < sipa> right
17:06 < sipa> i guess i am clueless about libtool
17:06 < wumpus> and gcc is very strict in argument parsing
17:06 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: No route to host]
17:07 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
17:07 < wumpus> me too, mostly
17:08 < wumpus> it's one of those things you'd wish wasn't necessary in the first place
17:11 < gwillen> hm, that's odd, it seems like I am supposed to be using latest libtool, although it's kind of hard to tell
17:12 < gwillen> I guess I don't understand the relationship between the libtool script and the libtool installed on the system
17:12 < gwillen> but the libtool script was generated with libtool 2.4.6 which is latest
17:12 < gwillen> I can't tell whether the system's libtool is something it invokes, or only something that would be used to generate it
17:14 < wumpus> it's... complicated
17:15 < gwillen> heh.
17:15 < gwillen> I hate build systems.
17:15 < wumpus> I think it's autoconf that generatesthe libtool executable from m3 templates elsewhere 
17:15 < wumpus> m4*
17:18 < wumpus> I think that's libtool*ize*
17:18 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.3]
17:21 < sipa> i never realize those could be distinct things
17:23 < wumpus> gwillen: I don't think I hate it, it's useful, but also it's grown organically to such a monstriosity
17:24 < gwillen> *nods*
17:24 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
17:24 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
17:24 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
17:24 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
17:26 < wumpus> in any case if the generated libtool executable that you have is sufficiently new I think that means everything should be okay
17:26 < gwillen> and yet it fails :-(
17:26 < wumpus> yep ...
17:28 < gwillen> it seems there is a magic flag to tell libtool to fuck off: "-XCClinker"
17:28 < gwillen> means "pass the following flag directly to cc when linking"
17:30 < gwillen> also the joke is apparently on me because all this was to build libbitcoinconsensus which nothing is actually using (?), apparently it had already built bitcoind the whole time I was fighting with this :D
17:30 -!- IGHOR [~quassel@93.178.216.72] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.]
17:31 < wumpus> yes, libconsensus is a library meant for external usage
17:32 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
17:32 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
17:32 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
17:32 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
17:35 -!- IGHOR [~quassel@93.178.216.72] has joined #bitcoin-core-dev
17:35 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
17:35 < wumpus> it still shouldn't fail the build I suppose
17:35 -!- ken2812221 [~ken281222@110.50.135.178] has quit [Read error: Connection reset by peer]
17:35 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
17:42 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.2]
17:42 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
17:43 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
17:44 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
18:05 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has quit [Ping timeout: 244 seconds]
18:28 -!- lnostdal [~lnostdal@77.70.119.51] has joined #bitcoin-core-dev
18:30 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Ping timeout: 246 seconds]
18:47 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-core-dev
18:59 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Remote host closed the connection]
19:07 -!- commavir_ is now known as commavir
19:11 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-zybiohglbjxdrimp] has joined #bitcoin-core-dev
19:11 < bitcoin-git> [bitcoin] gwillen opened pull request #14588: Refactor PSBT signing logic to enforce invariant and fix signing bug (master...feature-psbt-sign-fix) https://github.com/bitcoin/bitcoin/pull/14588
19:11 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-zybiohglbjxdrimp] has left #bitcoin-core-dev []
19:13 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
19:16 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds]
19:23 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit []
19:25 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev
19:26 -!- wahaha001 [~wahaha007@1.198.44.195] has joined #bitcoin-core-dev
19:32 -!- wahaha001 [~wahaha007@1.198.44.195] has quit [Quit: Mutter: www.mutterirc.com]
19:37 -!- josephnicholas [~josephnic@110.54.174.39] has joined #bitcoin-core-dev
19:54 -!- josephnicholas [~josephnic@110.54.174.39] has quit []
20:03 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection]
20:06 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev
20:06 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
20:08 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
20:08 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
20:08 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
20:12  * luke-jr wonders why there are nodes claiming to be 0.17.0.15
20:18 -!- robo7 [~robo7@unaffiliated/robo7] has joined #bitcoin-core-dev
20:24 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
20:26 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
20:29 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds]
20:31 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
20:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds]
20:47 -!- schnerchi [~schnerchi@p3EE1C3CE.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
20:50 -!- schnerch_ [~schnerchi@p3EE1CA64.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
20:51 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
21:03 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Remote host closed the connection]
21:03 -!- rhavar [uid237883@gateway/web/irccloud.com/x-iljwzpqkeeiborqi] has joined #bitcoin-core-dev
21:03 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev
21:17 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Read error: Connection reset by peer]
21:17 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
21:22 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Read error: Connection reset by peer]
21:30 -!- wahaha001 [~wahaha007@124.64.17.164] has joined #bitcoin-core-dev
21:30 -!- wahaha001 [~wahaha007@124.64.17.164] has quit [Client Quit]
21:31 -!- bitconner [~conner@136.24.75.121] has quit [Ping timeout: 245 seconds]
21:40 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
21:41 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
21:43 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
21:45 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
21:49 -!- schnerch_ [~schnerchi@p54A0EAAC.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
21:52 -!- schnerchi [~schnerchi@p3EE1C3CE.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
22:25 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev
22:31 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
22:33 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
22:33 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
22:33 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
22:33 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
22:37 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
22:39 -!- hatoda [6ad1ce5d@gateway/web/freenode/ip.106.209.206.93] has joined #bitcoin-core-dev
22:41 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
22:41 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
22:41 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
22:41 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
22:44 -!- hatoda [6ad1ce5d@gateway/web/freenode/ip.106.209.206.93] has left #bitcoin-core-dev []
22:46 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
22:46 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
22:47 -!- shesek [~shesek@141.226.218.111] has joined #bitcoin-core-dev
22:47 -!- shesek [~shesek@141.226.218.111] has quit [Changing host]
22:47 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
22:50 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has quit [Ping timeout: 246 seconds]
22:50 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
22:51 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
22:54 -!- hatoda [6ad1ce5d@gateway/web/freenode/ip.106.209.206.93] has joined #bitcoin-core-dev
22:58 -!- hatoda [6ad1ce5d@gateway/web/freenode/ip.106.209.206.93] has left #bitcoin-core-dev []
23:00 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
23:01 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
23:04 -!- Cory [~Cory@unaffiliated/cory] has quit []
23:05 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
23:06 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
23:11 -!- Cory [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev
23:14 -!- bralyclo_ [~bralyclow@195.242.213.119] has quit [Remote host closed the connection]
23:33 -!- akirashinjo [b299e60d@gateway/web/freenode/ip.178.153.230.13] has joined #bitcoin-core-dev
23:46 -!- akirashinjo [b299e60d@gateway/web/freenode/ip.178.153.230.13] has quit [Quit: Page closed]
--- Log closed Sat Oct 27 00:00:48 2018