--- Day changed Thu Oct 24 2019 00:44 -!- achow101 [~achow101@unaffiliated/achow101] has joined #joinmarket 00:57 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 276 seconds] 01:01 -!- achow101 [~achow101@unaffiliated/achow101] has joined #joinmarket 01:04 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 01:04 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket 02:43 -!- Giszmo [~leo@122-58-98-6-adsl.sparkbb.co.nz] has joined #joinmarket 05:16 -!- MaxSan [~four@195.206.105.227] has quit [Ping timeout: 268 seconds] 05:31 < zfk> holy cow... jm tumbled 4.89% of depth 0, followed by 6.88% of depth 0, then it took the remainder of depth 0 and tumbled it into a final address. it feels like jm hardly did anything; not to mention all those utxos in depth 0 were just combined.... but i dunno, i'm not math wizard, maybe that is enough to introduce privacy. 07:04 < belcher> zfk did you modify the default tumbler parameters? 07:04 < belcher> what you describe is odd for sure, it doesnt work that way (by default) 07:05 < belcher> especially the part about going straight from depth 0 to to a final destination address 11:49 -!- AgoraRelay [~jmrelayfn@p5DE4A42A.dip0.t-ipconnect.de] has joined #joinmarket 11:50 -!- CgRelayBot [~CgRelayBo@p5DE4A42A.dip0.t-ipconnect.de] has joined #joinmarket 11:57 -!- reallll [~belcher@unaffiliated/belcher] has joined #joinmarket 12:01 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 268 seconds] 12:10 -!- reallll is now known as belcher 13:35 -!- CgRelayBot_ [~CgRelayBo@p5DE4ADEC.dip0.t-ipconnect.de] has joined #joinmarket 13:35 -!- AgoraRelay_ [~jmrelayfn@p5DE4ADEC.dip0.t-ipconnect.de] has joined #joinmarket 13:35 -!- CgRelayBot [~CgRelayBo@p5DE4A42A.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 13:36 -!- AgoraRelay [~jmrelayfn@p5DE4A42A.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds] 14:26 -!- MaxSan [~four@195.206.105.227] has joined #joinmarket 15:09 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 250 seconds] 15:09 -!- CgRelayBot_ [~CgRelayBo@p5DE4ADEC.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 15:09 -!- AgoraRelay_ [~jmrelayfn@p5DE4ADEC.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 15:10 -!- CgRelayBot [~CgRelayBo@p5DE4AD54.dip0.t-ipconnect.de] has joined #joinmarket 15:11 -!- AgoraRelay [~jmrelayfn@p5DE4AD54.dip0.t-ipconnect.de] has joined #joinmarket 15:27 -!- nsh [~lol@wikipedia/nsh] has quit [Quit: ZNC - http://znc.in] 15:42 -!- nsh [~lol@wikipedia/nsh] has joined #joinmarket 15:43 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 15:44 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket 16:48 < zfk> im 90% sure I didnt and 100% sure I didntmodify an ything that was recommended to NOT modify 17:07 < zfk> :o the website got updated! 17:09 -!- AgoraRelay_ [~jmrelayfn@p5DE4A553.dip0.t-ipconnect.de] has joined #joinmarket 17:09 < waxwing> zfk, something's wrong there i think ... the schedule of transactions the tumbler did should still be in TUMBLE.schedule in logs/ ; how many transactions were there? how many final destinations? i think by default it mixes through 4 and should have done like around 10 transactions, although it's not deterministic 17:11 -!- CgRelayBot_ [~CgRelayBo@p5DE4A553.dip0.t-ipconnect.de] has joined #joinmarket 17:11 -!- CgRelayBot [~CgRelayBo@p5DE4AD54.dip0.t-ipconnect.de] has quit [Ping timeout: 245 seconds] 17:12 -!- AgoraRelay [~jmrelayfn@p5DE4AD54.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 17:17 < zfk> this is what tumbler.py came up with https://pastebin.com/EAqUTweq 17:17 < zfk> the only args I used were -a 4 and -C so everything, I assume, was default settings 17:19 < zfk> of course maybe thats why it failed, idk 19:38 < zfk> what am I doing wrong? https://pastebin.com/2B4yV5gu 19:41 < zfk> or is that normal? i thought jm wasnt supposed to tumble anything from depth0-->finalDestinationAddr 19:49 -!- hihih [4a8052a7@cpe-74-128-82-167.kya.res.rr.com] has joined #joinmarket 20:01 -!- hihih [4a8052a7@cpe-74-128-82-167.kya.res.rr.com] has quit [Remote host closed the connection] 23:24 < belcher> zfk abb 23:27 < belcher> ah yes, the explanation is there 23:29 < belcher> its configured to use 6 destination addresses, but only one destination address can be sent from each mixdepth.. overall there are 4 mixdepths used in that schedule with one destination address per mixdepth.. so 4 destination addresses used per mixdepth including mixdepth 0 (if you notice addr5 and addr6 were never used) 23:29 < belcher> you actually set -c 6 1 (or --txcountparam 6 1) so the number of mixdepths _should_ be close to 6 but for some reason they arent, that could be a bug 23:31 < belcher> ah hold on i get it, -c --txcountparam is about the number of transactions per mixdepth, what is required is to increased the number of mixdepths used which is -M or --mixdepthcount 23:32 < belcher> i see why this happened probably, the help string for --txcountparam says "The number of transactions to take coins from one mixing depth to the next, it is randomly chosen following a normal distribution. Should be similar to --addrask. " which is wrong, that help string should be in --mixdepthcount instead 23:34 < belcher> so its a bug with documentation, ill fix that in a sec... also maybe we could add a few lines in get_tumbler_schedule() which make sure that mixdepths with coins already in them dont send them straight to a destination