--- Log opened Fri Aug 13 00:00:37 2021 00:27 < waxwing> no comments on corrections on the release notes then? i'll just push it out today if so 00:27 < waxwing> s/on/or/ 01:03 -!- Floofie [~Thunderbi@c-66-30-49-23.hsd1.ma.comcast.net] has joined #joinmarket 01:59 < nobodyfks> I started the tumber and now it got stuck here: 2021-08-13 09:40:50,548 [INFO] ABORT:Could not find orders to complete transaction 01:59 < nobodyfks> 2021-08-13 09:40:50,549 [INFO] Taker not continuing after receipt of orderbook 01:59 < nobodyfks> but the program did not stop ? Am I still tumbling nothing happened for 20 minutes 02:01 -!- undeath [~undeath@user/undeath] has joined #joinmarket 02:06 -!- Floofie [~Thunderbi@c-66-30-49-23.hsd1.ma.comcast.net] has quit [Quit: Floofie] 03:19 -!- openoms [~quassel@gateway/tor-sasl/openoms] has quit [Remote host closed the connection] 03:19 -!- openoms [~quassel@gateway/tor-sasl/openoms] has joined #joinmarket 04:08 < waxwing> nobodyfks, take a look in ~/.joinmarket/logs/TUMBLE.log and TUMBLE.schedule 04:09 < waxwing> there will be at least a 20 minute wait whenever it fails, but it can happen that it won't succeed after several tries, if something specific is not working. do you see "Failed to source commitment"? or "not enough counterparties" type errors? 04:10 < waxwing> if after a while you can't see forward progress, you can try stopping the script, and restarting by taking the previous command and appending --restart, it will try to continue (this is described in the docs) 04:10 < nobodyfks> thanks waxwing 04:10 < nobodyfks> when I add another utxo during the tumble process, will it be considerd automatically ? 04:11 < waxwing> ah, good question. actually yes, in general, but that's kinda tricky. 04:11 < nobodyfks> ok, I will see, I just added one 04:11 < nobodyfks> to mixdepth 0 04:11 < waxwing> like if your tumbler is running on mixdepth 1, and you add a utxo to mixdepth 2, it should be OK 04:11 < waxwing> yeah adding to the mixdepth that is currently in process, tbh i think that might well screw it up. 04:11 < nobodyfks> ok 04:11 < waxwing> because it tries to calculate amount fractions of the total in the mixdepth at the start 04:12 < waxwing> and if you change the total in the mixdepth during, it will probably (not always) get confused about what amount to use. 04:12 < waxwing> so i'd disrecommend it, although it might work sometimes 04:12 < nobodyfks> ok I got this in the log: Added utxos= .... 04:12 < nobodyfks> I am using testnet so I am playing around 04:12 < waxwing> yeah it "works" but like i say it tries to figure out the fractions in the individual txs in advance. so it'll be a bit screwy. 04:13 < nobodyfks> thanks :) 05:22 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed] 05:25 -!- undeath [~undeath@user/undeath] has quit [Quit: WeeChat 3.1] 05:41 -!- jonatack [~jonatack@user/jonatack] has joined #joinmarket 07:06 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed] 07:18 -!- blkncd [sid505676@id-505676.brockwell.irccloud.com] has left #joinmarket [] 07:18 -!- jonatack [~jonatack@user/jonatack] has joined #joinmarket 07:20 < davterra> Is there typically a lag in time between a maker being selected for a coinjoin, and that event showing up in the yigen-statement.csv? My maker/offer was used about an hour ago and the resulting tx is confirmed, but it is not appearing in my yigen file. 07:27 < belcher> that event gets added to the .csv when the transaction is confirmed, however it doesnt get added if the bot gives up waiting 07:28 < belcher> in general the statement isnt always reliable and `wallet-tool.py history` is the most reliable way to see 07:35 < davterra> ok, thank you 08:05 < waxwing> belcher, got a chance to scan the release notes and give an ACK? 08:05 < waxwing> did it yesterday and want to push it out now 08:05 < belcher> will look 08:08 < belcher> ok iv read it, and acked 08:08 < waxwing> ok just tweaking a couple v. minor things then i'll push release in next few hours 08:08 < waxwing> thanks 08:16 < waxwing> belcher, the two lines under "The value of a bond after the timelock after expiry is:" in https://gist.github.com/chris-belcher/87ebbcbb639686057a389acb9ab3e25b are contradictory? 08:17 < waxwing> since the 1s cancel, the two lines are identical except t is replaced with t-L ? 08:17 < belcher> the first line is meant to imply the second line 08:18 < belcher> but you're right something is wrong since the arguments to the exp() function are different 08:18 < belcher> reading around, its pretty clear to me the mistake is in the first line, and "exp(rt)" should be "exp(r(t-l))" 08:19 < belcher> exp(rt) is definitely because t is calender... only t-L or T makes sense there (i.e. some kind of duration) 08:19 < belcher> calender time* 08:20 < belcher> ill edit it now 09:21 < waxwing> https://github.com/JoinMarket-Org/joinmarket-clientserver/releases/tag/v0.9.1 09:21 < waxwing> https://x0f.org/web/statuses/106744577443864890 09:21 -!- mode/#joinmarket [+o waxwing] by ChanServ 09:21 -!- 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.9.1 | Also on ncwkrwxpq2ikcngxq3dy2xctuheniggtqeibvgofixpzvrwpa77tozqd.onion:6667 09:21 -!- mode/#joinmarket [-o waxwing] by ChanServ 09:39 -!- Floofie [~Thunderbi@c-66-30-49-23.hsd1.ma.comcast.net] has joined #joinmarket 10:02 -!- nobodyfks [~Guest72@dslb-088-067-057-219.088.067.pools.vodafone-ip.de] has quit [Quit: Client closed] 10:37 -!- SomeFellow [~SomeFello@194.54.28.203] has joined #joinmarket 10:45 < SomeFellow> Is the OB watcher particularly broken today, with regards to fidelity bonds? Normally (as in, a couple of days ago), you could get more-or-less accurate data by restarting the OBW first, but it's been jumping between 0 and 9 FBs all day (always checked immediately after a restart). Seeing my offer on that list without a FB is making me nervous. 10:49 < belcher> i see 10 fidelity bonds just now 10:50 < belcher> yesterday it was ~27 10:50 < belcher> that maker with the 3 year locktime with ~12btc is gone 10:50 < belcher> i remember it saying ~50btc locked up and now its ~36btc 10:51 < belcher> not sure whats going on, something for sure 10:56 < JoinMarketRelay> [hackint/s45rutz7e] Sounds weird indeed. is the obwatcher refreshed good/often enough? may some are even not online 24/7 or moving to other systems. wouldn't feel very comfortable with that lots or more in hot wallets :D 10:59 < belcher> if it was just one or two bots disappearing you could write it off as that they shut down, but i think we went from ~25 bots down to 10 10:59 < belcher> so im thinking maybe the irc servers are blocking the messages or something like that 10:59 < SomeFellow> Restarted my YG (and then the OB), and that made my FB reappear. 11:00 < SomeFellow> (Only restarting the OB didn't) 11:19 -!- Floofie [~Thunderbi@c-66-30-49-23.hsd1.ma.comcast.net] has quit [Quit: Floofie] 13:37 -!- ufotofu [~ufotofu@user/ufotofu] has quit [Quit: WeeChat 2.7.1] 13:38 -!- SomeFellow [~SomeFello@194.54.28.203] has quit [Ping timeout: 248 seconds] 18:17 -!- belcher_ [~belcher@user/belcher] has joined #joinmarket 18:20 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 256 seconds] --- Log closed Sat Aug 14 00:00:38 2021