--- Day changed Tue Jul 02 2019
02:11 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]     
02:11 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket     
02:42 < adlai> fishscallop: a "tumble" is multiple txs, and their sizes range to small enough that miner fees become significant
02:44 < adlai> bitcoin itself is not exactly at fault for this: the daily and weekly fluctuations of miser fees are unlikely to cause such a sharp tumbling fee
02:45 < adlai> the tumbling fees are best treated as fundamentally nondeterministic, and if you want determinism, be a good physicist and observe your apparatus at work rather than delegating observation to a machine
02:46 < adlai> people have lost much more than miner fees in earlier versions of joinmarket due to treating the scripts as magic incantations.
02:54 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]     
04:46 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Remote host closed the connection]     
06:07 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]     
06:08 < waxwing> well that's certainly ... interesting: https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/361#issue-463217390
06:10 < waxwing> maybe people who are more expert on Bitcoin Core (there are plenty here!) have a comment.
06:13 < waxwing> i guess when you're running bitcoind as a service it might be slightly different. i don't.
06:28 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket     
11:12 -!- lnostdal [~lnostdal@77.70.119.51] has joined #joinmarket     
11:52 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket     
11:54 < kristapsk> waxwing, are the sources of the script you used to analyze blockchain for jm tx'es public somewhere?
12:10 < waxwing> belcher, https://gist.github.com/AdamISZ/639333568ad98f50354c933057ee32a4
12:10 < waxwing> oops sorry didn't mean to ping belcher_ just a copy paste :)
12:11 < waxwing> very rough, certainly possible to make a much better one .. or use something more serious that isn't stupidly slow.
12:14 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]     
12:14 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket     
12:15 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Remote host closed the connection]     
12:16 -!- StopAndDecrypt [~StopAndDe@107.181.189.46] has joined #joinmarket     
12:16 -!- StopAndDecrypt [~StopAndDe@107.181.189.46] has quit [Changing host]     
12:16 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #joinmarket     
12:18 < kristapsk> "at least 3 coinjoin outs (2 technically possible but excluded)" - actually I have seen rarely some 2 party coinjoins by other parties involving my yg
12:18 < kristapsk> not very often, but still
12:18 < waxwing> yeah
12:19 < waxwing> also it picked up one wasabi join i think .. but only one. i wrote it before wasabi and didn't filter on address type, which is a bit duh. i'm not sure why wasabi wouldn't be picked up more often, although i'm sure there's a reason.
12:20 < waxwing> i'll pastebin the output, hang on.
12:21 < kristapsk> yes, for JM, currently all inputs should be either p2pkh or p2sh, that will filter out wasabi ones
12:22 < waxwing> https://pastebin.com/vpiy6t6w
12:22 < kristapsk> also, only one output can be of different address type (or two if assume patientsendpayment from legacy jm (?) )
12:23 < waxwing> yes just filtering on address type of equal sized outputs should be good enough, except for weird false positives ofc
12:23 < waxwing> or rather as you say at least n-1 of them
12:25 < waxwing> you generally find there are edge cases to any rule but .. well anyway as you can see there was one wasabi with 144 outputs. so i guess 72 party.
12:27 < kristapsk> I think nopara had something in C# for analyzing blockchain for any kind of Cjs, maybe it worked faster and could be modified to search only for likely JM tx'es, will try to find it, have dotnet core on my machine anyway
12:28 < kristapsk> would be interesting to analyze longer periods, as workdays / weekends and even more mempool (state) impacts number of coinjoins people do, at least from what I have observed
12:29 < kristapsk> I mean, mempool state (fees)
12:30 < kristapsk> but I guess it will be full on LINQ, in which I'm really not an expert :D
13:12 -!- AbuseOfNotation [~AbuseOfNo@217.151.98.168] has quit [Ping timeout: 258 seconds]     
15:03 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 260 seconds]     
15:08 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #joinmarket     
15:31 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 268 seconds]     
16:01 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.5]     
17:14 -!- AgoraRelay [~jmrelayfn@p5DE4ACE9.dip0.t-ipconnect.de] has quit [Ping timeout: 248 seconds]     
17:23 -!- AgoraRelay [~jmrelayfn@p5DE4ABAA.dip0.t-ipconnect.de] has joined #joinmarket     
18:45 -!- viasil [~viasil@95.174.67.204] has joined #joinmarket     
19:45 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]     
20:08 -!- AbuseOfNotation [~AbuseOfNo@217.151.98.168] has joined #joinmarket     
21:47 -!- viasil [~viasil@95.174.67.204] has quit [Ping timeout: 244 seconds]     
23:26 -!- adlai [~adlai@unaffiliated/adlai] has quit [Read error: Connection reset by peer]     
23:27 -!- adlai [~adlai@unaffiliated/adlai] has joined #joinmarket