--- Log opened Fri Jun 18 00:00:41 2021
00:23 -!- belcher_ is now known as belcher
01:10 -!- SomeGuy [~SomeGuy@194.54.28.203] has joined #joinmarket
01:12 -!- SomeGuy is now known as SomeOtherGuy
01:12 < SomeOtherGuy> Is there a way to see your mixdepth balances without having to stop the YG?
01:17 < belcher> SomeOtherGuy yes just run wallet-tool 
01:26 < SomeOtherGuy> belcher Won't the wallet lock file interfere?
01:31 < belcher> no because that only applies if something is being changed, wallet-tool doesnt change anything it only displays
01:35 < SomeOtherGuy> Okay, thanks. That'll be very useful.
03:08 -!- undeath [~undeath@user/undeath] has joined #joinmarket
03:29 < SomeOtherGuy> Is the maxsize offered by my maker bot tied to a particular mixdepth (the biggest one)? Say I have 5BTC on MD0 and 10BTC on MD1, and am therefore advertising a maxsize of ~10BTC. If somebody comes along and wants to mix 4BTC, will it use the money from MD0? Or will it have to use (part of) the MD1 funds because they're the ones that were
03:29 < SomeOtherGuy> 'advertised'?
03:29 < SomeOtherGuy> I'm asking because I've ended up with my maker funds split between two adjacent mixdepths 40%/60%, and I'm wondering if the problem can resolve itself or if I'll have to intervene.
03:37 < undeath> the problem will resolve itself
03:37 < undeath> up until recently jm would have picked the first (lowest) mixdepth that has sufficient funds
03:39 < undeath> after a recent commit (will be in the next release) jm will pick mixdepths in a way to move funds into a common mixdepth if possible to maximize the maxsize
03:40 < SomeOtherGuy> Sounds good. Cheers.
04:22 < waxwing> if there are no further comments i'll squash and merge later tonight
04:23 < undeath> the release notes look good to me. thanks for putting that all together!
05:00 -!- undeath [~undeath@user/undeath] has quit [Quit: WeeChat 3.1]
12:58 < waxwing> release is up. belcher time for IRC channel topics.
12:58 < waxwing> if anyone wants to do reddit, thanks
12:59 -!- mode/#joinmarket [+o waxwing] by ChanServ
12:59 -!- waxwing changed the topic of #joinmarket to: JoinMarket: Improving bitcoin privacy since 2015 | https://github.com/Joinmarket-Org/joinmarket-clientserver | @joinmarket r/joinmarket | Logs: http://gnusha.org/joinmarket/ | Latest release 0.8.3 | Also on ncwkrwxpq2ikcngxq3dy2xctuheniggtqeibvgofixpzvrwpa77tozqd.onion:6667
12:59 -!- mode/#joinmarket [-o waxwing] by ChanServ
12:59 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] finally v0.8.3 hooray!
13:00 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] upgrading
13:12 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] btw. darkscience topic changed, but on hackint still says:  LATEST RELEASE v0.8.1
13:12 < waxwing> yes i pinged belcher , he has ops there
13:13 < waxwing> i don't
13:13 < waxwing> it'll be done shortly don't worry
13:13 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] ok great, because some still using 0xdeadbeed releases...
13:14 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] deadbeef*
13:15 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] on agorairc, there is no topic set at all.
13:53 < SomeOtherGuy> Just updated to the latest version, and trying to figure out what I did wrong. A size_factor of 0.05 (as opposed to the default 0.1) should result in less random swing, correct?
13:55 < SomeOtherGuy> Yet my minsize (set to the default 100k) is set closer to 6 million when I run privacyenhanced.
14:01 < SomeOtherGuy> Tried setting size_factor to 0 and restarting, and now my minsize is almost exactly 6 000 000.
14:21 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] someotherguy with size_factor to 0, the  minsize should be not change, even when running privacyenhanced yg
14:23 < SomeOtherGuy> That's what I figured, yeah. At first I thought I accidentally used a comma or something when changing the size_factor, but that wasn't the case. Then I tried it with 0, and 100 000 somehow turned into 6 000 000. So the problem seems to be with minsize, not size_factor.
14:28 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] minsize will now be always >=27300 sats at least.
14:29 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] if you try with less someotherguy, you should see this at startup: [WARNING]  Minsize was randomized to below dust; resetting to dust threshold: 0.00002730 BTC (2730 sat)
14:29 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] [WARNING]  Minsize was randomized to below dust; resetting to dust threshold: 0.00027300 BTC (27300 sat)
14:30 < SomeOtherGuy> Yeah, I meant that I set size_factor to 0, while keeping minsize at 100 000, and that resulted in an offered minimum size of 6 000 000 when I ran YG.
14:31 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] I understand and thats weird.
14:32 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] what does it change it to, if you set really low minsize just for the tests? like: minsize=27299
14:32 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] what will it result into
14:36 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] waxwing: the topic in darkscience #joinmarket says "Main channel on #joinmarket on irc.freenode.net or #joinmarket on hackint cwkrwxpq2ikcngxq3dy2xctuheniggtqeibvgofixpzvrwpa77tozqd.onion:6667 | THIS CHANNEL IS NOT BRIDGED, GO TO HACKINT " but the hackint address is wrong invalid. missing first letter! its:
14:36 <+JoinMarketRelay> ncwkrwxpq2ikcngxq3dy2xctuheniggtqeibvgofixpzvrwpa77tozqd.onion
14:39 < SomeOtherGuy> Correction: When I said 6 000 000 above (regarding my second attempt), it was actually 5 999 999.
14:39 < SomeOtherGuy> With all default settings (except minsize = 5000 and size_factor = 0): 1. I did not get the below dust warning you posted. 2. It warned me about how the mining fee contribution was too high to be profitable, and halved it (which it did not do on any previous attempt with a default/higher minsize. 3. The offered minimum size was still 5 999 999.
14:41 < waxwing> J546 oh thanks i'll fix it.
14:43 < waxwing> done
14:43 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] :)
14:45 < waxwing> SomeOtherGuy, the minsize for relfee is altered to keep the profit above zero, is your txfee setting zero?
14:45 < SomeOtherGuy> Wait, 2730 sat or 27300 sat?
14:46 < waxwing> i think it's actually 27300 (there is a confusion there, long story). but what exactly is going on here, you are gettnig a minsize of ~ 6M?
14:46 < waxwing> with relfee i take it?
14:46 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] minsize 27300 is the yg enforced dustlimit at the moment.
14:46 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
14:46 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #joinmarket
14:46 < SomeOtherGuy> waxwing Yeah, all default settings (except two), as I said above. So relfee and 100 miner contribution.
14:47 < waxwing> yeah but he's talking about getting minsize 6M for some reason
14:47 < SomeOtherGuy> But the profit >0 thing is just something I included to help troubleshoot the real issue.
14:48 < waxwing> set txfee to zero and txfee_factor to zero, and also mention exactly how you are changing those settings
14:48 < SomeOtherGuy> If it gives me that warning despite the public minsize of 6 million, it should mean that that part of the code reads the settings file minsize correctly (5000, in the attempt), I think.
14:49 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] yes
14:50 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] works, I'm right?
14:50 < waxwing> i couldn't parse that sentence SomeOtherGuy .
14:50 < waxwing> oh i get it.
14:50 < waxwing> but could you just mention exactly how you make the setting?
14:50 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] the code reads the settings file minsize correctly in your attemp
14:51 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] now as set
14:52 < SomeOtherGuy> Tried "set txfee to zero and txfee_factor to zero" while leaving the other altered settings unchanged, and I got the dust warning and the minsize set to 27k. I'll just post a screencap, should be easier.
14:52 < waxwing> https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/9517d9b2d7ab1d936226c6b27e98489cf418d7cd/jmclient/jmclient/yieldgenerator.py#L93-L94
14:53 < waxwing> linking that so you can see why, with extremely low rel cjfee (as default) and non zero txfee setting, you tend to get quite a big minsize
14:53 < waxwing> if you just set txfee and txfee factor to zero you should find it all behaves a lot more like you expect, i think.
14:53 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] oh, I missed that
14:54 < waxwing> people always find this confusing. this logic was there from the beginning of the project, and makes sense, it just results in surprisingly large minsizes with the very low default relfee settings we have nowadays
14:55 < waxwing> it's been well known for years that we really want to change how the whole 'txfee contribution' thing works, mostly just either ignore it or set it zero. you won't be punished for doing so, since taker just calculates the overall fee they have to pay to you.
14:56 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] once ago it was cjfee_r = '0.0002' # 0.02% fee now cjfee_r = '0.00002' # 0.002% fee as default
14:58 < waxwing> yes
14:58 < waxwing> at the beginning it was even much higher
15:00 < SomeOtherGuy> So would running the default settings in 0.8.2 have had the same result (minsize 5 999 999 sats)? I admit I've never looked that closely at the minsize, but that doesn't seem right.
15:00 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] I'm curios, whats the max acceptable fee is for the taker with default settings
15:02 < waxwing> SomeOtherGuy, yeah i'm pretty sure. none of the relevant settings/values/code changed there.
15:02 < waxwing> J546 you mean max cj fee? there is a warning somewhere that kicks in if the total cjfee is, i think, 2% of the cj value.
15:03 < waxwing> and there's the absurd fee per kilobyte for the txfee. there's quite a few things.
15:03 < waxwing> per maker there is max_cjfee_rel and max_cj_fee_abs which is their way of saying "i accept any price up to X"
15:04 < waxwing> which is the effective limit, the 2% thing was set early on as a "panic" but it isn't really needed any more.
15:05 < SomeOtherGuy> waxwing My yigen statement log shows CJs with a 'cj amount' of significantly less than 6 000 000 though. One of them (from 0.8.2) is only a little over 900 000.
15:05 < SomeOtherGuy> Ah, wait.
15:05 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] I understand, need to do my math than.
15:06 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] But can't find any max_cjfee_rel sorry.
15:07 < SomeOtherGuy> That was with different settings. I guess it's more realistic that I've been running a published minsize of 6kk for a few weeks without noticing (as opposed to several months).
15:07 < waxwing> sorry it's max_cj_fee_rel
15:07 < waxwing> i don't know how many people have txfee=0 SomeOtherGuy but i guess a lot of people do. you could look on ob-watcher. it makes it less confusing.
15:07 < waxwing> if they use absfee there is no such concern.
15:08 < waxwing> and they could also "fix" it by having signficantly higher relfee percentage.
15:09 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] someotherguy: you can find the minsize used in your logfolder by searching for offerlist=[{'oid': 0, 'ordertype': 'sw0reloffer', 'minsize':    and modifying orders. to_cancel=[]
15:09 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] to_announce=[{'oid': 0, 'ordertype': 'sw0reloffer', 'minsize':
15:13 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] ty waxwing, I now found it. MAX_DEFAULT_REL_FEE = 0.001 (0.1%)
15:15 < waxwing> sorry heh it's max_cj_fee_rel :) i got it wrong twice. https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/9517d9b2d7ab1d936226c6b27e98489cf418d7cd/jmclient/jmclient/configure.py#L244
15:16 < waxwing> it's commented out because the code will create a *random* one for the taker, if they don't set it.
15:16 < waxwing> we can't have everyone on the same default because makers would cluster under it.
15:17 < waxwing> the one you found is like the "starting" value that we randomize around
15:17 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] oh, I thought it used the 0.001 as default max. thanks for pointing out.
15:17 <+JoinMarketRelay> [hackint/J546rNPdB25zwXD2] if not set in config.
15:18 < waxwing> oh wait i think i remembered wrong. maybe we only randomize for abs, not rel? anyway.
15:23 < SomeOtherGuy> Checked the logs, and you're right. It's been publishing minsize 6 mil since I switched to reloffer a few weeks ago. Now that my minsize is back at 100k, hopefully the smaller transactions coming in will synergize with the new YG logic and quickly push all my scattered funds to a single mixdepth. Thanks for the help, both of you.
16:21 < belcher> updated topic on hackint
16:29 -!- SomeOtherGuy [~SomeGuy@194.54.28.203] has quit [Quit: Connection closed]
17:06 -!- belcher_ [~belcher@user/belcher] has joined #joinmarket
17:10 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 252 seconds]
23:33 -!- LittleBoy [~LittleOne@89.46.102.116] has joined #joinmarket
23:36 < LittleBoy> So I have joinmarket installed on ubuntu with bitcoin core running. when I try to run 'python joinmarket-qt.py' from /joinmarket-clientserver/scripts/ I get "Failed to setup joinmarket: JsonRpcConnectionError('authentication for JSON-RPC failed',)
23:36 < LittleBoy> It doesn't generate a .cfg file
23:36 < LittleBoy> Any ideas?
--- Log closed Sat Jun 19 00:00:43 2021