--- Day changed Fri Jan 20 2017 00:12 -!- windsok [~windsok@45.63.59.8] has quit [Ping timeout: 276 seconds] 00:31 < weex> getting there: 9 failed, 86 passed in 624.88 seconds 00:50 -!- windsok [~windsok@45.63.59.8] has joined #joinmarket 01:12 -!- buckowski [buckowski@gateway/shell/elitebnc/x-vbqnkjcwgzyzfezc] has quit [Ping timeout: 240 seconds] 01:19 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-jbmcjsbwjeotqazr] has quit [Quit: Connection closed for inactivity] 01:22 -!- buckowski [buckowski@gateway/shell/elitebnc/x-rzcqnqbbuzkndutg] has joined #joinmarket 01:33 -!- Yohkii [~Yohkii@unaffiliated/yohkii] has joined #joinmarket 01:36 -!- Yohkii [~Yohkii@unaffiliated/yohkii] has quit [Client Quit] 01:39 -!- emzy_ is now known as emzy 01:53 < weex> looks like at least one of those failures was because importaddress doesn't accept watchonly in 0.13.2 01:54 < adlai> weex: that's a nuisance. thank you for catching it. 01:55 < adlai> unsupported on 0.13.1 as well 01:55 < adlai> at least, undocumented 01:55 < weex> bitcoin-cli is changing quite a bit, wouldn't have known if i hadn't been checking jm 01:56 < adlai> jm doesn't use bitcoin-cli though, it has its own rpc client implementation. so bitcoin-cli documentation changing might not explain the problem. 01:57 < weex> sorry, yeah i meant the api more generally 01:57 < weex> it's cool though, all seem to be improvements 02:19 < waxwing> 0.13.1 seems to be fine, i was running that for a long while. 02:24 < waxwing> of interest to people here: http://samouraiwallet.com/features/ricochet 02:25 < waxwing> oh lol i thought they were using the ricochet p2p hidden service protocol :) 02:25 < waxwing> no it's just tx hops. 02:52 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-vmqfuecsxpaagymv] has joined #joinmarket 03:01 -!- windsok [~windsok@45.63.59.8] has quit [Ping timeout: 240 seconds] 03:31 -!- windsok [~windsok@45.63.59.8] has joined #joinmarket 05:06 -!- waxwing [waxwing@gateway/vpn/mullvad/x-folodrkoamyhzewx] has quit [Ping timeout: 256 seconds] 05:26 -!- waxwing [~waxwing@193.138.219.236] has joined #joinmarket 05:28 < waxwing> i seem to have got disconnected, did people see my last few messages ending with "if no one else is, i'll do it" ? 05:38 -!- GAit [~GAit@unaffiliated/gait] has quit [Quit: WeeChat 1.0.1] 06:13 -!- waxwing [~waxwing@193.138.219.236] has quit [Ping timeout: 255 seconds] 06:26 -!- waxwing [~waxwing@193.138.219.250] has joined #joinmarket 06:34 -!- guest6000 [33ebbe53@gateway/web/freenode/ip.51.235.190.83] has joined #joinmarket 07:14 < Anduck> i didnt 07:22 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket 07:25 < waxwing> looking at the orderbook now suggests to me that the situation has degraded such that system may be near-unusable. there are hundreds of duplicates completely swamping honest participants. 07:25 < waxwing> since i'm not currently connected i don't know whether they are blocking, as in not responding to !auth, or doing an economic attack (doing txs and trying to benefit by increasing probability) 07:25 < waxwing> what is completely bewildering is that they use the same min/max sizes. 07:25 < waxwing> i'd ask again if someone could do a quick check to see whether they are doing the blocking behaviour. 07:25 < waxwing> has anyone written a quick hack/patch to dump equal offer amounts? i previously rejected even trying it, since it's not an actual solution, but it might help someone as of right now. 07:26 < waxwing> if no one else is, i'll do it. 07:26 < waxwing> (assuming it didn't get sent, otherwise sorry for spam) 07:26 < waxwing> i'm nearly done now, as usual it's testing that takes time. 07:35 < waxwing> huh, my brain seems to be quite suboptimal today ... first, i didn't notice that almost all of those duplicates are off the same bot name, meaning it doesnt' get any advantage. second, filtering out equal max sizes is not only a non-solution, but actually opens a massive attack vector: just duplicate everyone else's maxsize, and remove all your competition! 07:35 < waxwing> doh! 07:36 < waxwing> i thought of that the first time this came up, but it was a while back, oh well. 07:37 -!- Netsplit *.net <-> *.split quits: fluffypony 07:39 -!- Netsplit over, joins: fluffypony 07:41 < JM-IRCRelay> [AlexCato1] maybe could do as taker/tumbler (simple): ignore any makers with >2 offers or (more complex): ignore any maker which has duplicate offers for >= 2 distinct other makers 07:42 < JM-IRCRelay> [AlexCato1] that might solve the problem of killing the competition 07:43 < waxwing> alexcato: for the latter, they'd just use different bots for each duplication 07:43 < waxwing> after all in that scenario those bots wouldn't have to do anything at all apart from announce 07:45 < JM-IRCRelay> [AlexCato1] true. I cant see any (sort of simple) solution at all tbh. And I cant really imagine who would gain anything from investing resources to completely block JM; snooping i get, disrupting service is where I dont see the adversary's gains 07:47 < waxwing> yes it's curious, but that behaviour was absolutely unambiguous when i investigated a couple of months back. in more recent times it's clearly still happening (whenever i send a join i always get < N). 07:47 < waxwing> can't check literally right now, though. 07:51 < JM-IRCRelay> [AlexCato1] What might work, at least from a taker's perspecitve: regardless of N, always ask 50% (up for debate) of all makers who did send offers to join, and then only use N of them which did indeed reply when building/broadcasting the final TX and discard the others. Downside taker: cant really know in advance how high the cj fee will be. Downside maker: many 07:51 < JM-IRCRelay> unused adresses. Upside: probably no more denial of service 07:52 < waxwing> something similar to what adlai was proposing. he's intending to work on it soon. 07:52 < JM-IRCRelay> [AlexCato1] oh, great! 07:52 < waxwing> off for today, see you 07:52 < JM-IRCRelay> [AlexCato1] see you too 09:14 -!- waxwing [~waxwing@193.138.219.250] has quit [Ping timeout: 245 seconds] 09:43 -!- coins123 [~coins123@unaffiliated/coins123] has quit [] 09:44 -!- clib_ [054f49f6@gateway/web/freenode/ip.5.79.73.246] has quit [Quit: Page closed] 10:10 -!- zxccxz [4f7c12d7@gateway/web/freenode/ip.79.124.18.215] has quit [Quit: Page closed] 10:11 -!- zxccxz [4f7c12d7@gateway/web/freenode/ip.79.124.18.215] has joined #joinmarket 10:29 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-vmqfuecsxpaagymv] has quit [Quit: Connection closed for inactivity] 10:44 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-nopucefuxoylojer] has joined #joinmarket 11:55 -!- Yohkii [~Yohkii___@unaffiliated/yohkii] has joined #joinmarket 12:09 -!- cbits_ [~cbits@47.148.176.74] has joined #joinmarket 12:09 -!- Yohkii [~Yohkii___@unaffiliated/yohkii] has quit [Quit: Leaving] 16:04 -!- waxwing [~waxwing@193.138.219.250] has joined #joinmarket 18:31 -!- waxwing__ [~waxwing@14.174.32.23] has joined #joinmarket 18:31 -!- waxwing [~waxwing@193.138.219.250] has quit [Disconnected by services] 18:31 -!- waxwing__ is now known as waxwing 19:10 -!- windsok [~windsok@45.63.59.8] has quit [Ping timeout: 240 seconds] 19:29 -!- cbits_ [~cbits@47.148.176.74] has quit [Read error: Connection reset by peer] 19:47 -!- windsok [~windsok@45.63.59.8] has joined #joinmarket 20:14 -!- windsok [~windsok@45.63.59.8] has quit [Ping timeout: 240 seconds] 20:50 -!- windsok [~windsok@45.63.59.8] has joined #joinmarket