--- Day changed Thu Dec 05 2019 00:34 -!- Netsplit *.net <-> *.split quits: Lightsword 00:37 -!- Johncc [807f69b8@128.127.105.184] has joined #joinmarket 00:38 -!- Netsplit over, joins: Lightsword 00:39 < Johncc> Hey any idea why "python wallet-tool -m 15 wallet" doesn't work any more? It throws out an error that any mixing depth higher than 4 is not allowed 00:39 < Johncc> and in the docs that is the command recommended for recovering btc spread among depths 01:18 -!- SourDoughB [027e398c@2.126.57.140] has joined #joinmarket 01:55 -!- Netsplit *.net <-> *.split quits: justinmoon_, openoms, harding, zfk, johnhmay, Anduck, felix34, qubenix, treyzania, @ChanServ, (+45 more, use /NETSPLIT to show all of them) 01:56 -!- Netsplit over, joins: achow101, waxwing, ghost43, luke-jr, sosthene, midnight, schmidty, justinmoon_, willcl_ark, takinbo (+28 more) 01:59 -!- AgoraRelay [~jmrelayfn@p5DE4A50C.dip0.t-ipconnect.de] has joined #joinmarket 01:59 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #joinmarket 01:59 -!- qubenix [~qubenix@66.172.11.228] has joined #joinmarket 02:00 -!- Netsplit *.net <-> *.split quits: sosthene, GAit, mr_burdell, qubenix, stoner19, nkuttler, achow101, belcher_, Xeha, nsh, (+31 more, use /NETSPLIT to show all of them) 02:01 -!- Netsplit over, joins: achow101, waxwing, ghost43, luke-jr, sosthene, midnight, schmidty, justinmoon_, willcl_ark, takinbo (+31 more) 02:02 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket 02:02 -!- Guest5184 [~azizLIGHT@097-101-162-070.res.spectrum.com] has joined #joinmarket 02:03 -!- so [~so@unaffiliated/so] has joined #joinmarket 02:03 -!- Lightsword [~Lightswor@107.170.253.193] has joined #joinmarket 02:03 -!- sturles [~sturles@unaffiliated/sturles] has joined #joinmarket 02:04 -!- SourDoughB [027e398c@2.126.57.140] has joined #joinmarket 02:04 -!- Johncc [807f69b8@128.127.105.184] has joined #joinmarket 02:04 -!- viasil [~viasil@95.174.67.204] has joined #joinmarket 02:04 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 02:04 -!- avril [wha@unaffiliated/avril] has joined #joinmarket 02:04 -!- emzy [~quassel@unaffiliated/emzy] has joined #joinmarket 02:04 -!- nothingmuch [~nothingmu@unaffiliated/nothingmuch] has joined #joinmarket 02:04 -!- fluffypony [fluffypony@unaffiliated/fluffypony] has joined #joinmarket 02:04 -!- Anduck [~Anduck@unaffiliated/anduck] has joined #joinmarket 02:12 < waxwing> Johncc, that'll be because the wallet file only contains 5 mixdepths. but there could be more to it than that, sorry i can't stay right now. 02:13 < Johncc> well im pretty sure i've btc stuck among higher depts but can't force it to show them :( 02:13 < Johncc> and in that case why the official docs recommend trying with -m 15 when recovering btc? 02:23 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 02:34 < AgoraRelay> [agora-irc/AlexCato1] are you sure you *manually* created a wallet with more than 5 depths? How long ago was this approximately, so that we can guess which Joinmarket version was used (or maybe you know?). Also, I cant recall the the docs recommending checking higher mixdepths, can you give me a link to that? 02:46 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket 02:52 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 03:04 -!- Francisco25Ernse [~Francisco@ns334669.ip-5-196-64.eu] has joined #joinmarket 03:16 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 276 seconds] 03:16 < waxwing> right which version of Joinmarket used is important. also is this a recovered wallet in a new version of Joinmarket, or something created and kept with the same Bitcoin Core instance. 03:16 < waxwing> re: the docs wouldn't surprise me at all if something like that is there, and of course will be changed if wrong. but first priority is diagnose the problem. 03:21 < waxwing> i mention recovery because one logical way this could arise: you do say a tumbler run and use higher mixdepths. then you recover the wallet (say, on another machine) and to do that you generate the wallet using the 'recover' method. but it gets created with 5 mixdepths (max=4), and when you run wallet-tool it's done with storage in read-only mode, which triggers the mentioned error (line 323 of jmclient/wallet.py) 03:25 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 03:31 < waxwing> afk for a little while i think but Johncc get back to us on some of that info ^ 03:38 -!- SourDoughB [027e398c@2.126.57.140] has quit [Remote host closed the connection] 03:42 -!- SourDoughB [027e398c@2.126.57.140] has joined #joinmarket 04:28 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has quit [Remote host closed the connection] 04:46 < Johncc> I don't remember if I manually created it with more mixing depths, but very often I had the tumble stuck and had to intervene, so might have created more if that has been necessary in the case. 04:46 < Johncc> I've used few different old versions and I'm going through all the wallets now recovered on the latest version on a new machine 04:47 < Johncc> Here is where the -m 15 argument is recommended https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/docs/USAGE.md#mnemonic 04:48 -!- Francisco25Ernse [~Francisco@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 240 seconds] 04:49 < Johncc> Basically the end goal is to go through few old wallets from varios older versions of joinmarket (segwit and non-segwit) and to make 100% sure there are NO btcs stuck among the depths. Because I remember always had problems with interrupted tumbles and btc left here and there among the process and depths. 04:49 < Johncc> And I have the latest versions of JM installed and bitcoin core with full blockchain on a pc to do that. 05:02 < waxwing> Johncc, answering on github issue. my connection here is flaky for some reason rn 05:03 -!- SourDoughB [027e398c@2.126.57.140] has quit [Remote host closed the connection] 05:03 < Johncc> yes, better to keep it in one place :) 05:04 -!- SourDoughB [027e398c@2.126.57.140] has joined #joinmarket 05:07 < waxwing> unrelated to above, but i'm guessing a lot of people didn't see this: https://github.com/JoinMarket-Org/custom-scripts/issues/5 05:07 < waxwing> should be a trivial fix as per comment 05:46 < AgoraRelay> [agora-irc/AlexCato1] oh, i completely forgot about the custom scripts repo 05:46 < AgoraRelay> [agora-irc/AlexCato1] sorry, pings only work on IRC and reddit for me :( 06:00 -!- SourDoughB [027e398c@2.126.57.140] has quit [Remote host closed the connection] 06:07 -!- SourDoughB [027e398c@2.126.57.140] has joined #joinmarket 06:16 -!- Johncc [807f69b8@128.127.105.184] has quit [Remote host closed the connection] 06:37 -!- SourDoughB [027e398c@2.126.57.140] has quit [Ping timeout: 260 seconds] 07:12 -!- SourDoughB [027e398c@2.126.57.140] has joined #joinmarket 07:24 < SourDoughB> If I understand correctly, when I top up my mixdepth0 with new coins, I have to restart the yiedgenerator.. Also a restart seems to be necessary when a balance within one mixdepth increases (due to new coins moving in after a successful coinjoin), so the new max amount is higher.. is this right? If so, is there a way to automatize this process 07:24 < SourDoughB> somehow, so that the YG can run for longer periods unattended (f.ex so the YG restarts itself once a day or so)? 07:36 < waxwing> ok i think i figured out johncc's issue, seems there is no error in the code, you just have to specify at point of recovery. see #465 for details 07:38 < waxwing> SourDoughB, after 0.6.0 you do not have to restart the yieldgenerator, no 07:38 < waxwing> the wallet is scanning for new transactions all the time. before 0.6.0 it wouldn't recognize new coins until restart. 07:40 < SourDoughB> Ah, thanks. I'm pretty sure I have 0.6.0. Is there a way to check the version quickly (noob with CLI...)? 07:44 < waxwing> if you did `git clone` you can do `git tag` and should see "tag: v0.6.0" on the top line; if you use Qt you can see it in `About` but perhaps dumbly the normal scripts don't have a --version 07:44 < SourDoughB> Actually I definitely should have 0.6.0 cause the set up guide I followed involves that version :) But I am fairly certain I had to restart the YG to include the new deposits etc... Will keep an eye on that 07:45 < waxwing> ah well i suppose there is a detail there. 07:45 < SourDoughB> yeah, the --version doesn't seem to work with the scripts 07:46 < waxwing> which i hadn't thought about: you add say 1 coin to mixdepth 0; the app then immediately knows about that coin but it doens't re-advertise. it's jsut, the next time it *does* advertise it will do so based on the newly updated balance. 07:46 < waxwing> seems reasonable to say it's probably correct like that, otherwise (theoretically) a spy can correlate txs on chain with advertisements/announcements 07:46 < waxwing> although random delay also solves that. 07:47 < waxwing> seems a fairly minor point though, basically, a deposit will be "known" by the app immediately, it just won't necessarily do anything with it until a new event happens. 07:47 < SourDoughB> ah yes, that's the situation that I observed 07:47 < waxwing> i mean if you get a join just after the deposit is confirmed, those coins can be used. 07:47 < waxwing> without a restart 07:48 < SourDoughB> yes, makes sense :) 07:49 < SourDoughB> But everything else should be advertised automatically (like when the overall balance of a mixdepth increases after new coinjoins come in from lower mixdepths), right? 07:50 < waxwing> yeah basically when a coinjoin happens your bot may or may not re-advertise, what it does is, first queries the wallet service for the balance at each mixdepth, then works out its highest offer size, then it re-announces if it's changed, and doesn't if it hasn't. *very rough* description. 07:50 < waxwing> and since the wallet service now is always up to date on real balances, new deposits get included in that process. that's all really. 07:51 < SourDoughB> ok gotcha :) 07:51 < waxwing> whereas before an external deposit would only get recognized when we did a "re-sync", which only happened in certain places in certain scripts, and as it happened it wasn't done in the yield generator. 07:51 < SourDoughB> I guess it would be nice to have YG automatically advertise the new, increased maxsize when new coins come into mixdepth0 (after a random delay, as you said)... But thinking about it it's a minor thing indeed 07:52 < waxwing> i agree prob random delay then readvertise is more in line with what users would want 07:57 < SourDoughB> yep :) 07:58 < waxwing> uh sorry above i said "if you did `git clone` you can do `git tag`" but i meant " ... you can do `git log`" 07:59 < SourDoughB> ah I didn't do git clone anyway :) 07:59 < SourDoughB> completely unrelated side note: watching coins go from lower mixdepths to higher ones feels a little like unlocking new levels in a game :D go go my little satoshis! 08:29 -!- SourDoughB [027e398c@2.126.57.140] has quit [Remote host closed the connection] 08:29 -!- SourDoughB [027e398c@2.126.57.140] has joined #joinmarket 09:49 -!- Guest5184 [~azizLIGHT@097-101-162-070.res.spectrum.com] has quit [Ping timeout: 268 seconds] 10:04 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket 12:05 < kristapsk> "yeah, the --version doesn't seem to work with the scripts" - hmmm, maybe we should add it? 12:10 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has joined #joinmarket 12:11 < belcher> should just be a few lines in cli_options.py i believe 12:12 < belcher> its definitely useful, like for example upgrading and making sure you're really using the new version... or for asking newbs to run it to see which version they're on 12:22 < SourDoughB> As a newb, I agree on the usefulness :) 12:36 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 265 seconds] 12:41 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket 12:51 < belcher> im listening to your podcast on unhashedpodcast waxwing 12:52 < belcher> https://www.unhashedpodcast.com/episodes/adam-gibson-join-market-privacy-open-networks if anyone is interested 12:52 < SourDoughB> haha, same here :) 13:19 < kristapsk> --version done, https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/466, now I can also probably listen to podcasts :) 13:41 < waxwing> kristapsk, thanks 13:54 < waxwing> also thanks takinbo for that custom script update i'll check it over shortly 14:16 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 14:38 -!- Giszmo [~leo@122-58-98-6-adsl.sparkbb.co.nz] has joined #joinmarket 14:39 -!- Giszmo [~leo@122-58-98-6-adsl.sparkbb.co.nz] has quit [Client Quit] 15:03 -!- Xeha [~Xeha@unaffiliated/k1773r] has quit [Ping timeout: 252 seconds] 15:05 -!- Xeha [~Xeha@unaffiliated/k1773r] has joined #joinmarket 15:07 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 15:47 -!- SourDoughB [027e398c@2.126.57.140] has quit [Remote host closed the connection] 16:56 -!- mr_paz [~mr_paz@24.14.251.223] has joined #joinmarket 17:26 -!- AgoraRelay [~jmrelayfn@p5DE4A50C.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds] 17:27 -!- CgRelayBot [~CgRelayBo@p5DE4A50C.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds] 17:41 -!- AgoraRelay [~jmrelayfn@p5DE4A6AB.dip0.t-ipconnect.de] has joined #joinmarket 17:41 -!- CgRelayBot [~CgRelayBo@p5DE4A6AB.dip0.t-ipconnect.de] has joined #joinmarket 18:15 -!- MaxSan [~four@185.93.182.171] has joined #joinmarket 19:52 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 19:52 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #joinmarket 21:20 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has quit [Remote host closed the connection] 22:04 -!- mr_paz [~mr_paz@24.14.251.223] has quit [Ping timeout: 265 seconds] 22:46 -!- SourDoughB [027e398c@2.126.57.140] has joined #joinmarket