--- Day changed Mon Nov 04 2019 00:44 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 245 seconds] 00:48 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket 01:11 -!- Giszmo [~leo@122-58-98-6-adsl.sparkbb.co.nz] has joined #joinmarket 01:12 -!- Giszmo [~leo@122-58-98-6-adsl.sparkbb.co.nz] has quit [Client Quit] 02:04 < waxwing> takinbo, belcher i don't think it's worth bothering about makers being slow, that's too complicated. re: the regtest timeout thing, i haven't read or thought about what you said yet, will get on it soon. 03:19 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket 04:02 -!- M1 [~Michail@michail.com] has quit [Ping timeout: 240 seconds] 04:06 -!- M1 [~Michail@michail.com] has joined #joinmarket 04:47 -!- openoms [~quassel@cpc115066-stok20-2-0-cust313.1-4.cable.virginm.net] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.] 04:50 -!- justbrowsingthro [5db1bc4a@93.177.188.74] has joined #joinmarket 04:51 < waxwing> belcher, i can't remember what i was thinking in setting maker_timeout_sec in the code dynamically; it was a long time ago and perhaps i just forgot .. but right now i see absolutely no reason not to just have it in regtest_joinmarket.cfg instead. 04:52 < waxwing> oh hang on need to check that works fine with Travis though 04:54 < waxwing> yeah that's fine travis uses regtest_joinmarket.cfg ofc so i'll push a PR with that, it shouldn't cause merge conflicts 05:26 < waxwing> belcher, i guess you can remove branch `undo-commit-**` (just noticing as i tidy up my old ones) 05:29 < waxwing> and for a final ping belcher :) i'm at a loss to understand how the new mixdepth accounting in the PR works, i'm going to need to go through it with you to get it. 05:33 < waxwing> it suddenly occurs to me (duh) that tumbler could use a wraparound approach to mixdepths; since it sweeps M before processing M+1, then when you get to the highest by default(mixdepth 4), you could have the destination be mixdepth 0 and it makes no difference to tumbler, and it would make it much easier to manage the wallet. 05:33 < waxwing> counterargument: if someone starts tumble from mixdepth 1 but 0 isn't empty. seems a bit artificial. well, feel free to ignore for now :) 05:41 -!- justbrowsingthro [5db1bc4a@93.177.188.74] has quit [Remote host closed the connection] 05:52 -!- MaxSan [~four@195.206.105.227] has quit [Quit: Leaving.] 05:54 < belcher> removed the undo-commit- branch 06:11 < waxwing> belcher, ok; just dropped a comment, there's a crash in #387, but easy to see how it came about 06:12 < waxwing> oh dammit i also caused a conflict in cli_options.py, sorry about that, i felt sure it wouldn't be a clash so just pushed it earlier today. it'll be very minor of course. 06:12 < belcher> thats ok conflicts are fixable 06:13 < belcher> do you have any advice for how to fix this crash 06:13 < belcher> the crash happens because it always imports sweep destination addresses, but since it sweeps to internal then that address is already imported so it crashes 06:13 < belcher> perhaps a check to wallet_service.is_address_mine() or whatever the method is called 06:14 < waxwing> yeah, i was also just thinking, just drop the import if it is INTERNAL 06:14 < waxwing> ' .. and self.my_cj_addr != 'INTERNAL' ' 06:15 -!- openoms [~quassel@cpc115066-stok20-2-0-cust313.1-4.cable.virginm.net] has joined #joinmarket 06:15 < waxwing> i mean you could argue that's a bit crappy but we're in the 'business logic' part of the code so i think it's allowed to be a bit arbitrary 06:15 < belcher> oh yes i see, self.my_cj_addr is taken directly from the schedule 06:15 < belcher> ok ill do that, sece 06:17 -!- openoms_ [~quassel@cpc115066-stok20-2-0-cust313.1-4.cable.virginm.net] has joined #joinmarket 06:18 < belcher> - if self.cjamount == 0: 06:18 < belcher> + if self.cjamount == 0 and self.my_cj_addr != "INTERNAL": 06:18 < belcher> thats the diff 06:18 < waxwing> yeah i'm setting up the test again now :) 06:18 < waxwing> but i really don't understand the mixdepth counting in the non-sweep part 06:19 < belcher> do you mean this code? https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/387/commits/27616a017156797c79e3a0bc87af94411eecdf66 06:19 < waxwing> this line: https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/387/files#diff-8ab678031c38c4411de493992a1ed85bR162 06:20 -!- openoms [~quassel@cpc115066-stok20-2-0-cust313.1-4.cable.virginm.net] has quit [Ping timeout: 252 seconds] 06:21 < waxwing> i mean i'm gonna test it but here's my reasoning: suppose i start off with coins in m0 and m2. i set srcmixdepth to 0. Stage 1 will move coins from m0 to m1 and from m2 to m3 (right?). Then when it starts out, the first iteration with m=0 in the loop over txcounts (for Stage 2), you'll have 1+0+0+1 so it'll start at mixdepth 2, but that's empty? 06:21 < belcher> lowest_initial_empty_mixdepth is the lowest empty mixdepth, the +1 is there because stage1 sweeps coins from one mixdepth to the next one 06:21 < waxwing> i'm no doubt entirely wrong but i couldn't get it. hence want to try it. 06:22 < belcher> in your example lowest_initial_empty_mixdepth will be 1, not zero 06:22 < belcher> wait a sec 06:22 < waxwing> right, that's as i recall what i got. the first '1' in 1+0+0+1 06:23 < belcher> hold on i dont know 06:23 < belcher> but i did test it 06:24 < belcher> i think you're right, ill try testing again.. this is weird 06:24 < waxwing> right. for me the worst part of tumbler is accounting for irregular mixdepth usage. even handling aberrant makers is a somewhat solved problem (we have malicious makers in ygrunner so you can at least see the tweaking in action). 06:24 < waxwing> but with all kinds of weird mixdepth counts and distributions it's a pain. 06:27 < belcher> i tested it again and it works 06:27 < belcher> ill debug more to figure out whats happening 06:28 < belcher> whats happening is lowest_initial_empty_mixdepth is zero for some reason 06:28 < belcher> oooh, because it gets initalized at zero 06:28 < belcher> so the min() means it always stays at zero 06:29 < waxwing> belcher, another one: this commit is not in the PR: https://github.com/JoinMarket-Org/joinmarket-clientserver/commit/b3c54ca4ae75c46bbfd5b87d5ab5318354bc90ca 06:29 < waxwing> right re: initialized LIEM. 06:29 < belcher> to make that commit in the PR i need to rebase, which ill do 06:30 < waxwing> i should probably leave this for now and you can let me know when it all makes sense to you and tests out OK (and do try a sanity check with Qt also, it's easy to run in regtest) 06:32 < belcher> ok, will do 06:34 < waxwing> but on the algo, i'm a bit worried about this whole 'sweep to next mixdepth' in Stage 1. can we not sweep to same mixdepth? otherwise there'll be a lot more people extending their mixdepths out to higher numbers. 06:34 < waxwing> maybe i'm being stupid and people do that anyway. 06:34 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.6] 06:34 < waxwing> i guess that's the whole INTERNAL issue you were asking about when you started coding it. 06:36 < belcher> sweeping to the same mixdepth requires adding more code, the status quo is simpler 06:38 -!- bsm1175321 [~mcelrath@71.181.119.146] has joined #joinmarket 06:51 -!- MaxSan [~four@195.206.105.227] has joined #joinmarket 07:36 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 276 seconds] 08:05 -!- M1 [~Michail@michail.com] has quit [Quit: ZNC - http://znc.in] 08:10 -!- M1 [~Michail@michail.com] has joined #joinmarket 08:16 -!- MaxSan [~four@195.206.105.227] has quit [Quit: Leaving.] 08:38 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket 09:02 -!- MaxSan [~four@195.206.105.227] has joined #joinmarket 09:10 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined #joinmarket 09:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 09:11 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket 09:19 -!- sosthene [~sosthene@88.191.20.124] has joined #joinmarket 09:51 -!- zndtoshi [4f705014@79.112.80.20] has joined #joinmarket 09:54 < zndtoshi> I want to connect JM to mynodebtc, a RPi4 full node. I've opened the port on the firewall on rpi4, inserted the local ip in joinmarket.cfg and also rpcuser and rpcpass. Still I get "[ERROR] Unhandled connection error [Errno 111] Connection refused". Any suggestions? 09:54 < zndtoshi> also added rpcbind=0.0.0.0rpcallowip=0.0.0.0/0to the bitcoin.conf 10:13 < undeath> either the ip in your joinmarket.cfg is wrong or you have a firewall on your rpi blocking the incoming connections 10:14 < undeath> or the port in your joinmarket.cfg is wrong 10:14 < zndtoshi> checked both :( 10:14 < zndtoshi> its 192.186.0.101 and port 8332 10:14 < undeath> which matches the ip/port on your rpi? 10:14 < zndtoshi> yes 10:15 < zndtoshi> had to add the port in the firewall settings 10:15 < zndtoshi> and the lan ip is correct 10:15 < undeath> check the output of "ss -tplen" on your rpi 10:21 < zndtoshi> State Recv-Q Send-Q Local Address:Port Peer Address:Port LISTEN 0 128 127.0.0.1:6379 0.0.0.0:* uid:109 ino:26162 sk:1 <-> LISTEN 0 100 127.0.0.1:28332 0.0.0.0:* uid:1002 ino:22857 sk:2 <-> LISTEN 0 128 10:21 < zndtoshi> 127.0.0.1:8332 0.0.0.0:* uid:1002 ino:22852 sk:3 <-> LISTEN 0 128 127.0.0.1:8333 0.0.0.0:* uid:1002 ino:28378 sk:4 <-> LISTEN 0 100 127.0.0.1:28333 0.0.0.0:* uid:1002 ino:22859 sk:5 <-> LISTEN 0 128 0.0.0.0:80 10:21 < zndtoshi> 0.0.0.0:* ino:18677 sk:6 <-> LISTEN 0 128 0.0.0.0:22 0.0.0.0:* ino:15822 sk:7 <-> LISTEN 0 128 127.0.0.1:9050 0.0.0.0:* ino:18438 sk:8 <-> LISTEN 0 128 127.0.0.1:9051 0.0.0.0:* ino:18439 10:21 < zndtoshi> sk:9 <-> LISTEN 0 100 0.0.0.0:443 0.0.0.0:* ino:15308 sk:a <-> LISTEN 0 128 [::]:22 [::]:* ino:15824 sk:b v6only:1 <-> 10:21 < undeath> that shows your bitcoind is listening on 127.0.0.1 only 10:22 < zndtoshi> so should I change rpcbind=0.0.0.0rpcallowip=0.0.0.0/0 10:22 < zndtoshi> to default? 10:22 < undeath> no, but apparently those settings are not used by bitcoind 10:23 < undeath> meaning it's in the wrong config file or you didn't restart bitcoind 10:23 < zndtoshi> checking 10:26 < zndtoshi> this is how the config looks like. the mynode dev added the custom configs at the end of the file 10:26 < zndtoshi> https://postimg.cc/bs6Y7L7b 10:26 < zndtoshi> the rpcpassword is in another file but I tripple checked it's the right one 10:28 < undeath> at the middle of the config you have rpcbind=127.0.0.1 10:28 < zndtoshi> shouldn't the last 2 lines overwrite that? 10:29 < undeath> well, apparently not 10:29 -!- M1 [~Michail@michail.com] has quit [Quit: ZNC - http://znc.in] 10:29 < zndtoshi> trying to manually modify 10:36 < zndtoshi> seems it reverts to default after I reboot the mynode 10:36 < zndtoshi> will check with the lead dev 10:36 < zndtoshi> thank you 10:36 < undeath> yw :) 10:38 < zndtoshi> undeath you are so awesome 10:38 < zndtoshi> tried again to manually change the file 10:38 < zndtoshi> and do 10:38 < zndtoshi> sudo systemctl restart bitcoind 10:38 < zndtoshi> and now it worked 10:38 < zndtoshi> lol 10:38 < undeath> :) 10:38 < undeath> just hope you don't have to do that on every reboot 10:39 < zndtoshi> no worries.. I know what to tell dev to fix 10:58 -!- reallll [~belcher@unaffiliated/belcher] has joined #joinmarket 11:01 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds] 11:10 -!- M1 [~Michail@michail.com] has joined #joinmarket 11:15 -!- reallll is now known as belcher 12:07 -!- zndtoshi [4f705014@79.112.80.20] has quit [Ping timeout: 260 seconds] 12:22 -!- zndtoshi [b9d2dadc@185.210.218.220] has joined #joinmarket 12:23 < zndtoshi> Can someone please explain: Is single join a type of market taker (uses available liquidity to obfuscate links) and multiple join a type of market maker (provides liquidity)? Am I getting this right? 12:26 < undeath> no 12:27 < undeath> a single coinjoin does not provide much anonymity 12:27 < undeath> if you want anonymity you need to use the tumbler multi-coinjoin script 12:28 < undeath> if you want to be a maker you should run a yieldgenerator 12:29 < zndtoshi> Is that possible with the Qt? 12:29 < undeath> no 12:29 < zndtoshi> I think I should finish reading the wiki before asking :) 12:38 < zndtoshi> so running a yieldgenerator looks straight forward.. deposit coins and run. Right? 12:39 < undeath> yep 12:40 < zndtoshi> just to gauge for the market as I don't know the liquidity.. what's a good deposit amount? Can you give me a range so I can get an idea? 12:41 < undeath> you need to remember that your deposit amount will be spread over all your mixdepths, so in general there will be 1/5th available for a single cj of what you deposit 12:42 < undeath> i don't think running a yg with less than 0.1 is going to see much activity 12:42 < undeath> but other may have more solid numbers 12:42 < undeath> *others 12:43 < zndtoshi> I run on ubuntu.. are there any realistic risks of having coins on hot wallet JM? 12:44 < undeath> well, the coins in your hot wallet are basically as secure as your computer itself 12:45 < undeath> that's an assessment nobody can really help you with 12:45 < zndtoshi> would you kindly explain mixdepths? can't get a grasp 12:46 < undeath> oof, not sure there's a short explanaition for this 12:47 < zndtoshi> is it like higher anonimity set as I go higher in mixdepth? 12:47 < undeath> basically yes 12:47 < undeath> coins in each mixdepth are considered "unlinked" to the other mixdepths 12:48 < undeath> which is not 100% true because there is no information about the "quality" of the coinjoin done to ascend mixdepths 12:48 < zndtoshi> is mixdepth 4 a higher anonimity set than 2 or it's just unlinkable 12:48 < undeath> but it gives a good indication 12:48 < zndtoshi> I understand 12:49 < undeath> yes, you would usually deposit to md 0 and it will go up to 4 (and then wrap back to 0) 12:49 < zndtoshi> If I want to deposit for tumbler.. should I make one deposit or split my utxo to different addresses in mixdepth 0 (even if I don't see a point for this) 12:50 < undeath> the tumbler will handle all the splitting needed 12:50 < undeath> consider all funds in a mixdepth linked to each other 12:51 < zndtoshi> yeah.. imagined it's like that. so no point in splitting. it makes sense to use different wallets in mixdepth 0 only if I deposit from different wallets.. right? 12:52 < undeath> or you deposit to different mixdepth but then you again have the problem that everything in a specific mixdepth may possibly be linked to that deposit 12:53 < zndtoshi> got it. Can I leave the yield run indefinitely? I'd assume at one point there would be a lot of utxo fragmentation. 12:55 < undeath> the yg will handle the fragmentation quite well. you will have fragmentation, but with your merge algorithm set to "greedier" it should never grow excessively 12:56 < zndtoshi> thank you undeath. You've been awesome! Will dive into it! 12:57 < undeath> no problem :) 13:04 -!- zndtoshi [b9d2dadc@185.210.218.220] has quit [Remote host closed the connection] 13:35 -!- bsm1175321 [~mcelrath@71.181.119.146] has quit [Ping timeout: 245 seconds] 14:45 -!- viasil [~viasil@95.174.67.204] has quit [Ping timeout: 276 seconds] 14:50 -!- viasil [~viasil@95.174.67.204] has joined #joinmarket 15:55 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.6] 16:00 -!- ghost43_ is now known as ghost43 16:00 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 246 seconds] 17:40 -!- CgRelayBot [~CgRelayBo@p5DE4A5D1.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds] 17:40 -!- AgoraRelay [~jmrelayfn@p5DE4A5D1.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds] 17:54 -!- AgoraRelay [~jmrelayfn@p5DE4A2E9.dip0.t-ipconnect.de] has joined #joinmarket 17:54 -!- CgRelayBot [~CgRelayBo@p5DE4A2E9.dip0.t-ipconnect.de] has joined #joinmarket 22:10 -!- Giszmo [~leo@122-58-98-6-adsl.sparkbb.co.nz] has joined #joinmarket 22:10 -!- Giszmo [~leo@122-58-98-6-adsl.sparkbb.co.nz] has quit [Client Quit]