--- Day changed Mon Nov 13 2017 00:02 < meshcollider> Lauda: 0.15.0 or 0.15.0.1? 00:03 < Lauda> 0.15.0 00:03 < Lauda> Mine crashed several times with "Error eading from database" 00:03 < Lauda> over the last few days. Runs okay for a while and just crashes 00:03 < Lauda> updating to 0.15.0.1 right now to compare 00:03 < wumpus> 0.15.0 can crash due to corrupt peers.dat, but apart from that, no 00:04 < wumpus> this was solved in 0.15.1 (not 0.15.0.1) 00:04 < Lauda> Interesting. I wonder what could be causing this. 00:04 < Lauda> Erm, sorry. Updating to 0.15.1 00:04 < wumpus> without further context it sounds like a hardware issue of some kind 00:05 -!- JackH [~laptop@91.189.61.70] has joined #bitcoin-core-dev 00:06 < wumpus> most of the time database corruptions, if they happen a lot on a single computer, tend to be hw issues (cpu overheat, memory corruption, disk corruption, sometimes due to PSU issues,...) 00:07 < wumpus> you could try to debug it if you think it's a sw issue, but the few times I've spend lots of time chasing such an issue I ended up with a faulty component 00:08 < wumpus> most amusing was the USB stick that randomly toggles bits on heavy usage 00:10 < wumpus> can you pastebin the detailed error? 00:10 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 250 seconds] 00:12 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has joined #bitcoin-core-dev 00:13 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has quit [Remote host closed the connection] 00:13 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has joined #bitcoin-core-dev 00:13 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 00:13 < Lauda> Yeah, I had a flaky USB slot back when I had Core on a external HDD which led to a lot of reindexing. I'll try 0.15.1 first and hope that solves. it 00:14 < Lauda> From the debug log? 00:14 < wumpus> yes 00:16 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 00:18 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has quit [Ping timeout: 268 seconds] 00:20 -!- Guest55818 [~wqetyy@212.133.241.10] has quit [Remote host closed the connection] 00:21 < wumpus> we really need to add a filename to the leveldb checksum mismatch errors, so people can send to file to be analyzed 00:21 < Lauda> ^ 00:22 < wumpus> I did that locally a long time ago but don't think I still have it 00:22 -!- bule2 [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds] 00:22 -!- bitstr3am [~Mutter@50-47-107-125.evrt.wa.frontiernet.net] has joined #bitcoin-core-dev 00:22 -!- bitstr3am [~Mutter@50-47-107-125.evrt.wa.frontiernet.net] has quit [Client Quit] 00:23 -!- bitstr3am [~Mutter@50-47-107-125.evrt.wa.frontiernet.net] has joined #bitcoin-core-dev 00:24 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 248 seconds] 00:24 < Lauda> Shouldn't be too hard? 00:26 < wumpus> depends on whether that context is known at the place the exception is thrown 00:28 -!- bitstr3am [~Mutter@50-47-107-125.evrt.wa.frontiernet.net] has quit [Quit: Mutter: www.mutterirc.com] 00:29 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 00:31 -!- go1111111 [~elliot@199.231.240.157] has joined #bitcoin-core-dev 00:39 < wumpus> oh this seems to be easy 00:41 < wumpus> but it does need some leveldb changes, e.g. currently RandomAccessFile has no way to get the file name back 00:41 -!- Cogito_Ergo_Sum [~Myself@athedsl-314838.home.otenet.gr] has joined #bitcoin-core-dev 00:41 -!- Cogito_Ergo_Sum [~Myself@athedsl-314838.home.otenet.gr] has quit [Changing host] 00:41 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 00:41 -!- scratch_1 [~Mutter@141.22.240.205] has joined #bitcoin-core-dev 00:44 -!- scratch_1 [~Mutter@141.22.240.205] has quit [Client Quit] 00:48 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has joined #bitcoin-core-dev 00:51 < wumpus> still easy changes though 00:52 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 00:53 < wumpus> I'll have a shot at it 00:58 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [Ping timeout: 240 seconds] 01:01 -!- timothy [tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:03 -!- fanquake1 [~fanquake@1.126.48.19] has joined #bitcoin-core-dev 01:03 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Ping timeout: 248 seconds] 01:06 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 01:07 -!- fanquake1 [~fanquake@1.126.48.19] has quit [Ping timeout: 248 seconds] 01:08 -!- scratch_1 [~Mutter@141.22.240.205] has joined #bitcoin-core-dev 01:11 -!- scratch_1 [~Mutter@141.22.240.205] has quit [Client Quit] 01:19 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:21 < bitcoin-git> [bitcoin] laanwj opened pull request #11674: leveldb: Add filename to corruption errors (master...2017_11_leveldb_report_errors) https://github.com/bitcoin/bitcoin/pull/11674 01:23 -!- helloBits [46b4ca1d@gateway/web/freenode/ip.70.180.202.29] has joined #bitcoin-core-dev 01:24 < helloBits> Good day chappies 01:26 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:28 < Lauda> \o/ wumpus 01:29 -!- promag__ [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:30 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Read error: Connection reset by peer] 01:32 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 01:35 -!- laurentmt1 [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 01:37 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Ping timeout: 268 seconds] 01:37 -!- laurentmt1 is now known as laurentmt 01:38 -!- harrymm [~harrymm@85.203.47.130] has quit [Ping timeout: 248 seconds] 01:41 -!- qwerty [~wqetyy@212.133.241.10] has joined #bitcoin-core-dev 01:41 -!- qwerty is now known as Guest92143 01:42 -!- promag__ [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 01:50 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-rfxpalwyzkkbouqw] has quit [Quit: Connection closed for inactivity] 01:52 -!- harrymm [~harrymm@85.203.47.130] has joined #bitcoin-core-dev 01:53 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 01:59 -!- m8tion01 [~m8tion@81-65-53-254.rev.numericable.fr] has joined #bitcoin-core-dev 02:01 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has quit [Ping timeout: 250 seconds] 02:04 -!- roconnor [~roconnor@host-45-58-192-10.dyn.295.ca] has quit [Ping timeout: 248 seconds] 02:07 -!- sefasefseaf [cbdd9390@gateway/web/freenode/ip.203.221.147.144] has joined #bitcoin-core-dev 02:34 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 02:37 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Ping timeout: 248 seconds] 02:46 -!- scratch_1 [~Mutter@141.22.240.205] has joined #bitcoin-core-dev 02:51 -!- coin_trader [~coin_trad@2604:2000:14c4:8161:2c3e:4d2f:561f:fb4b] has quit [Ping timeout: 250 seconds] 02:52 -!- coin_trader [~coin_trad@2604:2000:14c4:8161:1061:8c43:a461:9373] has joined #bitcoin-core-dev 02:54 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 02:55 -!- scratch_1 [~Mutter@141.22.240.205] has quit [Ping timeout: 248 seconds] 02:58 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 03:00 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 03:16 -!- nelruk [~dax_the_c@host-144.58.217.201.copaco.com.py] has joined #bitcoin-core-dev 03:18 -!- scratch_1 [~Mutter@x2f7f7e9.dyn.telefonica.de] has joined #bitcoin-core-dev 03:23 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has quit [] 03:27 -!- sefasefseaf [cbdd9390@gateway/web/freenode/ip.203.221.147.144] has quit [Ping timeout: 260 seconds] 03:29 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 03:34 -!- scratch_1 [~Mutter@x2f7f7e9.dyn.telefonica.de] has quit [Remote host closed the connection] 03:49 < bitcoin-git> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/2adbddb03840...7fbf3c638f3f 03:49 < bitcoin-git> bitcoin/master e0fc4a7 Aaron Clauson: Updated Windows build doc for WSL/Xenial workarounds. 03:49 < bitcoin-git> bitcoin/master 7383d77 Aaron Clauson: Updated instructions for Windows 10 Fall Creators Update. 03:49 < bitcoin-git> bitcoin/master 7fbf3c6 Wladimir J. van der Laan: Merge #11438: Updated Windows build doc for WSL/Xenial workaround... 03:49 < bitcoin-git> [bitcoin] laanwj closed pull request #11438: Updated Windows build doc for WSL/Xenial workaround (master...wslbuilddoc) https://github.com/bitcoin/bitcoin/pull/11438 03:54 -!- scratch_1 [~Mutter@141.22.240.205] has joined #bitcoin-core-dev 03:56 -!- scratch_1 [~Mutter@141.22.240.205] has quit [Client Quit] 03:56 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 248 seconds] 03:59 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 04:02 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 1.7.1] 04:09 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 04:11 -!- wxss [~chatzilla@82.221.112.213] has quit [Ping timeout: 260 seconds] 04:12 -!- wxss [~chatzilla@82.221.112.213] has joined #bitcoin-core-dev 04:15 -!- pergaminho [~Cleber@201.47.91.172] has joined #bitcoin-core-dev 04:16 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 04:16 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 04:22 < Victorsueca> trying to build bitcoin core on WSL, when building the depends it tells me automake is not installed, however it is and both the automake and autoconf commands work when writing them on the terminal 04:22 < Victorsueca> any clue of what's going wrong? 04:23 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 04:24 < wumpus> isn't WSL an ever enduring source of issues, just use a real linux or BSD already :) 04:25 < Victorsueca> welp, I used to compile it succesfully on WSL with ubuntu 14 04:25 < wumpus> yes I'm just kidding, it should work, it's just that there's so many problems reported with it all over the place 04:26 < wumpus> so many "fixes" to that doc 04:26 < Victorsueca> yeah, totally agree, WSL is just a pain in the arse 04:27 < Victorsueca> I still have the Ubuntu 14 WSL on another machine and I can use that to build it 04:27 < wumpus> in theory it's simply a ubuntu "VM", that's how it started and worked fine w/ 14.04, but they started injecting the environment from windows in it 04:27 < wumpus> the more it mutates into some hybrid monster 04:28 < Victorsueca> Basically, getting something that already exists and doing exactly the same but in incompatible ways 04:28 < Victorsueca> has Microsoft ever done anything other than that? ;) 04:28 < wumpus> embrace and extinguish (tm) 04:30 < Victorsueca> Currently building 0.15.1 on the old WSL, works fine as always 04:31 < Victorsueca> but I'd like to get the new one working for damn once 04:32 < Victorsueca> So, more specifically, it's asking for automake-1.14 04:32 < Victorsueca> but the distro repositories only have automake-1.11 and automake-1.15 04:33 < wumpus> it shouldn't require a specific automake version. Did you perhaps upgrade something, without cleaning your tree? 04:33 < Victorsueca> could it be just a version missmatch? 04:33 < wumpus> sometimes there are leftovers from scripts generated from old versions in the way 04:33 < Victorsueca> nope, it's a fresh WSL, just ran the commands stated on the windows build doc 04:34 < Victorsueca> except the Xenial workaround 04:34 < Victorsueca> which I did later today when the doc updated 04:37 < wumpus> the xenial workaround changes to some newer versions using backported packages, that's exactly the change that can result in what I said 04:38 < Victorsueca> thought so, it was worth mentioning that 04:38 < Victorsueca> so, now how do I clean this? 04:39 < wumpus> I'd move away the depends/sources directory, than git clean -f -x -d, move it back, and start over 04:45 -!- marcoagner [~user@gateway/tor-sasl/marcoagner] has joined #bitcoin-core-dev 04:46 < Victorsueca> wumpus: done, still same problem 04:47 < wumpus> ok... no clue in that case 04:47 < Victorsueca> I think it's worth mentioning also that I tried to make the depends before the xenial workaround, and got the same issue 04:48 < Victorsueca> I hoped that the workaround would fix it 04:48 < wumpus> the workaround is for generating broken executables 04:48 < wumpus> it should still build... 04:53 < Victorsueca> hmmm 04:57 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 05:02 < Victorsueca> just noticed that ccache built successfully 05:02 < Victorsueca> it fails when it tries to build native_protobuf 05:04 < Victorsueca> wumpus: I think I found the problem 05:05 < Victorsueca> /depends/work/build/x86_64-w64-mingw32/native_protobuf/2.6.1-38b82cbb6fc on line 81 05:06 < Victorsueca> it's trying to run automake-1.14 05:07 < wumpus> can you pastebin the file plesae? 05:07 < Victorsueca> on the way 05:10 < wumpus> that's a strange file name, are you sure it's called like that, without an extension? 05:10 < Victorsueca> nope, it's a dir, I think the file is Makefile.in 05:11 < Victorsueca> I'll just pastebin the console so you can tell me for sure which file should I send 05:13 < Victorsueca> wumpus: https://0bin.net/paste/NCCZM8Etb52NvGhW#BdyXYVQzaGTwy+xcK75FLDyCA6NOBcwl2BxpwhL6i1D 05:14 < wumpus> "missing" is a generated file 05:14 < wumpus> are you sure cleaning the tree actually cleaned up all that? 05:15 < wumpus> hrm, I think I know the issue 05:15 < wumpus> Victorsueca: you should build from the linux fs, not the mounted windows fs 05:16 < Victorsueca> ok, trying that now 05:16 < wumpus> the windows fs emulation botches timestamps, which makes protobuf think it needs to rebuild its configure scripts 05:16 < wumpus> .... another thing that should be mentionined in that infamous doc 05:21 < Victorsueca> nice, seems like it's working 05:22 < Victorsueca> gone past protobuf, now building boost 05:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 05:40 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 258 seconds] 05:51 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 06:00 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 06:01 < bitcoin-git> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/7fbf3c638f3f...927e5280bdba 06:01 < bitcoin-git> bitcoin/master 84e2462 practicalswift: contrib: Add Valgrind suppressions file... 06:01 < bitcoin-git> bitcoin/master 4a426d8 practicalswift: Add note about Valgrind suppressions file in developer-notes.md 06:01 < bitcoin-git> bitcoin/master 927e528 Wladimir J. van der Laan: Merge #11035: [contrib] Add Valgrind suppressions file... 06:01 < bitcoin-git> [bitcoin] laanwj closed pull request #11035: [contrib] Add Valgrind suppressions file (master...valgrind-suppressions) https://github.com/bitcoin/bitcoin/pull/11035 06:02 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds] 06:03 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 06:08 -!- roconnor [~roconnor@host-45-78-197-59.dyn.295.ca] has joined #bitcoin-core-dev 06:09 < roconnor> wumpus: thanks for the info regarding ccache and gitian. 06:10 -!- roconnor is now known as roconnor_ 06:10 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-emgpqgjuvncgwahu] has quit [Quit: Connection closed for inactivity] 06:15 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds] 06:17 -!- marcoagner [~user@gateway/tor-sasl/marcoagner] has quit [Quit: WeeChat 1.0.1] 06:28 -!- Guest92143 [~wqetyy@212.133.241.10] has quit [Ping timeout: 248 seconds] 06:33 -!- unholymachine [~quassel@2601:8c:c003:9f16:b5a5:17d1:d9dc:6d76] has quit [Remote host closed the connection] 06:33 -!- meilin [~meilin@117.28.223.48] has joined #bitcoin-core-dev 06:34 -!- unholymachine [~quassel@2601:8c:c003:9f16:b4f6:6ecb:b8d:4303] has joined #bitcoin-core-dev 07:00 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 240 seconds] 07:04 < ryanofsky> eck: re "multi-process bitcoin core" see https://eklitzke.org/multiprocess-bitcoin and prs 10102, 10244, 10973 07:06 -!- adiabat [~adiabat@45.63.20.152] has joined #bitcoin-core-dev 07:07 -!- Jey [~je2p@5.120.95.73] has joined #bitcoin-core-dev 07:07 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 07:07 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 07:07 -!- Jey [~je2p@5.120.95.73] has quit [Remote host closed the connection] 07:14 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 07:17 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 07:21 -!- cbag_ [4d397228@gateway/web/freenode/ip.77.57.114.40] has joined #bitcoin-core-dev 07:24 -!- cbag_ [4d397228@gateway/web/freenode/ip.77.57.114.40] has quit [Client Quit] 07:44 -!- hi [6ea80646@gateway/web/freenode/ip.110.168.6.70] has joined #bitcoin-core-dev 07:44 -!- hi [6ea80646@gateway/web/freenode/ip.110.168.6.70] has quit [Client Quit] 07:45 -!- timothy [tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 07:50 -!- timothy [tredaelli@redhat/timothy] has joined #bitcoin-core-dev 07:51 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 07:54 -!- JackH [~laptop@91.189.61.70] has quit [Ping timeout: 240 seconds] 07:57 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 07:59 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 08:00 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 08:01 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 240 seconds] 08:03 -!- jb55 [~jb55@70.36.49.138] has joined #bitcoin-core-dev 08:05 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 248 seconds] 08:08 -!- jb55 [~jb55@70.36.49.138] has quit [Ping timeout: 268 seconds] 08:09 -!- LumberCartel [~randolf@96.53.47.42] has quit [Ping timeout: 240 seconds] 08:18 < ossifrage> I just noticed that somehow ~0.15.1 some how managed to drop a label (it now reads "(no label)") that was present last night via listtransactions 08:19 -!- JackH [~laptop@alvira.static.korbank.pl] has joined #bitcoin-core-dev 08:19 < ossifrage> It seems that 3 of my segwit addresses all have lost their labels 08:20 < ossifrage> It looks like maybe 'addsegwitaddress' for an address that already has a segwit address will clobber the existing label 08:27 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has joined #bitcoin-core-dev 08:30 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has quit [Client Quit] 08:31 < sipa> ossifrage: it shouldn't touch the original address 08:31 < sipa> but the witness address returned by addwitnessaddress won't have a label 08:32 < ossifrage> sipa, I couldn't figure out how to extract the private key for a segwit address, so I walked throught he candidate keys doing an 'addwitnessaddress' until I got a hit 08:35 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 08:36 < achow101> could someone help me debug some locks on https://github.com/achow101/bitcoin/tree/encrypt-no-restart? That branch is for encrypting wallets without restarting, and something in the GUI part is holding cs_KeyStore causing the GUI to freeze 08:37 -!- helloBits [46b4ca1d@gateway/web/freenode/ip.70.180.202.29] has quit [Quit: Page closed] 08:37 < sipa> ossifrage: yes, how is that related to the labels 08:38 < sipa> addwitnessaddress does not support labels 08:38 < achow101> sipa: presumably he called addwitnessaddress a bunch of times to make witness addresses that already existed in the wallet. so then addwitnessaddress overwrote whatever label had already been given to that address? 08:39 < sipa> addresses created by addwitnessaddress never have a label, so i don't think that situation is even possible 08:39 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 08:40 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 08:40 < achow101> sipa: pwallet->SetAddressBook(w.result, "", "receive"); 08:40 < achow101> I think that's the problem 08:41 < sipa> yes, but there's no way the address would have had another label before the call, i think? 08:41 < sipa> or is there some account related call to modify a label after creation 08:41 < achow101> sipa: he added a label himself using some other call 08:44 < achow101> setaccount will let you re-label an address. It can also be done in the GUI, but I don't know if witness addresses will show up there 08:44 < sipa> ah 08:44 < sipa> that's what i was missing 08:53 < ossifrage> sipa, I gave them a label after I initially created them... then that label was clobbered by doing an addwitnessaddress a second time 08:53 < ossifrage> I added the label in the UI by double clicking on the label text and changing it. 08:55 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt] 08:55 -!- LumberCartel [~randolf@209.205.87.205.core.cipherkey.net] has joined #bitcoin-core-dev 08:56 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-oyaxlzisuwlaedia] has joined #bitcoin-core-dev 08:56 < sipa> right, addwitnessaddress sets it to "" 08:56 < sipa> you could change it back, i guess 08:56 < ossifrage> I did, it just was a bit confusing 08:56 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 08:57 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 08:58 -!- Mayra75Walsh [~Mayra75Wa@static.237.72.4.46.clients.your-server.de] has joined #bitcoin-core-dev 09:02 -!- adam_ [cdb25c0c@gateway/web/freenode/ip.205.178.92.12] has joined #bitcoin-core-dev 09:03 -!- adam_ [cdb25c0c@gateway/web/freenode/ip.205.178.92.12] has quit [Client Quit] 09:09 -!- Mayra75Walsh [~Mayra75Wa@static.237.72.4.46.clients.your-server.de] has quit [Remote host closed the connection] 09:11 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 09:12 -!- Curt87Schultz [~Curt87Sch@static.237.72.4.46.clients.your-server.de] has joined #bitcoin-core-dev 09:14 -!- Curt87Schultz [~Curt87Sch@static.237.72.4.46.clients.your-server.de] has quit [Remote host closed the connection] 09:14 -!- Autumn60Schuster [~Autumn60S@static.237.72.4.46.clients.your-server.de] has joined #bitcoin-core-dev 09:16 -!- Autumn60Schuster [~Autumn60S@static.237.72.4.46.clients.your-server.de] has quit [Remote host closed the connection] 09:16 -!- Adolph84Huel [~Adolph84H@static.237.72.4.46.clients.your-server.de] has joined #bitcoin-core-dev 09:19 < achow101> so I'm experiencing some lock contention in the branch I mentioned earlier, and I can't figure out why. nothing is holding cs_KeyStore but the line that is blocking can't acquire it for some reason 09:21 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 248 seconds] 09:24 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 09:27 -!- Adolph84Huel [~Adolph84H@static.237.72.4.46.clients.your-server.de] has quit [Remote host closed the connection] 09:27 -!- Rafael4McDermott [~Rafael4Mc@static.237.72.4.46.clients.your-server.de] has joined #bitcoin-core-dev 09:30 -!- Rafael4McDermott [~Rafael4Mc@static.237.72.4.46.clients.your-server.de] has quit [Remote host closed the connection] 09:31 -!- Kailyn11Kovacek [~Kailyn11K@static.237.72.4.46.clients.your-server.de] has joined #bitcoin-core-dev 09:35 -!- Kailyn11Kovacek [~Kailyn11K@static.237.72.4.46.clients.your-server.de] has quit [Remote host closed the connection] 09:41 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 09:42 -!- Alicia40Nienow [~Alicia40N@static.237.72.4.46.clients.your-server.de] has joined #bitcoin-core-dev 09:49 -!- Alicia40Nienow [~Alicia40N@static.237.72.4.46.clients.your-server.de] has quit [Remote host closed the connection] 09:50 -!- Nona51Blanda [~Nona51Bla@static.237.72.4.46.clients.your-server.de] has joined #bitcoin-core-dev 09:51 -!- bule2 [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 09:55 -!- Nona51Blanda [~Nona51Bla@static.237.72.4.46.clients.your-server.de] has quit [Remote host closed the connection] 09:56 -!- Aaronvan_ is now known as AaronvanW 09:57 -!- timothy [tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 10:09 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 260 seconds] 10:14 -!- nelruk [~dax_the_c@host-144.58.217.201.copaco.com.py] has quit [Quit: Leaving] 10:30 -!- Brad70Eichmann [~Brad70Eic@LFbn-1-936-126.w86-247.abo.wanadoo.fr] has joined #bitcoin-core-dev 10:32 -!- Brad70Eichmann [~Brad70Eic@LFbn-1-936-126.w86-247.abo.wanadoo.fr] has quit [Remote host closed the connection] 10:40 -!- Jaylen58Satterfi [~Jaylen58S@LFbn-1-936-126.w86-247.abo.wanadoo.fr] has joined #bitcoin-core-dev 10:45 -!- pergaminho [~Cleber@201.47.91.172] has quit [Quit: This computer has gone to sleep] 10:46 -!- pergaminho [~Cleber@201.47.91.172] has joined #bitcoin-core-dev 10:47 -!- Jaylen58Satterfi [~Jaylen58S@LFbn-1-936-126.w86-247.abo.wanadoo.fr] has quit [Remote host closed the connection] 10:49 -!- LumberCartel [~randolf@209.205.87.205.core.cipherkey.net] has quit [Ping timeout: 248 seconds] 10:50 -!- Tierra12Toy [~Tierra12T@LFbn-1-936-126.w86-247.abo.wanadoo.fr] has joined #bitcoin-core-dev 10:51 -!- Tierra12Toy [~Tierra12T@LFbn-1-936-126.w86-247.abo.wanadoo.fr] has quit [Remote host closed the connection] 11:04 -!- BGL [~BGLWrK@75-149-171-58-Washington.hfc.comcastbusiness.net] has quit [Ping timeout: 268 seconds] 11:20 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 11:21 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 11:28 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 11:30 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: BRB] 11:35 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 11:43 -!- LumberCartel [~randolf@96.53.47.38] has joined #bitcoin-core-dev 11:48 -!- harrymm [~harrymm@85.203.47.130] has quit [Ping timeout: 248 seconds] 11:59 -!- pergaminho [~Cleber@201.47.91.172] has quit [Quit: Saindo] 11:59 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #11663: [trivial] doc: Add getreceivedbyaddress release notes (master...Mf1711-docReleaseNotes16) https://github.com/bitcoin/bitcoin/pull/11663 12:01 -!- harrymm [~harrymm@85.203.47.130] has joined #bitcoin-core-dev 12:04 -!- bule2 [~bule@gateway/tor-sasl/bule] has quit [Quit: Leaving] 12:07 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 12:08 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 12:09 -!- PaulCape_ [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 12:10 -!- PaulCape_ [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 12:10 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 12:11 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 12:13 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 12:14 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 12:14 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 12:15 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 12:18 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 12:19 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 12:21 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 12:21 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 12:22 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 12:28 -!- reallll [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 12:31 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds] 12:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 12:32 -!- LumberCartel_ [~randolf@96.53.47.42] has joined #bitcoin-core-dev 12:33 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 12:35 -!- LumberCartel [~randolf@96.53.47.38] has quit [Ping timeout: 240 seconds] 12:36 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 12:43 -!- LumberCartel_ [~randolf@96.53.47.42] has quit [Quit: http://www.randolfrichardson.com/] 12:43 -!- LumberCartel [~randolf@96.53.47.42] has joined #bitcoin-core-dev 12:50 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:52 -!- ula [~ula@b2b-78-94-11-194.unitymedia.biz] has joined #bitcoin-core-dev 12:53 -!- shesek [~shesek@bzq-84-110-56-179.red.bezeqint.net] has joined #bitcoin-core-dev 12:53 -!- shesek [~shesek@bzq-84-110-56-179.red.bezeqint.net] has quit [Changing host] 12:53 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 12:55 -!- Dtime [181c0a94@gateway/web/freenode/ip.24.28.10.148] has joined #bitcoin-core-dev 12:56 -!- Dtime [181c0a94@gateway/web/freenode/ip.24.28.10.148] has quit [Client Quit] 12:57 -!- Cogito_Ergo_Sum [~Myself@athedsl-314734.home.otenet.gr] has joined #bitcoin-core-dev 12:57 -!- Cogito_Ergo_Sum [~Myself@athedsl-314734.home.otenet.gr] has quit [Changing host] 12:57 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 12:59 -!- wxss_ [~chatzilla@82.221.112.213] has joined #bitcoin-core-dev 13:01 -!- wxss [~chatzilla@82.221.112.213] has quit [Ping timeout: 240 seconds] 13:01 -!- wxss_ is now known as wxss 13:05 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 13:08 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 13:13 -!- PaulCape_ [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 13:15 -!- rconscious [8102b4f2@gateway/web/freenode/ip.129.2.180.242] has joined #bitcoin-core-dev 13:16 -!- PaulCape_ [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 13:16 -!- BGL [thirty@75-149-171-58-Washington.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 13:16 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 13:17 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...] 13:19 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-xznhjyvkrcpngaii] has joined #bitcoin-core-dev 13:23 < eck> why is it that when you look at debug.log, you see the cache size growing and growing until it periodically "resets" to some much smaller value? 13:23 < BlueMatt> eck: thats when the cache flushes.......... 13:23 < eck> i see, thanks 13:24 < sipa> it's both a cache and a buffer 13:24 < gmaxwell> it's mostly a buffer. :) the performance elements of the caching aren't that significant. 13:24 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 250 seconds] 13:24 < LumberCartel> A cache is strategically managed buffers. 13:25 < LumberCartel> At least that's how I've always understood it. 13:25 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 13:28 -!- PaulCape_ [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 13:29 -!- reallll [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 13:29 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 13:31 -!- LumberCartel [~randolf@96.53.47.42] has quit [Ping timeout: 240 seconds] 13:33 < eck> so if you kill -9 bitcoind, does that mean you have to potentially resync all the data that had been in the in-memory cache/buffer at the time that it was killed? 13:34 < gmaxwell> yes. 13:34 < gmaxwell> it will flush once a day if not earlier due to size 13:40 -!- blockchain [~linux@178.237.154.22] has joined #bitcoin-core-dev 13:41 -!- rconscious [8102b4f2@gateway/web/freenode/ip.129.2.180.242] has quit [Quit: Page closed] 13:45 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Quit: conversation terminated!] 13:46 -!- aspect__ [sid151486@gateway/web/irccloud.com/x-rwashhaabydsevoj] has joined #bitcoin-core-dev 13:47 -!- cryptapus [~cryptapus@jupiter.osmus.org] has joined #bitcoin-core-dev 13:47 -!- cryptapus [~cryptapus@jupiter.osmus.org] has quit [Changing host] 13:47 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 13:48 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has joined #bitcoin-core-dev 13:48 -!- helo_ [~helo@unaffiliated/helo] has joined #bitcoin-core-dev 13:49 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 13:51 -!- gaf_ [~fag@12.smos-linux.org] has quit [Ping timeout: 255 seconds] 13:51 -!- aspect_ [sid151486@gateway/web/irccloud.com/x-euknljsolwpabxqn] has quit [Ping timeout: 255 seconds] 13:51 -!- helo [~helo@unaffiliated/helo] has quit [Ping timeout: 255 seconds] 13:51 -!- PatBoy [xyz@192.99.249.194] has quit [Ping timeout: 255 seconds] 13:51 -!- cdecker [~cdecker@mail.snyke.net] has quit [Ping timeout: 255 seconds] 13:51 -!- bad_duck [~arthur@2001:bc8:c087:1001::1] has quit [Ping timeout: 255 seconds] 13:51 -!- aspect__ is now known as aspect_ 13:52 -!- gaf_ [~fag@12.smos-linux.org] has joined #bitcoin-core-dev 13:52 -!- bad_duck [~arthur@area51.powaaa.com] has joined #bitcoin-core-dev 13:52 -!- cdecker [~cdecker@mail.snyke.net] has joined #bitcoin-core-dev 13:53 -!- PatBoy [xyz@192.99.249.194] has joined #bitcoin-core-dev 13:54 -!- jb55 [~jb55@24.87.206.252] has joined #bitcoin-core-dev 13:57 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 13:57 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has quit [Quit: Mutter: http://www.mutterirc.com] 13:59 -!- griswaalt[m] [griswaaltm@gateway/shell/matrix.org/x-rjpzlswsugcvapym] has quit [Ping timeout: 240 seconds] 13:59 -!- herzmeister[m] [herzmeiste@gateway/shell/matrix.org/x-hrnuslwncopgugkq] has quit [Ping timeout: 250 seconds] 13:59 -!- kewde[m] [kewdematri@gateway/shell/matrix.org/x-nhjdgbkwyedqawkp] has quit [Ping timeout: 246 seconds] 14:00 -!- Masaomi[m] [masaomimat@gateway/shell/matrix.org/x-nuxadmljxitxoxnv] has quit [Ping timeout: 252 seconds] 14:01 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 14:02 -!- kakobrekla [~kako@unaffiliated/kakobrekla] has quit [Ping timeout: 260 seconds] 14:03 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/41aa9c4a801a...5e468994fbb3 14:03 < bitcoin-git> bitcoin/master 2f041f0 Luke Dashjr: contrib/init: Update openrc-run filename... 14:03 < bitcoin-git> bitcoin/master 5e46899 MarcoFalke: Merge #11676: contrib/init: Update openrc-run filename... 14:04 -!- jb55 [~jb55@24.87.206.252] has quit [Ping timeout: 240 seconds] 14:04 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #11676: contrib/init: Update openrc-run filename (master...openrc-run) https://github.com/bitcoin/bitcoin/pull/11676 14:04 -!- kakobrekla [~kako@163-172-8-69.rev.poneytelecom.eu] has joined #bitcoin-core-dev 14:04 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 14:04 -!- kakobrekla [~kako@163-172-8-69.rev.poneytelecom.eu] has quit [Changing host] 14:04 -!- kakobrekla [~kako@unaffiliated/kakobrekla] has joined #bitcoin-core-dev 14:04 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 14:06 -!- wunpunch [~Alli@176.27.129.249] has joined #bitcoin-core-dev 14:06 -!- herzmeister[m] [herzmeiste@gateway/shell/matrix.org/x-cwkhkcenzpxqchnj] has joined #bitcoin-core-dev 14:08 -!- emzy [~quassel@unaffiliated/emzy] has quit [Ping timeout: 240 seconds] 14:09 -!- jb55 [~jb55@24.87.206.252] has joined #bitcoin-core-dev 14:11 -!- esotericnonsense [~esotericn@gateway/vpn/privateinternetaccess/esotericnonsense] has quit [Quit: esoteric nonsense] 14:15 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has joined #bitcoin-core-dev 14:18 -!- emzy [~quassel@raspberry.emzy.de] has joined #bitcoin-core-dev 14:18 -!- JackH [~laptop@alvira.static.korbank.pl] has quit [Read error: Connection reset by peer] 14:18 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has quit [Client Quit] 14:19 -!- JackH [~laptop@alvira.static.korbank.pl] has joined #bitcoin-core-dev 14:19 -!- emzy [~quassel@raspberry.emzy.de] has quit [Changing host] 14:19 -!- emzy [~quassel@unaffiliated/emzy] has joined #bitcoin-core-dev 14:30 -!- LumberCartel [~randolf@24.114.38.138] has joined #bitcoin-core-dev 14:35 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has quit [Read error: Connection reset by peer] 14:39 -!- griswaalt[m] [griswaaltm@gateway/shell/matrix.org/x-xejfnexcqvhuhzjr] has joined #bitcoin-core-dev 14:39 -!- Masaomi[m] [masaomimat@gateway/shell/matrix.org/x-hknxkhhzbpippags] has joined #bitcoin-core-dev 14:39 -!- kewde[m] [kewdematri@gateway/shell/matrix.org/x-yvcfubwysvydzuyy] has joined #bitcoin-core-dev 14:46 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 14:46 -!- unholymachine [~quassel@2601:8c:c003:9f16:b4f6:6ecb:b8d:4303] has quit [Ping timeout: 252 seconds] 14:47 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #11677: qa: Remove unused NodeConn members (master...Mf1711-qaMininodeUnused) https://github.com/bitcoin/bitcoin/pull/11677 14:48 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 14:49 -!- jb55 [~jb55@24.87.206.252] has quit [Ping timeout: 248 seconds] 14:50 -!- unholymachine [~quassel@c-69-248-123-139.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 14:52 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 15:09 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 15:12 < karelb> I will probably ask here - is there a rule how often to reset testnet chains? Shouldn't testnet be reset more often? It is too big now for effective testing 15:13 -!- wunpunch [~Alli@176.27.129.249] has quit [Quit: Leaving] 15:14 < karelb> Is it good idea to make an "informal" rule - that testnet will be reset once it has a certain size in the next release? (For example, once it has 100.000 blocks, then in the next core release) 15:17 < karelb> Well seems I am not the first one to want to reset it - #4416 :) 15:17 < gribble> https://github.com/bitcoin/bitcoin/issues/4416 | testnet4 · Issue #4416 · bitcoin/bitcoin · GitHub 15:18 -!- Cogito_Ergo_Sum2 [~Myself@80.107.150.74] has joined #bitcoin-core-dev 15:18 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [Ping timeout: 248 seconds] 15:21 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 15:22 -!- Cogito_Ergo_Sum2 [~Myself@80.107.150.74] has quit [Client Quit] 15:26 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 15:28 < achow101> karelb: there's no rule. it's only reset when it is super problematic or people start trading testnet coins for money 15:29 < karelb> hm, it's 10GB right now... that is not *super* problematic, but also not small 15:30 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 15:38 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 15:39 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 15:42 -!- LumberCartel [~randolf@24.114.38.138] has quit [Read error: Connection reset by peer] 15:48 -!- uneeb [~uneeb@104.156.103.173] has joined #bitcoin-core-dev 15:50 -!- uneeb [~uneeb@104.156.103.173] has quit [Read error: Connection reset by peer] 16:09 -!- go1111111 [~elliot@199.231.240.157] has quit [Ping timeout: 248 seconds] 16:13 -!- Dizzle [~dizzle@108.171.182.16] has quit [Ping timeout: 240 seconds] 16:14 < bitcoin-git> [bitcoin] achow101 opened pull request #11678: [wip][wallet] Don't shut down after encrypting the wallet (master...encrypt-no-restart) https://github.com/bitcoin/bitcoin/pull/11678 17:06 < phantomcircuit> achow101, i have 2m ... somewhere 17:07 < achow101> phantomcircuit: ?? 17:08 < gmaxwell> achow101: I assume he means testnet coins. 17:09 < achow101> ah 17:09 < sipa> in other words: if TN coins ever have a trade value, phantomcircuit will just crash the market? 17:10 < achow101> one could argue that testnet coins have a trade value now 17:10 < sipa> iirc it was once 3 BTC for 10000 tnBTC 17:15 < phantomcircuit> lol 17:15 < phantomcircuit> sipa, DEAL 17:15 < phantomcircuit> xd 17:16 -!- tloriato [b1d01421@gateway/web/freenode/ip.177.208.20.33] has joined #bitcoin-core-dev 17:16 < sipa> haha 17:16 < sipa> the market may not have been particularly deep back then :p 17:17 < tloriato> good evening, gentlemen. i was reading a little more about schnorr signatures and i'm pretty excited about it 17:17 < tloriato> i was wondering if we have any tests already running or an ETA on that? 17:17 < sipa> tloriato: let's move to #bitcoin-wizards 17:22 -!- pandabull [~pandabull@2600:1:f517:8124:3c43:5296:da3a:fb46] has joined #bitcoin-core-dev 17:24 -!- pandabull [~pandabull@2600:1:f517:8124:3c43:5296:da3a:fb46] has quit [Remote host closed the connection] 17:25 -!- pandabull [~pandabull@2600:1:f517:8124:3c43:5296:da3a:fb46] has joined #bitcoin-core-dev 17:31 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Remote host closed the connection] 17:33 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 17:34 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-oyaxlzisuwlaedia] has quit [Quit: Connection closed for inactivity] 17:38 -!- ChristianXK [23b6fefc@gateway/web/freenode/ip.35.182.254.252] has joined #bitcoin-core-dev 17:42 -!- blockchain [~linux@178.237.154.22] has quit [Quit: Verlassend] 17:43 -!- Itachi [180e0c56@gateway/web/freenode/ip.24.14.12.86] has joined #bitcoin-core-dev 17:47 -!- Itachi [180e0c56@gateway/web/freenode/ip.24.14.12.86] has quit [Ping timeout: 260 seconds] 17:52 < bitcoin-git> [bitcoin] Thoragh closed pull request #11533: Docs: Update WSL installation notes for Fall Creators update (master...Update-WSL-installation-for-Fall-Creators-update) https://github.com/bitcoin/bitcoin/pull/11533 17:56 < midnightmagic> phantomcircuit's not the only one. lol 17:56 < midnightmagic> Dunno who it was who put all those diff-1 post-block diff hack blocks in there but someone was doing it for hundreds of thousands of blocks. 17:57 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 18:02 -!- Itachi [180e0c56@gateway/web/freenode/ip.24.14.12.86] has joined #bitcoin-core-dev 18:06 -!- tloriato [b1d01421@gateway/web/freenode/ip.177.208.20.33] has quit [Quit: Page closed] 18:07 < bitcoin-git> [bitcoin] Thoragh reopened pull request #11533: Docs: Update WSL installation notes for Fall Creators update (master...Update-WSL-installation-for-Fall-Creators-update) https://github.com/bitcoin/bitcoin/pull/11533 18:07 -!- Itachi [180e0c56@gateway/web/freenode/ip.24.14.12.86] has quit [Ping timeout: 260 seconds] 18:08 -!- ChristianXK [23b6fefc@gateway/web/freenode/ip.35.182.254.252] has quit [Ping timeout: 260 seconds] 18:14 -!- nickler [~nickler@185.12.46.130] has quit [Ping timeout: 248 seconds] 18:19 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 18:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Read error: Connection reset by peer] 18:21 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 18:21 -!- nickler [~nickler@185.12.46.130] has joined #bitcoin-core-dev 18:23 -!- jjxtra [a6465e49@gateway/web/freenode/ip.166.70.94.73] has joined #bitcoin-core-dev 18:24 -!- jjxtra [a6465e49@gateway/web/freenode/ip.166.70.94.73] has quit [Client Quit] 18:27 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 18:33 < dcousens> any love for a `droptransaction` from mempool rpc call? 18:34 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 18:37 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 18:40 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 18:47 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 18:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 18:52 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds] 18:58 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 248 seconds] 18:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 19:00 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Quit: WeeChat 1.9] 19:51 -!- pandabull [~pandabull@2600:1:f517:8124:3c43:5296:da3a:fb46] has quit [Remote host closed the connection] 19:51 -!- pandabull [~pandabull@2600:1:f517:8124:3c43:5296:da3a:fb46] has joined #bitcoin-core-dev 19:53 -!- bule2 [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 19:55 -!- pandabull [~pandabull@2600:1:f517:8124:3c43:5296:da3a:fb46] has quit [Ping timeout: 240 seconds] 19:57 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds] 19:57 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 19:59 -!- bule2 [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds] 20:07 -!- jrayhawk_ is now known as jrayhawk 20:10 -!- photonclock [~photonclo@47.37.153.193] has joined #bitcoin-core-dev 20:19 -!- meilin [~meilin@117.28.223.48] has quit [Read error: Connection reset by peer] 20:29 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 20:39 -!- pandabull [~pandabull@2601:184:407f:de69:49df:f3bf:66be:d195] has joined #bitcoin-core-dev 20:43 -!- pandabull [~pandabull@2601:184:407f:de69:49df:f3bf:66be:d195] has quit [Ping timeout: 240 seconds] 20:48 -!- pandabull [~pandabull@2601:184:407f:de69:49df:f3bf:66be:d195] has joined #bitcoin-core-dev 20:53 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 21:07 -!- photonclock [~photonclo@47.37.153.193] has left #bitcoin-core-dev [] 21:43 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 21:49 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 268 seconds] 21:50 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 22:05 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 268 seconds] 22:09 < phantomcircuit> midnightmagic, that's me 22:11 < midnightmagic> phantomcircuit: Oh, good then. 22:12 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 22:15 < warren> dcousens: I'd love that personally 22:16 < sipa> what for? 22:32 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 240 seconds] 22:33 < wumpus> doesn't abandoning a transaction from the wallet remove it from the mempool? 22:34 < sipa> iirc you can only abandan a wallet transaction when it already isn't in the mempool 22:35 < wumpus> you're right, I had that the wrong way around 22:36 < wumpus> and the wallet adds all its transactions to the mempool at startup 22:36 < wumpus> (at least if not walletbroadcast=0) 22:38 < sipa> so basically abandon only works when the tx is already unacceptable to the mempool (due to conflicts with existing chain, or due to mempool full and too low fee) 22:38 < sipa> a mechanism to forcefully abandon a tx may make sense (though it's hard to prepare for it still being possible to mine) 22:39 < sipa> but i'm not sure that giving direct access to drop something from the mempool matters 22:40 < wumpus> there can be cases during development/testing where it can be marginally useful to drop things from the mempool, but it seems to much of a foot shooting option to expose generally 22:40 < sipa> right, as a debug thing sure 22:40 < sipa> at the same level as invalidateblock and reconsiderblock 22:41 < wumpus> warren's case is that he sent a transaction with way too little fee to ever be mined, without RBF, and he wants to try to get rid of it by double-spending it 22:42 < sipa> right, but you really just want a "force abandon wallet tx" there, rather than the more level "drop from mempool", i think 22:42 < wumpus> there's no guarantee it will work of course because miners and other nodes might still have it, but he still wants to try 22:42 < sipa> or even a "force accept this tx, replacing whatever is needed in the mempool" 22:43 < warren> wumpus: actually I was successful 22:44 < wumpus> the latter would be nice, as it matches what needs to be done in this case better, if you don't respend the inputs there's always the possibilty that your transaction gets replayed and mined in the future 22:44 < warren> generally I'd like the ability to remove something from my mempool without wiping the entire thing 22:44 -!- gaf_ [~fag@12.smos-linux.org] has quit [Ping timeout: 248 seconds] 22:46 < wumpus> but anyhow for a diagnostic, undocumented option at the level of invalidateblock/reconsiderblock I woudln't have problems with it 22:47 -!- gaf_ [~fag@5.39.219.206] has joined #bitcoin-core-dev 22:47 < wumpus> it'd be trivial to implement: make a RPC that calls removeRecursive, this will make sure the descendants are removed too 22:49 < wumpus> and then pray it won't be advertised as a general "cancel transaction" solution by people who have no clue how the mempool works and think it's shared between all nodes 22:53 -!- baldur [~baldur@pool-100-2-154-254.nycmny.btas.verizon.net] has quit [Ping timeout: 240 seconds] 22:54 < mryandao> would it be possible to add a key-value "tx-rate" for the getmempoolinfo rpc command, where the average tx-rate of the mempool? 22:55 < mryandao> *fee rate 22:57 < wumpus> would be easier to keep track of the total amount of fee. But what would that info be useful for? 22:58 < mryandao> so a user can decide in advance if they should make a transaction now 22:58 < wumpus> estimatesmartfee would be better for that 22:59 < mryandao> over the weekend, estimate smart fee wasn't very effective 22:59 < sipa> or a way to query "what is the feerate in the mempool, X MB from the top" 22:59 < wumpus> I mean the decision criterion would be the cost to submit a transaction now, not so much what other transaction are paying 23:00 < wumpus> mryandao: the fee estimation is not perfect, but I'm not sure making people do their own fee estimation based on some (easy to manipulate) stats is a better idea 23:01 < mryandao> over the weekend, i thought it might also be a good idea to keep track of the rate of growth of the mempool 23:01 < sipa> mryandao: meh, "infinite" is a good approximation 23:01 < mryandao> maybe the differential is useful for fee estimation 23:01 < sipa> the real question is what the size is _above a certain feerate level_ 23:02 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-hzaictgpvrotdsow] has joined #bitcoin-core-dev 23:05 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 23:11 < bitcoin-git> [bitcoin] jamesob opened pull request #11680: [docs] Add instructions for lcov report generation (master...lcov-docs) https://github.com/bitcoin/bitcoin/pull/11680 23:22 -!- LumberCartel [~randolf@96.53.47.42] has joined #bitcoin-core-dev 23:24 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 248 seconds] 23:37 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 23:40 < eck> +1 for tracking the mempool rate-of-growth 23:41 < eck> and derivatices and higher-order derivatives generally 23:43 < wumpus> sipa's point is that rate of growth in itself isn't interesting; someone could submit an ~infinite number of low fee transactions to pad your mempool up to mempoolmax, and that should not affect fee estimates 23:44 < eck> ah 23:44 < wumpus> so you'd need to track something more subtle 23:44 < sipa> it isn't interesting, and it also doesn't matter 23:44 < sipa> if you're willing to pay X feerate, you don't care at all about any transaction that pays less than X, even if there is 10 GB of them 23:44 < eck> I guess you would need the time derivative of the histogram (if you needed it at all) 23:45 -!- ChristianXK [23b6fefc@gateway/web/freenode/ip.35.182.254.252] has joined #bitcoin-core-dev 23:46 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 23:50 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/5e468994fbb3...cbb54e77a120 23:50 < bitcoin-git> bitcoin/master 73a7e6d Thoragh: Update WSL installation for Fall Creators update 23:50 < bitcoin-git> bitcoin/master cbb54e7 Wladimir J. van der Laan: Merge #11533: Docs: Update WSL installation notes for Fall Creators update... 23:50 < eck> just thinking out loud here, but you could train a simple convolutional filter (for example) to learn the best parameters to estimate a fee rate given the fee histogram from the last N time periods; but you'd have to update the convolution parameters for each bitcoin release, and it would be trivial to find pathological values after the fact to trick the trained algorithm 23:53 < sipa> eck: no way, we're not putting gameable methods in 23:53 < sipa> such methods are awesome if they have human oversight 23:54 < sipa> but you don't want to put them in a fully automated system that is intentionally designed to need user intervention to upgrade :) 23:54 < eck> that's kind of what i thought, interesting though experiment though 23:57 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/cbb54e77a120...7adeea3b0fc2 23:57 < bitcoin-git> bitcoin/master faaa7db MarcoFalke: qa: Only allow disconnecting all NodeConns 23:57 < bitcoin-git> bitcoin/master 7adeea3 Wladimir J. van der Laan: Merge #11641: qa: Only allow disconnecting all NodeConns... 23:57 < bitcoin-git> [bitcoin] laanwj closed pull request #11641: qa: Only allow disconnecting all NodeConns (master...Mf1711-qaNodeConnDisconnectAll) https://github.com/bitcoin/bitcoin/pull/11641