--- Log opened Thu Dec 03 00:00:34 2020
00:17 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Remote host closed the connection]
00:21 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer]
01:32 -!- ricks_ [~ricks_@gateway/tor-sasl/ricks/x-19497574] has joined #joinmarket
01:56 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 256 seconds]
01:57 -!- jonatack [~jon@134.19.179.187] has joined #joinmarket
02:34 -!- ricks_ [~ricks_@gateway/tor-sasl/ricks/x-19497574] has quit [Quit: ricks_]
02:46 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has joined #joinmarket
03:17 -!- Katharina75Barto [~Katharina@static.57.1.216.95.clients.your-server.de] has quit [Remote host closed the connection]
03:20 -!- Lois17Konopelski [~Lois17Kon@static.57.1.216.95.clients.your-server.de] has joined #joinmarket
04:11 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket
05:04 -!- reallll is now known as belcher
05:21 -!- kisbitcoin [2578d7e6@37.120.215.230] has joined #joinmarket
05:28 < kisbitcoin> Can I download and modify https://raw.githubusercontent.com/JoinMarket-Org/joinmarket-clientserver/master/scripts/sample-schedule-for-testnet, pass it through into tumbler.py ? I tried manually inputting the parameters as a list but I can't get it to work
05:31 -!- Lois17Konopelski [~Lois17Kon@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 240 seconds]
05:55 -!- reallll [~belcher@unaffiliated/belcher] has joined #joinmarket
05:55 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds]
06:03 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket
06:10 -!- reallll [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds]
06:11 -!- reallll [~belcher@unaffiliated/belcher] has joined #joinmarket
06:59 < waxwing> kisbitcoin, use the -S flag to `sendpayment.py`
07:00 < kisbitcoin> Isn't that made to use with tumble.py ?
07:01 < waxwing> no; ultimately we shouldn't really have two separate scripts, because the 'schedule' concept means that 1 coinjoin or several come under the same umbrella; but the refactoring to merge them into one script hasn't been done.
07:01 < waxwing> essentially, a Taker always runs a schedule, whether of one join or several
07:01 < kisbitcoin> I was intending not to show QT in the guide, but I was told QT was ideal to use for multiple coinjoins.
07:01 < kisbitcoin> * as a taker*
07:01 < waxwing> if you run sendpayment with command line arguments, and no schedule, then it builds internally a schedule of one entry.
07:02 < waxwing> I mean, Qt has various advantages, enough that i myself quite often use it. but there are some things in the command line version that don't exist in the Qt.
07:03 < waxwing> custom schedules actually isn't one though, thinking about it, although this is perhaps not tested or used by anyone, you're allowed to load any schedule file into the multijoin tab
07:03 < waxwing> by default the multi join tab will load a file logs/TUMBLE.schedule if restarted (or more usually, it will create that file)
07:03 < waxwing> but if you build a schedule file in the same format and call it myschedule.txt or anything, you can load it.
07:05 < kisbitcoin> I attempted to use multijoin and went through the GUI , setup schedule parameters and ran it, but I ended up going back to CLI to view the progress, QT wasn't clearly showing me what was transpiring- especially after having gone through sendpayment.py
07:06 < waxwing> did you not see basically the same output in the log pane at the bottom of the tab?
07:07 < waxwing> not that i think it's especially informative to the user, but it should be basically the same i think. perhaps it's different in the log level, i don't recall (maybe it shows DEBUG and not only INFO by default)
07:08 < kisbitcoin> Yes I did, however asthetically its better for the guide on CLI. Especially since I've already shown how to use sendpayment.py with multiple flags.
07:08 < waxwing> oh i think i get what you mean, you found it was easier to just read what was being output on the terminal
07:08 < kisbitcoin> Exactly.
07:08 < waxwing> ok yeah. i mean user feedback in the Qt app is pretty basic and by no means good enough, for what is a pretty complex app
07:09 < waxwing> it is what it is until it gets improved. it's already improved a great deal from what it was 2 years ago.
07:09 < kisbitcoin> I tried to use tumble.py and pass the parameters outlines in the schedule file on github
07:10 < kisbitcoin> I guess I'll show it scheduled on QT and showcase the progress from the CLI.
07:11 < kisbitcoin> I would have liked to skip QT altogether so user can get more comfortable on CLI since thats where most of the meat is. O well.
07:12 < kisbitcoin> I could generate tumble schedule with QT, save that and return to CLI and run the schedule with tumble.py ?
07:12 < waxwing> i think my personal experience is the main advantage of Qt is dealing with the wallet and coins. it keeps the wallet real time updated, and it shows you individual utxos that you can control ... also, if you want to do e.g. payjoin it's nice that you paste in the URI. there's also QR codes for deposit.
07:13 < waxwing> for actions like tumble, shrug, i used both tons of times in testing and i used both on mainnet too. to me it's nbd which you use.
07:13 < waxwing> for maker function in Qt, we have a PR open that basically works, but there are some open questions about it.
07:13 < waxwing> kisbitcoin, yes you could do that.
07:15 < kisbitcoin> I'll play with that. I might show it that way.
07:21 < kisbitcoin> https://paste.pics/0b662eaa2e370471b51e52aae6031a0f
07:21 < kisbitcoin> What is average # of txns per mixdepth mean ?
07:21 < kisbitcoin> In the QT's schedule generator.
07:25 < technonerd> sweeps are just for internal addresses right?
07:29 < kisbitcoin> technonerd you can sweep with sendpayment.py to any address by putting '0' as amount.
07:30 < kisbitcoin> Is there a way to use 'INTERNAL'  as a flag with sendpayment.py or tumble.py ?
07:30 < technonerd> i have coins in external and internal, trying to migrate to native wallet
07:33 -!- reallll is now known as belcher
08:06 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds]
08:07 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket
09:47 -!- deafboy [quasselcor@cicolina.org] has quit [Quit: deafboy]
09:47 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket
09:49 -!- deafboy [quasselcor@cicolina.org] has quit [Client Quit]
09:49 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket
09:50 -!- kisbitcoin [2578d7e6@37.120.215.230] has quit [Ping timeout: 245 seconds]
09:53 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
09:58 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket
10:20 -!- zndtoshi [~zndtoshi@79.112.20.148] has joined #joinmarket
10:22 < zndtoshi> throwing an idea out there: what if a coinjoin transaction would create equal outputs, but with the change from every user try to create equal change outputs too to further mix the heuristics
10:25 < zndtoshi> or during a sendpayment.py create only equal change for all participants while sending the intended amount without getting it mirrored from any other maker (it would look thus like the change)
10:30 -!- belcher_ [~user@unaffiliated/belcher] has quit [Ping timeout: 260 seconds]
10:33 -!- belcher_ [~user@unaffiliated/belcher] has joined #joinmarket
10:35 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
11:22 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Ping timeout: 264 seconds]
11:46 -!- boblee53 [18967140@d24-150-113-64.home.cgocable.net] has joined #joinmarket
11:47 -!- boblee53 [18967140@d24-150-113-64.home.cgocable.net] has quit [Remote host closed the connection]
12:19 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket
12:27 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 3.0]
12:29 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has quit [Remote host closed the connection]
12:30 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has joined #joinmarket
12:35 -!- davterra [~davterra@static-198-54-131-92.cust.tzulo.com] has joined #joinmarket
12:38 -!- tralfaz [~davterra@static-198-54-131-92.cust.tzulo.com] has quit [Ping timeout: 256 seconds]
14:52 -!- zndtoshi [~zndtoshi@79.112.20.148] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
16:15 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer]
16:26 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has quit [Quit: Leaving]
17:15 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
17:44 -!- HackRelay [~jmrelayha@p5de4a11a.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
17:44 -!- DSRelBot [~DSRelBot@p5de4a11a.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
17:57 -!- DSRelBot [~DSRelBot@p5de4a66e.dip0.t-ipconnect.de] has joined #joinmarket
17:58 -!- HackRelay [~jmrelayha@p5de4a66e.dip0.t-ipconnect.de] has joined #joinmarket
19:04 -!- DSRelBot [~DSRelBot@p5de4a66e.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
19:05 -!- HackRelay [~jmrelayha@p5de4a66e.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
19:15 -!- DSRelBot [~DSRelBot@p548666f8.dip0.t-ipconnect.de] has joined #joinmarket
19:20 -!- HackRelay [~jmrelayha@p548666f8.dip0.t-ipconnect.de] has joined #joinmarket
19:44 -!- viasil [~nobody@95.174.67.172] has quit [Ping timeout: 260 seconds]
19:44 -!- viasil [~nobody@95.174.67.172] has joined #joinmarket
20:33 -!- viasil [~nobody@95.174.67.172] has quit [Ping timeout: 256 seconds]
20:48 -!- viasil_ [~nobody@95.174.67.172] has joined #joinmarket
23:39 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Ping timeout: 264 seconds]
--- Log closed Fri Dec 04 00:00:36 2020