--- Log opened Fri Oct 01 00:00:23 2021 00:13 < openoms[m]> set the agora channel, hackint is working poorly: https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/1026/files 00:15 -!- bairen [~bairen@gateway/tor-sasl/bairen] has quit [Remote host closed the connection] 00:16 -!- bairen [~bairen@gateway/tor-sasl/bairen] has joined #joinmarket 00:21 -!- berndj [~berndj@ns2.linksynergy.co.za] has quit [Remote host closed the connection] 00:22 -!- berndj [~berndj@ns1.linksynergy.co.za] has joined #joinmarket 00:25 -!- stevenro- [~steven@irc.roose.io] has joined #joinmarket 00:27 -!- stevenroose [~steven@irc.roose.io] has quit [Ping timeout: 252 seconds] 01:41 < waxwing> hmm, ok i'll merge that today and do a release (as per previous conversation, not specifically for that) 01:41 < waxwing> i see 290 in the hackint pit, are we sure it's not working? 01:42 -!- kanzure [~kanzure@user/kanzure] has quit [Ping timeout: 252 seconds] 01:42 -!- greypw2 [~greypw2@grey.pw] has quit [Ping timeout: 252 seconds] 01:42 -!- greypw2 [~greypw2@grey.pw] has joined #joinmarket 01:43 < openoms[m]> I see only 51 combined: http://526xpibebns6mehmmfqj5kpzl4shg4wa7sdwbnpsjqenfidbnn4m3lyd.onion/ 01:43 -!- kanzure [~kanzure@user/kanzure] has joined #joinmarket 01:43 < openoms[m]> also multiple people reported low numbers like 10-20 couple of hours ago 01:44 < openoms[m]> https://nixbitcoin.org/obwatcher/ has 158 01:46 < waxwing> interesting. let me try, i haven't been in there for a while. 01:46 < bitipy> Is there a way to add multiple payments to the sendpayment option in one transaction? I thought it be sendtomany but that apparently is only for internal transactions. 01:48 < belcher> joinmarket's coinjoin inherently only have one output address (and often one change address) 01:49 < belcher> it could be possible for non-coinjoin sends from sendpayment, but i dont think they're implemented 01:50 < bitipy> @belcher: isn't it even more confusing if there are more output addresses? 01:50 < belcher> depends how you design it 01:50 < waxwing> i'm getting 130 orders / 123 counterparties with default 01:50 < waxwing> so looks like about half of typical figures i think openoms[m] 01:51 < belcher> if all the makers have coinjoin outputs with value 10btc, but you as a taker create two coinjoin outputs with value (7btc, 3btc) then you havent added confusion in fact you've cleared up confusion because its obvious which outputs belong to the taker 01:52 < waxwing> it's definitely possible to complexify the design further but the "basic" structure is a single matching output amount. 01:52 < waxwing> re "complexify" see e.g. https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/994 or also ideas like, multiple cj-outs of equal amounts 01:52 < belcher> so any batched coinjoin scheme has to be designed very carefully, and IMO its not really worth doing... what probably is worth doing is adding a feature for tumbler where tumbler pays to multiple addresses in amounts that the user chooses (right now tumbler already pays to multiple addresses but with random amounts) 01:52 < waxwing> i don't honestly like stuff that ends up with more and more outputs, it just gets expensive 01:53 < waxwing> wasabi's v2 is going to be very interesting in this regard 01:53 < belcher> has that been released yet? 01:53 < bitipy> I thought it be less expensive since otherwise you need to make 2 joins instead of 1 with 2 targeted outputs? 01:54 < waxwing> no i think it'll be a while before relase belcher but not sure 01:54 < belcher> bitipy but the privacy might be less 01:55 < waxwing> openoms[m], looks vaguely like the pit is functioning but .. yeah not sure. it would be nice if someone did a detailed investigation. i have no time to do that as well as all the other things. 01:59 < openoms[m]> waxwing in any case it will be good to have two IRC servers active by default so there is fallback 02:00 < belcher> the irc code tolerates networks that don't work, right? so theres no downside to adding more networks just in case they later start working 02:03 < waxwing> openoms[m], do you mean 3? 02:03 < waxwing> belcher, yeah it tolerates specifically in the sense of giving up after 60s and going ahead with wherever it's connected 02:04 < belcher> would there be any downside to having 5 or 10 irc networks configured by default? 02:04 < waxwing> i'm not actually sure. i don't remember testing with more than 3. 02:04 < belcher> eventually the internet bandwidth used becomes very large, but the bandwidth used by a full node is large already 02:05 < waxwing> yeah in theory there are no limits in the way it's coded, just being cautious like it might trip on something we never thought of 02:08 < openoms[m]> waxwing it is just hackint and the old and new address of agora for now 02:08 < waxwing> ok now i'm even more confused :) 02:09 < waxwing> our existing config has 2 active: darkscience, hackint and one commented out: agora 02:09 < waxwing> so we have 2 by default now, so i don't get why you said "in any case it will be good to have two IRC servers active by default so there is fallback" 02:10 < waxwing> why do you write then 'it is just hackint and old and new .. agora'. what is "it" here? 02:10 < openoms[m]> ok, sorry waxwing I missed the darkscience one 02:10 < openoms[m]> so yes, there was 2 and #1026 is adding a third 02:11 < waxwing> ok, got it 02:11 -!- berndj-blackout [~berndj@ns2.linksynergy.co.za] has joined #joinmarket 02:12 -!- kanzure_ [~kanzure@user/kanzure] has joined #joinmarket 02:14 -!- kanzure [~kanzure@user/kanzure] has quit [Ping timeout: 252 seconds] 02:14 -!- berndj [~berndj@ns1.linksynergy.co.za] has quit [Ping timeout: 252 seconds] 02:15 -!- berndj-blackout is now known as berndj 02:45 -!- Zenton [~user@user/zenton] has quit [Ping timeout: 264 seconds] 02:52 -!- Zenton [~user@user/zenton] has joined #joinmarket 03:38 < waxwing> release build in process 03:48 -!- BUSY [~BUSY@user/busy] has quit [Ping timeout: 252 seconds] 03:49 -!- BUSY [~BUSY@user/busy] has joined #joinmarket 04:23 < waxwing> Please review as soon as you get a chance, I intend to push it out today if possible: https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/1029 04:25 < waxwing> kristapsk openoms[m] belcher undeath ++ (just pinging in case) 04:25 < openoms[m]> thanks, reading! and posted to Telegram too 04:34 < belcher> will do 04:40 < belcher> i think theres never a reason to remove an irc network anymore, there used to be a bug where if a single irc network was down then joinmarket wouldnt start up properly but thats fixed now 04:41 < belcher> the upside to having an extra irc network is it might work one day and provides extra redundancy, the downside to having an extra irc network is a tiny bit of extra internet bandwidth used 05:12 < bitipy> stuck on: [INFO] Starting transaction monitor in walletservice 05:13 < bitipy> how to figure out what it is waiting for? 05:14 < waxwing> bitipy, it might be a RPC connection that isn't working 05:14 < waxwing> or it might be a failure to connect to an IRC 05:17 < bitipy> IRC down then? 05:31 < waxwing> try connecting in an IRC client. but also can you run wallet-tool and it works? bitipy 05:32 < waxwing> if you can then it has to be your IRC config i *think* 06:42 -!- tralfaz is now known as davterra 13:03 -!- kanzure_ is now known as kanzure 16:21 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 252 seconds] 16:33 -!- belcher [~belcher@user/belcher] has joined #joinmarket 19:19 -!- technonerd [~techno@user/technonerd] has quit [Ping timeout: 276 seconds] 19:20 -!- technonerd [~techno@user/technonerd] has joined #joinmarket 20:00 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has quit [Remote host closed the connection] 20:00 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has joined #joinmarket 21:58 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has quit [Quit: No Ping reply in 180 seconds.] 21:59 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has joined #joinmarket --- Log closed Sat Oct 02 00:00:24 2021