--- Log opened Wed May 06 00:00:14 2020 00:03 < HackRelay> [hackint-irc/user] a tumble has been stuck for hours and keeps giving that error, then saying stall detected and trying again 00:05 -!- achow101 [~achow101@unaffiliated/achow101] has joined #joinmarket 00:41 -!- JenSelter [4d410d55@gateway/web/cgi-irc/kiwiirc.com/ip.77.65.13.85] has joined #joinmarket 00:43 -!- JenSelter [4d410d55@gateway/web/cgi-irc/kiwiirc.com/ip.77.65.13.85] has quit [Client Quit] 00:53 < DSRelBot> [DS/AlexCato] either the irc connection is not working on the bot, or the available bots can't fulfill your criteria for coinjoins. Reasons possible for that: 00:53 < DSRelBot> [DS/AlexCato] maybe too few offering your desired join amount (too high, e.g. way above 100 BTC or too low, e.g. below 0.01 btc or so) 00:54 < DSRelBot> [DS/AlexCato] or you have fee settings which rule out most of the makers, e.g. you're willing to pay 100 sat max for a coinjoin, which most makers will not do 01:40 -!- chad2000 [daa64b0d@218-166-75-13.dynamic-ip.hinet.net] has quit [Remote host closed the connection] 02:02 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer] 03:14 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has joined #joinmarket 03:22 -!- HaileyBiwin [c8c3a2f2@gateway/web/cgi-irc/kiwiirc.com/ip.200.195.162.242] has joined #joinmarket 03:24 -!- HaileyBiwin [c8c3a2f2@gateway/web/cgi-irc/kiwiirc.com/ip.200.195.162.242] has quit [Client Quit] 03:33 -!- kristapsk___ is now known as kristapsk 04:42 < waxwing> --> [DS/AlexCato] or you have fee settings which rule out most of the makers, e.g. you're willing to pay 100 sat max for a coinjoin, which most makers will not do <-- wait, where are you getting that? have i forgotten something? 04:43 < waxwing> makers either contribute or not to the network fee, but it's entirely the taker's choice what the feerate is, again, unless i forgot something 04:44 < waxwing> oh! i think you meant the coinjoin fee? 04:44 < waxwing> not sure why i was confused about that, sorry 04:49 < waxwing> user - irc connection problems should show up on the terminal as regular disconnection messages, but i agree it is at least possible that that could be a cause of issues. do you use the tor hidden service connections to the IRC servers (both)? 04:49 < waxwing> further, there is a tweaking mechanism that should change either the coinjoin amount size or the number of counterparties in case of failure, which can result in correcting the problem, but it takes a long time. retries are about 20 minutes apart by default iirc. 04:50 -!- jonatack_ [~jon@37.166.24.197] has joined #joinmarket 04:51 < waxwing> if problems are caused by inability to source commitments, you should see a detailed message displayed about that (also stored in commitments_debug.txt file). 04:52 < waxwing> also worth mentioning that in cases where for some reason it cannot continue right now, it is not a bad idea to restart: stop (abort on gui or just ctrl-c on command line) then (a) on CLI run the same command with the same parameters but append --restart or (b) on GUI load schedule file ~/.joinmarket/logs/TUMBLE.schedule and the tumble will continue from where it left off. 04:53 -!- jonatack [~jon@37.164.75.174] has quit [Ping timeout: 256 seconds] 04:54 < waxwing> alexcato's earlier points are very valid of course; i note though he quoted 0.01 whereas i think realistically 0.001-0.005 is where you start hitting problems, i can't imagine 0.01 ever being an issue. 05:00 < DSRelBot> [DS/AlexCato] yes, you're right of course that 0.01 is fine; agree with that. Below that you'll start hitting problems, I just wasnt so sure *how much* below that, so that's why I went with 'below 0.01' 05:02 -!- jonatack_ [~jon@37.166.24.197] has quit [Quit: jonatack_] 05:02 < DSRelBot> [DS/AlexCato] and in yg-privacyenhanced, the minimum CJ amount accepted is 0.01 by default 05:03 < DSRelBot> [DS/AlexCato] and since defaults usually arent changed... it indeed will get hard to do joins below that amount with a reasonable amount of makers 05:03 < DSRelBot> [DS/AlexCato] interesting, the basic YG script defaults to 0.001 05:04 < DSRelBot> [DS/AlexCato] maybe it would make sense to default to the same val, and I cant see a good reason why it shouldnt be 0.001 in the yg-privacyenhanced too 05:05 < DSRelBot> [DS/AlexCato] also checked the current orders on ob-watcher: anything above 0.001 should indeed be fine. There's loads of makers supporting it, so waxwing is more right with his range estimation than I was 05:17 -!- jonatack [~jon@37.166.24.197] has joined #joinmarket 05:21 -!- jonatack_ [~jon@134.19.179.195] has joined #joinmarket 05:21 -!- jonatack [~jon@37.166.24.197] has quit [Ping timeout: 272 seconds] 05:21 -!- jonatack_ [~jon@134.19.179.195] has quit [Client Quit] 05:22 -!- jonatack [~jon@134.19.179.195] has joined #joinmarket 05:43 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:199d:ea40:f2ff:fe85:d2dc] has quit [Quit: WeeChat 2.6] 05:43 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:199d:ea40:f2ff:fe85:d2dc] has joined #joinmarket 06:55 < waxwing> AlexCato oh, i was completely unaware that 0.01 was the default min on the yg-priv (with randomization ofc). it'd probably be better if that changed. 06:56 < waxwing> in the nature of things, there are a lot of people who want to at least try joins with sub $100, unsurprisingly. woudl be good to give them as wide a spread of makers as is reasonable. 06:57 < waxwing> ok yeah i see you agree. 06:57 < belcher> probably when that default was set 0.01 btc was worth much less 07:26 < kristapsk> i've always prefered 0.001 btc as minimum in current low txfee environment 08:09 < waxwing> AlexCato do you remember doing this: https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/383 and do you remember what you thought about how it changes the fee estimate message that comes after it, using options.txfee? 09:47 -!- viasil [~nobody@134.19.189.124] has quit [Ping timeout: 240 seconds] 09:54 -!- viasil [~nobody@134.19.189.124] has joined #joinmarket 10:02 -!- viasil [~nobody@134.19.189.124] has quit [Ping timeout: 264 seconds] 10:03 -!- viasil [~nobody@134.19.189.124] has joined #joinmarket 10:19 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket 10:19 -!- undeath [~undeath@hashcat/team/undeath] has quit [Client Quit] 10:59 < HackRelay> [hackint-irc/user] ok so it kept getting ABORT:Could not find orders to complete transaction over and over until finally I got Failed to source a commitment because all my uxtos were used too many times 11:01 < HackRelay> [hackint-irc/user] using all default settings for the tumbler 11:09 < HackRelay> [hackint-irc/user] If it was the IRC connection would it use up uxtos? I am on tor - whonix 11:09 < HackRelay> [hackint-irc/user] I n the log I also see: ERROR not enough liquidity in the orderbook 11:10 < HackRelay> [hackint-irc/user] The input was around .02 12:26 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket 12:28 < waxwing> user did you change any settings in the joinmarket.cfg (in ~/.joinmarket/)? 12:28 < DSRelBot> [DS/AlexCato] .02 should easily work. Do you see any other errors or warning in the log? 12:30 < waxwing> also could you show us your MESSAGING section in joinmarket.cfg. there's nothing security sensitive in that section, so pastebin it or whatever is fine. 12:34 < DSRelBot> [DS/AlexCato] about this, waxwing: "do you remember what you thought about how it changes the fee estimate message that comes after it, using options.txfee?" 12:35 < DSRelBot> [DS/AlexCato] yes, it changes the message to exactly what it used to calculate, either from the joinmarket.cfg-config or the cli option (the latter takes priority) 12:35 < DSRelBot> [DS/AlexCato] you can see it here: https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/5a082a07edac4fef4399663c4b722c4045f9ccd3/scripts/sendpayment.py#L142 . A few lines before that, the cli option overrides the config file if necessary 12:38 < waxwing> alexcato are you pointing at master there? i think so? 12:39 < waxwing> i was pointing specifically at the code as in the PR because i had been trying to trace through the sequence of changes. 12:40 < waxwing> as far as i could tell, that change updated it so that options.txfee could be overriden, and in that case it was used to set the config `tx_fees` var, which is fine - but it seemed to still be the case that the same value was used as a per-participant txfee estimator to decide whether to emit the warning here: https://github.com/AlexCato/joinmarket-clientserver/blob/0ab5b6560c4161062b719f598caa7ea26c79ae11/scripts/sendpayment.py#L151-L157 12:41 < waxwing> note that after that usage, to print a warning if necessary, the Taker code (sendpayment here) doesn't use it further. unless i missed something. 12:43 < DSRelBot> [DS/AlexCato] oh, interesting. This seems like an oversight. In my answer, Ididnt think of that message, but the other one I linked 12:45 < waxwing> this is related: https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/536#issuecomment-624610497 12:45 < waxwing> (and is why it's cropping up now) 12:48 < DSRelBot> [DS/AlexCato] though, i think my change did not override options.txfee 12:48 < DSRelBot> [DS/AlexCato] as you can see here in the changes, the only *real* changes were to sendpayment and tumbler scripts: https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/383/files 12:49 < DSRelBot> [DS/AlexCato] it does re-set the config of the joinmarket.cfg, but just temporarily for tumlber & sendpayment via this: 12:49 < DSRelBot> [DS/AlexCato] jm_single().config.set("POLICY", "tx_fees", str(options['txfee'])) 12:50 < DSRelBot> [DS/AlexCato] the linked comment was about payjoin though - possibly it ignores the cli txfee setting? 12:50 < DSRelBot> [DS/AlexCato] have to read the rest of the thread first, but there should be no effect if the fee isnt set on CLI 12:54 < waxwing> "didn't override". oh yes, i see. but .. how does this work, if a user specifies say 10000 so as to have tx_fees be that, then it will not be default, so the section `if options.tx_fee == -1` will not apply, so it will be .. 12:54 < waxwing> ... something that is not suitable as an estimate of the per-participant cost, right? 12:55 < waxwing> like it might be '3' 12:58 < DSRelBot> [DS/AlexCato] correct. This seems like another thing that could be improved: if the txfee it set via CLI, it does not display any tx fee estimation at all 12:58 < DSRelBot> [DS/AlexCato] though it arguably isnt really needed either, as the user did just specify the value. But maybe would still be nice to mirror that back 13:01 < waxwing> yes. but i am mostly concerned about the warning. 13:01 < waxwing> sorry doing two things at once here, a bit slow. 13:02 < waxwing> i don't want the warning to not show if it should show. 13:05 < HackRelay> [hackint-irc/user] @waxwing These are my servers - https://pastebin.com/imS2Ew6a 13:06 < HackRelay> [hackint-irc/user] would IRC issues cause the uxtos to get used up? 13:07 < waxwing> yes i understand the question. i didn't answer it immediately because the way i see it, it is possible but isn't usual/normal, a bit tricky to figure out. 13:07 < waxwing> so your server2 looks a bit wrong. you have socks5 false. 13:07 < HackRelay> [hackint-irc/user] it shows these though first so it seems to be connecting INFO:Received offers from joinmarket pit INFO:Preparing bitcoin data choosing sweep orders for total_input_value = 13:08 < HackRelay> [hackint-irc/user] I'm in whonix so no socks5 13:08 < waxwing> what i know is that if both are hidden service, and you actually have the tor part workign correctly, then it works. 13:08 < waxwing> ok 13:08 < waxwing> are you gettin any "nick signature verification failed" messages during the flow of debug messages here. 13:08 < HackRelay> [hackint-irc/user] all the other transactions went through - then this started happening 13:08 < HackRelay> [hackint-irc/user] then it shows orderlist = but there are only two in there 13:08 < HackRelay> [hackint-irc/user] then ERROR not enough liquidity in the orderbook 13:09 < HackRelay> [hackint-irc/user] Yes lots of nick signature verification failed 13:10 < waxwing> user ok. can you test whether it's possible to have both servers running over tor. 13:10 < waxwing> because i find that that is reliable. we have a specific bug causing these nick signature verification failures. 13:10 < waxwing> i keep asking for someone else to fix it for me because i'm so busy :) 13:10 < waxwing> they seem to happen specifically on the clearnet server of one of the IRC servers. i know what causes it. 13:11 < waxwing> i can't remember which one. 13:11 < waxwing> i can't 100% say that that would, or wouldn't, cause commitments to get used up. 13:11 < waxwing> it depends on the exact mechanism by which disconnection/communication failure is occurring. it looks like it may be happening to you. 13:12 < waxwing> use both Tor hidden service and do a single test coinjoin. i believe it will fix it. 13:12 < waxwing> and i appeal again to other developers to help with fixing this bug. (although, i repeat, i don't have 100% information on this case so i don't know 100% that that is causing your problem, but it does seem likely) 13:15 < waxwing> (i have literally been trying coinjoins today, so i know it *should* work fine on Tor. no nick sig failures) 13:20 < waxwing> oh i forgot to mention, to get more commitments available you can do a self transfer or a transfer from another wallet. other way is external commitments but it's a messy thing that i wouldn't recommend 14:34 < HackRelay> [hackint-irc/user] @waxwing you mean both using the onion DNS? I am connecting via tor to both servers but for one I use their onion address 14:58 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has quit [Quit: Leaving] 15:06 -!- viasil [~nobody@134.19.189.124] has quit [Ping timeout: 256 seconds] 15:07 < waxwing> sorry yes i meant onion on both 15:11 -!- viasil [~nobody@134.19.189.124] has joined #joinmarket 16:05 < qubenix> i was thinking about swapping out some of my coins from my maker with funds in cold storage, but i'm thinking about fidelity bonds and wondering if i'm better off not touching them. or will the utxos that go into cold storage in the near future be eligible by the time fidelity bonds are implemented? 16:14 < belcher> it shouldnt matter i think 16:14 < belcher> the history of a coin doesnt matter for fidelity bonds 16:15 < belcher> only where that coin is now (e.g. in a timelocked address) 16:32 < qubenix> oh, thanks belcher. i thought it had something to do with the age of the utxo or something. 16:54 -!- jonatack [~jon@134.19.179.195] has quit [Ping timeout: 246 seconds] 16:56 -!- jonatack [~jon@37.173.38.62] has joined #joinmarket 17:14 -!- viasil [~nobody@134.19.189.124] has quit [Ping timeout: 246 seconds] 17:19 -!- viasil [~nobody@134.19.189.124] has joined #joinmarket 17:38 -!- HackRelay [~jmrelayha@p5DE4A3FD.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds] 17:40 -!- DSRelBot [~DSRelBot@p5DE4A3FD.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds] 17:51 -!- HackRelay [~jmrelayha@p5DE4A2C0.dip0.t-ipconnect.de] has joined #joinmarket 17:51 -!- DSRelBot [~DSRelBot@p5DE4A2C0.dip0.t-ipconnect.de] has joined #joinmarket 22:22 -!- rdymac [uid31665@gateway/web/irccloud.com/x-imdwinpazhcqdmdj] has quit [Quit: Connection closed for inactivity] 22:25 -!- jon-r__ [~jon-r@104.129.29.26] has joined #joinmarket 22:55 -!- tlo1337 [~tlo1337@142.183.170.75] has joined #joinmarket 22:59 < tlo1337> Also after getting JM setup complete, I know get this error: 2020-05-06 22:57:53,520 [ERROR] Unhandled connection error [Errno 111] Connection refused 22:59 < tlo1337> 2020-05-06 22:57:53,521 [ERROR] Failure to get blockheight from Bitcoin Core: 22:59 < tlo1337> 2020-05-06 22:57:53,522 [ERROR] ConnectionRefusedError(111, 'Connection refused') 22:59 < tlo1337> followed by some traceback text 22:59 < tlo1337> is this also normal while running yg? 23:24 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 272 seconds] 23:25 -!- k3tan [~pi@unaffiliated/k3tan] has joined #joinmarket --- Log closed Thu May 07 00:00:14 2020