--- Day changed Thu Aug 04 2016
00:17 < waxwing> belcher_: thanks for that, i'll merge it, it needs some extra edits: remove hostid from default config and also from get_irc_mchannels. i'll add that in later today.
00:18 < waxwing> belcher_: re: secp256k1, which OS?
00:19 < waxwing> for windows step 4 in the wiki page on windows install shows a method that seems to work.
00:19 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
00:19 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket
00:20 < waxwing> also there has been an update to the secp256k1-py binding repo that changed the install method, but i think it only applied to linux, in any case, when i get a chance i will review the situation for windows. for sure it's worked in the past.
00:21 < waxwing> and so far i'm not getting reports on people who can't install it, so let me ask again: is anyone still not using the secp256k1 binding?
00:24 < waxwing> hmm those extra edits are only clean-up i think, not technically needed.
00:25 < waxwing> no, it is needed so get_irc_mchannels doesn't complain
00:31 < GithubBot5678> [joinmarket] AdamISZ closed pull request #598: made irc code detect network name and use it for hostid (0.2.0...0.2.0-networkname) https://git.io/v6LPk
00:43 < waxwing> belcher_: this output suggests to me there might be an error with freenode? :
00:43 < waxwing> 2016-08-04 08:42:00,894 [MCThread    ] [DEBUG]  found network name: CgAn;
00:43 < waxwing> 2016-08-04 08:42:00,909 [MCThread    ] [DEBUG]  Connected to IRC and joined channel
00:43 < waxwing> 2016-08-04 08:42:05,197 [MCThread    ] [DEBUG]  found network name: Rizon;
00:43 < waxwing> 2016-08-04 08:42:05,473 [MCThread    ] [DEBUG]  Connected to IRC and joined channel
00:43 < waxwing> 2016-08-04 08:42:05,576 [MCThread    ] [DEBUG]  Connected to IRC and joined channel
00:44 < waxwing> a parsing error i mean (because i connected to cgan, freenode and rizon)
01:01 < waxwing> ah here's the problem:
01:02 < waxwing> 005 J5F6kNS1xHAhCWMv CHANTYPES=# EXCEPTS INVEX CHANMODES=eIbq,k,flj,CFLMPQScgimnprstz CHANLIMIT=#:120 PREFIX=(ov)@+ MAXLIST=bqeI:100 MODES=4 NETWORK=freenode KNOCK STATUSMSG=@+ CALLERID=g :are supported by this server
01:02 < waxwing> note the ":" in CHANLIMIT=#:120
01:34 -!- lnostdal [~lnostdal@15-64-11.connect.netcom.no] has joined #joinmarket
02:03 -!- Giszmo [~leo@ppp-188-174-93-152.dynamic.mnet-online.de] has joined #joinmarket
02:43 -!- berndj [~berndj@197.242.93.84] has quit [Ping timeout: 260 seconds]
03:52 -!- Cory [~C@unaffiliated/cory] has quit [Ping timeout: 265 seconds]
03:57 -!- Cory [~C@unaffiliated/cory] has joined #joinmarket
04:59 -!- grubles [~buttsniff@unaffiliated/grubles] has joined #joinmarket
05:02 -!- berndj [~berndj@197.242.93.84] has joined #joinmarket
05:17 -!- hazed_and_confus [32aa86c0@gateway/web/freenode/ip.50.170.134.192] has joined #joinmarket
05:18 < hazed_and_confus> hi, I've created a second wallet file so I can start tumbling, but how do I get the wallet address for the tumbler script? There's a bunch of addresses listed by wallet-tool on the intermediate wallet but I'm not sure which one to use...
05:18 < hazed_and_confus> I'm pretty much entirely new to BTC and JM so feel free to ELI
05:18 < hazed_and_confus> 5
05:22 -!- King_Rex [~King_Rex@unaffiliated/king-rex/x-3258444] has joined #joinmarket
05:23 < OverlordQ> to deposit, put them in first 'new' address in depth 0
05:24 < hazed_and_confus> OverlordQ: that's the one on the "external addresses m/0/0/0 <this_part>" line, right?
05:25 < OverlordQ> yup
05:26 < hazed_and_confus> OverlordQ: thanks!
05:28 < OverlordQ> err no, not that <this_part> part
05:29 < OverlordQ> below that line that has the xpub<whatever>
05:29 < OverlordQ> should be m/0/0/0/001 if it's a new wallet that has 'new' beside it with a balance of zero
05:29 < hazed_and_confus> OverlordQ: oh, so... "m/0/0/0/000 <this_part> new 0.00000000 btc" part?
05:30 < OverlordQ> yup, that'll be the first address in the wallet
05:30 < hazed_and_confus> cool, thank you so much
06:26 -!- hazed_and_confus [32aa86c0@gateway/web/freenode/ip.50.170.134.192] has left #joinmarket []
06:46 -!- Guest88 [~textual@41.21.229.128] has joined #joinmarket
06:58 -!- Guest88 [~textual@41.21.229.128] has quit [Ping timeout: 252 seconds]
07:00 -!- mkarrer [~mkarrer@142.red-83-47-107.dynamicip.rima-tde.net] has quit [Remote host closed the connection]
07:01 -!- mkarrer [~mkarrer@142.red-83-47-107.dynamicip.rima-tde.net] has joined #joinmarket
09:59 -!- imposter [uid57046@gateway/web/irccloud.com/x-jcgjdnfehucchhxr] has joined #joinmarket
10:14 < waxwing> randomized utxo selection algo would be very helpful
10:31 < waxwing> blockcypher published a pastebin http://pastebin.com/i4C02xeA from their post: https://blog.blockcypher.com/finding-bitfinexs-bits-de7044185ed3#.by4cjf614
10:35 < waxwing> it seems a little unlikely that they have such good network analytics that they can say that those IP addresses are actually meaningful?
10:38 -!- Einherjer [~einherjer@69.64.40.177] has quit [K-Lined]
10:42 < waxwing> damn JM is fast when you have only 1 counterparty :)
10:58 < waxwing> for some reason my walletnotifys aren't working on my testnet setup on vps. ports look right, hmm.
11:03 < waxwing> hmm not the most profound bug ever, the notify lines were commented out.
11:53 < waxwing> nkuttler: there was another protocol break yesterday night, so feel free to update when it's convenient, thanks
11:54 < nkuttler> waxwing: up
11:56 < waxwing> tks
12:00 < waxwing> nkuttler: can you check the J59B log? i just tried one and it didn't respond, but didn't seem to crash
12:01 < waxwing> possibly there's a config entry missing or something, i'm not sure what it'd be.
12:03 < nkuttler> blacklisted it seems
12:11 < waxwing> nkuttler: right. sorry to be a pain, can you send/show me joinmarket.cfg?
12:13 < nkuttler> no problem :)
12:13 < waxwing> and latest, right? a255d5d993ad16dcc11fe6a8da268bf991a1ae3f
12:28 < nkuttler> a255d5d993ad16dcc11fe6a8da268bf991a1ae3f
12:29 < waxwing> yes, error is repeatable, but i can't make sense of it. got enough info though, thanks, i'll investigate.
12:30 < waxwing> btw you have 'joinmarket-pit2' repeated in the cfg, should be just 1 for 1 server. and the hostid field can now be removed, that's no longer needed.
12:32 < nkuttler> hm, joinmarket-pit2 only appears once?
12:32 < nkuttler> or do you mean to remove the other channel?
12:33 < waxwing> in the joinmarket.cfg you sent me you have channel = joinmarket-pit2, joinmarket-pit2
12:35 < nkuttler> hm
12:37 < waxwing> damn, tried to recreate the situation as exactly as possible: my 2 bots on freenode, tx against them, but don't get this same effect. it's really hard to see how it managed to blacklist that commitment, it didn't exist before. but it was repeatable.
12:44 < waxwing> nkuttler: are the last two values in 'blacklist' ae099 and 1bad ? not that probably tells me anything, but to sanity check
12:45 < nkuttler> waxwing: yes
13:02 < fronti> not enough counterparties to fill order, ending
13:03 < fronti> means what it tell? not enough participants (in the testnet client) for a send?
13:03 < waxwing> fronti: yes
13:04 < waxwing> remember it doesn't only depend how many counterparties, but also whether they have a big enough size for your order. in case it helps.
13:05 < waxwing> which pit are you in? if only cgan i will restart a bot or two
13:05 < waxwing> i was doing testing separately in freenode for a bit
13:06 < fronti> MESSAGING]
13:06 < fronti> host = irc.cyberguerrilla.org
13:06 < fronti> channel = joinmarket-pit2
13:06 < fronti> its this?
13:07 < waxwing> fronti: yes
13:07 < waxwing> btw are you on the latest commit?
13:07 < fronti> it was a git clone https://github.com/JoinMarket-Org/joinmarket.git
13:08 < fronti> just 20 minutes ago
13:08 < waxwing> fronti: ok great
13:08 < waxwing> i started two up on cgan
13:08 < waxwing> i think one has ~ 13btc and the other only ~0.5 offered or something
13:09 < waxwing> well anyway you can see easy enough
13:09 < waxwing> fronti: https://joinmarket.me/obtest/
13:09 < waxwing> fronti: oh you're not using the new version
13:09 < waxwing> use 0.2.0
13:10 < waxwing> https://github.com/JoinMarket-Org/joinmarket/tree/0.2.0
13:10 < fronti> ok i do  
13:24 < fronti> hmm..
13:24 < fronti> oinmarket/joinmarket/irc.py", line 430, in run self.sock = ssl.wrap_socket(self.sock)
13:25 < fronti> SSLEOFError: EOF occurred in violation of protocol (_ssl.c:590)
13:25 < waxwing> fronti: i have found that cgan doesn't allow more than ~ 3 (not sure exact) simultaneous connections, and i get that error if i make too many.
13:26 < waxwing> basically it's sending EOF and dropping the connection. and i think you'll find it drops *all* your connections at that point, and you have to wait a bit.
13:26 < waxwing> if you like you can join on freenode or rizon and do tests there.
13:26 < fronti> ok, so i can empty the disher and then try again :)
13:27 < waxwing> :)
13:33 < waxwing> fronti: ok, i can try a tx with that new one if you like
13:34 < waxwing> can you send me in privmsg your POLICY section of joinmarket.cfg?
13:36 < waxwing> fronti: success: 9171e1c5faff21cbd05cd6cb26a6f269767c44f7fb2125f2b9f4652b3ce3cbc4
13:37 < waxwing> that's yours and one of mine via freenode only
13:37 < fronti> cooll my first jm transaction :)
13:37 < nkuttler> mh. too bad freenode doesn't do tor..
13:38 < waxwing> yeah, well, this is just testing, i remember back in the day having this problem
13:38 < nkuttler> [DEBUG]  Commitment: 767e31a0c5dd360deea96052d06b1f4748830b0ec08b28ebca1b1dcd400dbc8a blacklisted.
13:38 < nkuttler> fronti: let me know if you need more conis
13:38 < nkuttler> coins
13:38 < waxwing> nkuttler: your bot seems to love censorship :)
13:39  * nkuttler doesn't even know what or why the blacklist is..
13:39 < waxwing> i also have 767 in my lists
13:39 < nkuttler> is that against the privacy attacker?
13:40 < waxwing> yes, i'm working on blog posts about it, see https://joinmarket.me/blog/blog/joinmarket-020-changes/ and the previous one
13:40 < waxwing> or read the 156 issue, that's where it all started, or the gist, or... well you get the idea :)
13:40 < nkuttler> oh right, i read that
13:40 < nkuttler> should probably read it again
13:40 < waxwing> so far i've spent about an hour trying to figure out what happened with your bot, i'm quite flummoxed
13:41 < nkuttler> if you need me to try something just ask
13:41 < nkuttler> fwiw, happends to both basic and deluxe 
13:41 < waxwing> right, that crossed my mind, but i could see no difference there
13:42 < waxwing> it might also be easier to explain (not really) if you were on more than one server, but you weren't.
13:42 < nkuttler> well. i don't *have* to use tor
13:42 < waxwing> it's pretty much the simplest scenario, but the log clearly indicates that the commitment was in the list *before* you received it in !fill, but that seems impossible.
13:42 < nkuttler> i could join freenode as well if that helps
13:43 < nkuttler> hm
13:43 < waxwing> is it up right now?
13:43 < nkuttler> yeah
13:43 < waxwing> let me do *one* more with it, then if same behaviour, let's switch to freenode for an expt.
13:43 < nkuttler> sure
13:43 < waxwing> have to remember to switch one off..
13:47 < waxwing> huh, it worked. that time, i picked only 1 (you), though.
13:47 < nkuttler> it did?
13:48 < nkuttler> deluxe says [DEBUG]  Commitment: 04631fb0e8d1f060de8f49fb484973513d5ebf7bcfab0dbe296b4867a299b279 blacklisted
13:48 < nkuttler> ah, looks like basic made it
13:49 < nkuttler> it was J57mNmFTT2FyhUF6, right?
13:49 < waxwing> nkuttler: that blacklisted comment is correct
13:49 < waxwing> it means that you're accepting broadcasts of commitments from other makers
13:49 < waxwing> the one that was selected was J58 iirc
13:49 < nkuttler> ah, great
13:50 < waxwing> i should probably change the log to say 'accepted broadcast or something' to distinguish
13:50 < nkuttler> ah, i always get confused because logs/yigen-statement.csv has a delay
13:50 < waxwing> heh, or something not in quotes :)
13:50 < waxwing> yeah waits for conf
13:51 < waxwing> sorry about the crappy names but needed to make the multi-server thing work
13:52 < waxwing> nkuttler: so i'll try again against the deluxe, it's J5Bj right?
13:54 < nkuttler> i think so, yeah
13:54 < nkuttler> odd. didn't it use to print the nick in the log
13:55 < waxwing> print which nick in which log?
13:55 < waxwing> oh at the start, right
13:55 < nkuttler> yeah, the nick the bot selects
13:55 < waxwing> yes, you're absolutely right, that is an annoyance with the change that i forgot about.
13:56 < waxwing> but the bot log file is still there, i just ls -lart and whatnot for now
13:56 < nkuttler> right
14:02 < waxwing> i'm getting lost, where are we now? :)
14:03 < waxwing> ok i want to do the deluxe on its own, then do both together
14:04 < waxwing> ok, seemed to work on its own (J5Bj)
14:05  * waxwing waits for 1 conf
14:06 < waxwing> ok, wish me luck, i'm going in
14:08 < waxwing> no, didn't work when choosing both. hmm.
14:10 < waxwing> nkuttler: are your bots in different directories?
14:10 < nkuttler> waxwing: no
14:10 < waxwing> ok. this is most likely the cause. let me think a minute.
14:11 < nkuttler> oh?
14:11 < nkuttler> hmm
14:11 < waxwing> yeah they share one blacklist file
14:11 < nkuttler> ok
14:11 < waxwing> i did that deliberately because people want to restart their bots all the time, but they (mostly) want to remember what has been blacklisted for obvious reasons
14:17 < waxwing> it's an interesting point; in doing the regtest testing, i run everything out of the same directory, and specifically put code in to create separate blacklist files for that case. but given the point above, i can't see much sense in doing the same for mainnet. perhaps i'm missing an obvious alternative.
14:20 < waxwing> nkuttler: so yeah just run one yg out of that dir, or make a second (but if it's a hassle don't bother). btw you can run taker bots out of the same dir no problem, obv it doesn't read that.
14:29 < nkuttler> waxwing: hm, couldn't there be separate blacklists? for wallets or yigen, or if that's possible nick?
14:29 < waxwing> nkuttler: well it's not that there couldn't (like i say, i do that with regtest), but it's that i don't think that's what we want, because people will stop and start ygs all the time
14:30 < waxwing> and they won't generally want to have forgotten everything that's blacklisted. by design it's a permanent effect.
14:30 < nkuttler> yeah, not by nick then
14:30 < waxwing> so you're thinking by wallet, hmm
14:30 < nkuttler> just wondering
14:36 < waxwing> it's kind of the opposite of broadcast .. partition the info between "entities" (wallets). i'd prefer it if when i start with a new wallet, it remembers the blacklist.
14:38 < waxwing> having said that, if it avoided this kind of thing happening, it may be worth it. it just feels awkward to me.
15:03 < nkuttler> maybe just an option, --blacklist
15:03 < nkuttler> then people can do whatever they want :) probably needs some documentation though
15:14 < nkuttler> or if not maybe there should be a lock file or something, to prevent two yigens from running at the same time?
15:34 -!- fdgsdf [549161f0@gateway/web/freenode/ip.84.145.97.240] has joined #joinmarket
15:51 < nkuttler> btw, the bots use privmsg? just wondering, privacy, server admin etc
16:00 -!- emzy [~quassel@raspberry.emzy.de] has joined #joinmarket
16:01 -!- Giszmo [~leo@ppp-188-174-93-152.dynamic.mnet-online.de] has quit [Ping timeout: 276 seconds]
16:04 -!- molly [~molly@unaffiliated/molly] has joined #joinmarket
16:07 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
16:12 -!- fdgsdf [549161f0@gateway/web/freenode/ip.84.145.97.240] has quit [Quit: Page closed]
16:27 -!- molz [~molly@unaffiliated/molly] has joined #joinmarket
16:30 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 258 seconds]
16:48 -!- belcher [~user@unaffiliated/belcher] has joined #joinmarket
17:51 -!- lnostdal [~lnostdal@15-64-11.connect.netcom.no] has quit [Read error: Connection reset by peer]
18:02 -!- ghf_ [44064732@gateway/web/freenode/ip.68.6.71.50] has joined #joinmarket
18:03 -!- ghf_ [44064732@gateway/web/freenode/ip.68.6.71.50] has quit [Client Quit]
18:06 -!- imposter [uid57046@gateway/web/irccloud.com/x-jcgjdnfehucchhxr] has quit [Quit: Connection closed for inactivity]
18:22 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
19:40 -!- HostFat [~HostFat@2-235-224-2.ip230.fastwebnet.it] has joined #joinmarket
19:53 -!- King_Rex [~King_Rex@unaffiliated/king-rex/x-3258444] has quit [Remote host closed the connection]
21:32 -!- HostFat [~HostFat@2-235-224-2.ip230.fastwebnet.it] has quit [Ping timeout: 260 seconds]
23:04 < waxwing> nkuttler: the bots use privmsg but E2E encryption (after handshake)
23:47 < nkuttler> that makes sense