--- Log opened Fri Mar 20 00:00:28 2020
00:14 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 246 seconds]
00:42 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #joinmarket
01:00 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
01:02 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket
02:39 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
03:17 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket
04:06 -!- Allene64Cummings [~Allene64C@ns334669.ip-5-196-64.eu] has joined #joinmarket
04:41 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Remote host closed the connection]
05:18 -!- belcher_ [~user@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]
05:19 -!- belcher_ [~user@unaffiliated/belcher] has joined #joinmarket
05:37 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
05:48 -!- Allene64Cummings [~Allene64C@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 250 seconds]
05:58 -!- DSRelBot_ [~DSRelBot@p5DE4A3A0.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
05:58 -!- DSRelBot [~DSRelBot@p54866D31.dip0.t-ipconnect.de] has joined #joinmarket
05:58 -!- HackRelay [~jmrelayha@p54866D31.dip0.t-ipconnect.de] has joined #joinmarket
05:58 -!- HackRelay_ [~jmrelayha@p5DE4A3A0.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
06:09 -!- tlo1337 [~tlo1337@142.180.9.134] has joined #joinmarket
06:16 < tlo1337> Hello again:) hope everyone is doing well during all this.. I'm curious though about something that happened when CJIng on the Taker side
06:16 < tlo1337> What happened was I chose destination addresses (separate from JM) that weren't part of mixdepths in my JM wallet, but when the CJ finished it chose one address in my last mixdepth as a desitination address in my JM wallet
06:16 < tlo1337> The addresses in my JM wallet are all segwit and the addresses i chose as my destination addresses were bech32 so not sure if that matters here. I thought I was going to get all my uxtos on 3 destination addresses but it just chose one in my JM wallet and now it's all on that utxo so just curious as to if there is maybe something I need to be doing
06:16 < tlo1337>  Also, I'm assuming it will probably be harder to run the yield generator now, with 1 utxo rather than 3 which was what i was hoping for, is that correct?
06:25 < waxwing> tlo1337, on that last point, no, for a yg it doesn't matter if the coins are in 1 or 3.
06:26 < waxwing> but the previous part of the description i can't make any sense of. you had 3 destination addresses for the tumbler (you ran 'multi join' in Qt I'm assuming?), but none of the coins were sent to them? or some of them were?
06:26 < waxwing> in the schedule (the text at the top of the multi join tab), that is the "schedule", do you see those destination addresses in that schedule?
06:27 < waxwing> also, has the schedule finished running (you should see a notification "all transactions completed successfully" when it does)?
08:26 < tlo1337> Okay that's good
08:28 < tlo1337> Of course you can't haha! Yes I chose 3 bech32 destination addresses for the tumbler (yes multijoin in Qt), and none of the coins were sent to them. Instead, they were all sent to one segwit address in my last mixdepth.
08:29 < tlo1337> The schedule did have the destination addresses I chose visible on the schedule there yes.
08:30 < waxwing> tlo1337, you could take a look at TUMBLE.schedule, it sounds like the tumble didn't complete, it should go through many transactions over a long period
08:30 < waxwing> which would be in ~/.joinmarket/logs/TUMBLE.schedule, same information as was displayed in the multi join tab
08:31 < waxwing> look at the last entry on each line. then read the tumblerguide.md in docs/ folder in the repo .. basically that last entry tells you whether that transaction completed.
08:31 < waxwing> in cases where a tumbler run did not complete (i.e. only some transactions completed, there is a --restart option as explained there, which is triggered automatically if you load that TUMBLE.schedule file in the multi-join tab
08:32 < waxwing> obviously some guesswork here as i don't see everything you see
08:38 < tlo1337> Okay I'm looking at the tumble schedule log and I see a lot of "Transaction attempt failed, tweaking schedule and trying again." so I guess it didn't complete. I just assumed it did since it seemed the tumbler was no longer active on Qt, and all the coins were in my last mixdepth in red as "cj-out", so I thought that meant it was done. To be honest I don't recall checking the terminal, so I should've done that I guess.
08:39 < waxwing> tlo1337, i was asking though for you to check the TUMBLE.schedule file, not the TUMBLE.log file (although that is interesting/useful of course)
08:40 < waxwing> and to check specifically the last entry on each line as per the description in tumblerguide.md, it should be either 0 or 1 or the txid
08:40 < tlo1337> oh shoot okay
08:40 < waxwing> a TODO is to make that text section at the top of the tumbler (multijoin) tab more readable for the user; at the moment it's a bunch of text that i'm sure most users don't pay attention to
08:41 < waxwing> there is an open issue for that since like 2017 probably
08:42 < waxwing> but it specifically shows you which transactions have completed; it's *fairly* normal to have a bunch of "transaction attempt failed, tweaking.."
08:42 < waxwing> but "fairly" normal, if you have that a lot, there might be something specific causing problems
08:42 < waxwing> for example: asking for very large numbers of counterparties is likely to cause timeouts
08:42 < waxwing> and asking for very small amounts can cause problems (or very high amounts) in terms of how many counterparties are available
08:43 < waxwing> anyway the --restart feature is also explained in tumblerguide.md , so if you haven't read all of that, please do.
08:43 < waxwing> if you have only a couple of transactions finished and the others didn't, then the --restart option may well be fine.
08:44 < waxwing> another thing to bear in mind is the timing; it is generally designed to run for at least ~ a day and is fine to run for several days.
08:44 < tlo1337> Okay I'm looking at the schedule now and yes I see many O's as the last entry on each line except the first one
08:45 < waxwing> ok so only the first transaction occurred. look at the timing settings.
08:45 < waxwing> there is a multiplier on the timing of the first transaction(s), which sweep any funds from one mixdepth to another as the first step of the process.
08:45 < tlo1337> I bet there is haha! But yes would be helpful for less advanced users.
08:46 < waxwing>  --stage1-timelambda-increase=STAGE1_TIMELAMBDA_INCREASE
08:46 < waxwing>                         Stage 1 sweep coinjoins have a longer wait time. This
08:46 < waxwing>                         parameter controls by what factor longer is this
08:46 < waxwing>                         average wait time compared to stage2 coinjoins which
08:46 < waxwing>                         are controlled by `--timelambda`, default=3
08:46 < tlo1337> I didn't ask for a large number of counterparties or anything, just used default settings, but yes will read through the tumblerguide.md
08:46 < waxwing> this setting, visible in either the wizard on the gui (make sure to see the tooltips) or the --help on CLI, by default multiplies the average time wait by 3 for that first transaction
08:47 < waxwing> if you just let it run for a while, the first tx went through and then it started waiting, maybe you just shut it down prematurely
08:47 < tlo1337> Yes I think I might try the restart option first.
08:47 < waxwing> note the schedule text also shows the wait time
08:47 < waxwing> belcher_, can explain the logic of this longer wait time
08:49 < tlo1337> Okay I understand, that makes sense. I think that was the case, that I shut it down prematurely.
08:51 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has quit [Remote host closed the connection]
08:51 < waxwing> i guess there is a valid practical point there also: if people don't want to leave their comps on 24hrs a day, the --restart feature is useful just for that. unfortunately the wait times will not account for you shutting down and restarting though.
08:55 < waxwing> but otoh the wait times are *after* a particular tx, so e.g. if you shut down after tx1 and then --restart later, tx2 will happen immediately. so in theory you could just ignore all the wait times and control the time of each tx manually. bit impractical of course.
09:10 < tlo1337> Yes there is that option, but true that it's impractical. Think that TODO would be useful, along with a reminder of sorts that it needs several days to complete and to not shut it down prematurely, but if you do you have the restart option. I'm trying to think of the easiest way to provide that info without doing too much work and I think maybe an FAQ tab next to Wallet and About would be quite helpful for users looking for common issues they can 
09:10 < tlo1337> quickly troubleshoot themselves.
09:32 < waxwing> tlo1337, yeah it could be an idea. i think sort of, formatting the schedule informatoin would only be *slightly* more work than that, and would make more sense, though.
10:00 -!- avril [wha@unaffiliated/avril] has quit [Remote host closed the connection]
10:19 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has joined #joinmarket
10:35 < belcher_> the longer wait time for stage1 coinjoins is so they're less linked to each other and to the with-change-coinjoins
10:35 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
10:36 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #joinmarket
10:59 -!- MaxSan [~four@185.156.175.171] has joined #joinmarket
11:02 -!- DSRelBot [~DSRelBot@p54866D31.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
11:02 -!- rdymac_ [~britoair@90.162.99.55] has quit [Quit: ZNC 1.7.5 - https://znc.in]
11:03 -!- HackRelay [~jmrelayha@p54866D31.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
11:03 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Remote host closed the connection]
11:03 -!- DSRelBot [~DSRelBot@p54866CED.dip0.t-ipconnect.de] has joined #joinmarket
11:04 -!- HackRelay [~jmrelayha@p54866CED.dip0.t-ipconnect.de] has joined #joinmarket
11:08 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
11:09 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #joinmarket
11:18 -!- avril [~av@ivana.humpalot.org] has joined #joinmarket
11:18 -!- avril [~av@ivana.humpalot.org] has quit [Changing host]
11:18 -!- avril [~av@unaffiliated/avril] has joined #joinmarket
11:45 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
11:46 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #joinmarket
12:31 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 246 seconds]
12:36 -!- coconutanna [~coconutan@gateway/tor-sasl/coconutanna] has quit [Remote host closed the connection]
12:36 -!- coconutanna [~coconutan@gateway/tor-sasl/coconutanna] has joined #joinmarket
12:43 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
12:46 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #joinmarket
13:00 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Remote host closed the connection]
13:02 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
13:04 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
13:04 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #joinmarket
13:13 -!- MaxSan [~four@185.156.175.171] has quit [Ping timeout: 250 seconds]
13:17 -!- slivera [~slivera@217.138.204.104] has joined #joinmarket
13:48 -!- rdymac [~britoair@90.162.99.55] has joined #joinmarket
13:48 -!- rdymac is now known as Guest87202
14:17 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket
16:25 -!- fiatjaf [~fiatjaf@2804:7f2:2981:26c1:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 246 seconds]
16:25 -!- fiatjaf [~fiatjaf@2804:7f2:2981:26c1:ea40:f2ff:fe85:d2dc] has joined #joinmarket
16:37 -!- fiatjaf [~fiatjaf@2804:7f2:2981:26c1:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 246 seconds]
16:37 -!- fiatjaf [~fiatjaf@2804:7f2:2981:26c1:ea40:f2ff:fe85:d2dc] has joined #joinmarket
16:40 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Remote host closed the connection]
16:41 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
16:45 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Ping timeout: 246 seconds]
16:53 -!- openoms [~quassel@195.140.215.182] has quit [Remote host closed the connection]
17:17 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.7.1]
17:23 -!- Sentineo [~Undefined@unaffiliated/sentineo] has quit [Ping timeout: 258 seconds]
17:32 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
17:33 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #joinmarket
17:39 -!- Sentineo [~Undefined@unaffiliated/sentineo] has quit [Remote host closed the connection]
19:01 -!- DSRelBot [~DSRelBot@p54866CED.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
19:02 -!- HackRelay [~jmrelayha@p54866CED.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
19:06 -!- HackRelay [~jmrelayha@p5DE4AB46.dip0.t-ipconnect.de] has joined #joinmarket
19:06 -!- DSRelBot [~DSRelBot@p5DE4AB46.dip0.t-ipconnect.de] has joined #joinmarket
21:12 -!- stoner19 [~stoner19@unaffiliated/stoner19] has quit [Ping timeout: 256 seconds]
22:48 -!- opal [~wowaname@volatile/founder/wowaname] has quit [Ping timeout: 240 seconds]
22:51 -!- opal [~wowaname@volatile/founder/wowaname] has joined #joinmarket
22:52 -!- stoner19 [~stoner19@vmi221374.contaboserver.net] has joined #joinmarket
22:52 -!- stoner19 [~stoner19@vmi221374.contaboserver.net] has quit [Changing host]
22:52 -!- stoner19 [~stoner19@unaffiliated/stoner19] has joined #joinmarket
22:58 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 256 seconds]
22:59 -!- k3tan [~pi@unaffiliated/k3tan] has joined #joinmarket
23:16 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 240 seconds]
23:18 -!- felix34_ [~muh@5.2.76.19] has joined #joinmarket
23:19 -!- opal [~wowaname@volatile/founder/wowaname] has quit [Ping timeout: 240 seconds]
23:19 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has quit [Ping timeout: 240 seconds]
23:19 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
23:19 -!- coconutanna [~coconutan@gateway/tor-sasl/coconutanna] has quit [Ping timeout: 240 seconds]
23:19 -!- k3tan [~pi@217.138.204.84] has joined #joinmarket
23:19 -!- k3tan [~pi@217.138.204.84] has quit [Changing host]
23:19 -!- k3tan [~pi@unaffiliated/k3tan] has joined #joinmarket
23:20 -!- opal [~wowaname@volatile/founder/wowaname] has joined #joinmarket
23:20 -!- coconutanna [~coconutan@gateway/tor-sasl/coconutanna] has joined #joinmarket
23:21 -!- felix34 [~muh@5.2.76.19] has quit [Ping timeout: 260 seconds]
23:22 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has joined #joinmarket
23:32 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #joinmarket
--- Log closed Sat Mar 21 00:00:29 2020