--- Day changed Fri Dec 30 2016 01:21 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-swkyhukkvunondym] has joined #joinmarket 01:30 -!- weex [sid152634@fsf/member/weex] has joined #joinmarket 04:43 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 264 seconds] 05:08 < waxwing> juscamarena: as i said above, i can't see that as likely; why would captcha be turned off for http? 05:08 < waxwing> but, haven't tried it. 05:17 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 05:24 -!- fqtw__ is now known as fqtw 05:36 -!- Empty2k12 [~Empty2k12@p4FEDFC3B.dip0.t-ipconnect.de] has joined #joinmarket 08:13 -!- ]GD [~gd@pool-100-8-68-102.nwrknj.fios.verizon.net] has joined #joinmarket 08:20 -!- ]GD [~gd@pool-100-8-68-102.nwrknj.fios.verizon.net] has quit [Ping timeout: 260 seconds] 09:29 -!- ssiswxw [2f58d41c@gateway/web/freenode/ip.47.88.212.28] has joined #joinmarket 09:46 -!- ssiswxw [2f58d41c@gateway/web/freenode/ip.47.88.212.28] has quit [Ping timeout: 260 seconds] 10:10 -!- shinobimonkey [~vagabond@107.172.254.2] has joined #joinmarket 10:22 < weex> should funding of a new wallet always start with the mixdepth 0 addresses? what if mixdepth 1 addresses were used instead? 10:23 < waxwing> weex: it's fine. use external, unused addresses but other mixdepths ok. 10:24 < belcher> depends what you're trying to do? yield generator or tumbler? 10:24 < weex> yeild generator and got an error about minsize and maxsize i think 10:24 < weex> maybe i should start with tumbler? 10:24 < belcher> depends what you're trying to do 10:25 < belcher> that minmaxsize thing probably happened because you only added a little bit (to test i assume) 10:25 < weex> what's a reasonable minimum per address with default settings? 10:26 < belcher> depends what you're trying to do, do you just want to make money from yieldgenerator? 10:26 < weex> that would be cool, but also generally interested in tumbling 10:27 < weex> so whichever's the simplest thing to get going to start 10:30 < belcher> 'per address' is irrelevant 10:30 < waxwing> for testing the yield generator, something like 0.1 would be ok (0.05 would be ok-ish for a single join, but the funds will get split over time), although you'll definitely get more activity as you go to higher numbers. if you run into errors let us know specifically what you get. 10:31 < belcher> send your bitcoins to mixdepth 0 is fine for both tumbler and yieldgen 10:33 < weex> so just sent 0.1 or greater to one address at mixdepth 0 and yeild generator should be able to do its thing? 10:34 < weex> i read on the wiki about splitting funds into three addresses but not sure what that was for really 10:34 < waxwing> weex: yeah for clarity, the reason it's advised to send multiple payments for *takers* is because they have to have valid commitments for their utxos, makers don't. so 1 pay-in is fine for a yield generator. 10:43 < weex> great, will try it out 10:47 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 260 seconds] 10:53 -!- ]GD [~gd@pool-100-8-68-102.nwrknj.fios.verizon.net] has joined #joinmarket 10:53 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket 11:16 < grubles> waxwing, pm? 11:16 < waxwing> grubles: ? 12:39 < GithubBot5678> [joinmarket] AdamISZ pushed 3 new commits to develop: https://git.io/vMLy2 12:39 < GithubBot5678> joinmarket/develop 8e0b51e Damian Mee: Add link to "High level design"... 12:39 < GithubBot5678> joinmarket/develop 374a730 Damian Mee: wording improved 12:39 < GithubBot5678> joinmarket/develop 1002bf2 Adam Gibson: Merge #686: Add link to "High level design"... 12:39 < waxwing> sorry neglected to notice lack of squash, well no big deal 12:49 < GithubBot5678> [joinmarket] chris-belcher opened pull request #687: improved patientsendpayment now that the new protocol allows it to work (develop...improve-patient) https://git.io/vMLSq 12:49 < belcher> finally got this patientsendpayment thing out of the way, can work on other stuff 13:12 < belcher> "The tumbler.py application can be made to ask you for a new address just before it needs to send, giving you the chance to click Generate New Address on whatever service you're using and copypaste it in." 13:12 < belcher> people must be doing that i guess.. 13:12 < belcher> does anyone here actually use tumbler.py on a regular basis? i get the feeling i only talk to yield generators much of the time 13:13 < waxwing> belcher: what makes you say that (certainly not that i don't think it's true, just curious what prompts it) 13:13 < waxwing> the first part, not the second 13:13 < belcher> most of the bug fixes and contributions we get seem to be much more about yieldgen (just a feeling, i could be wrong) 13:14 < waxwing> no, the first part, the tumbler part 13:14 < belcher> does anyone use it here? 13:14 < belcher> oh i was reading over the github wiki 13:14 < waxwing> the generate new address thing 13:14 < belcher> was reading over the wiki and forgot that feature existed :) 13:19 < belcher> the fees section is interesting, i wonder what a typical tumbler run costs in miner fee 13:20 < waxwing> at the time of writing that it seemed like a reasonable estimate (50c-80c per tx, nowadays it's probably more like 80c-$1.20c or something) 13:21 < waxwing> based on, i guess the average number of counterparties is ~ 5 13:23 < belcher> looking at the joinmarket twitter, seems like someone from the coin tracking startup elliptic is following 13:23 < belcher> https://twitter.com/NathanJessop 13:24 < belcher> retweeted a tweet about tumblebit.. thats confusing wouldnt that be irritating to them? 13:26 < waxwing> irritating? why's that? 13:28 < belcher> to them, their startup's business model is to spy on everyone, right? 13:28 < weex> just checked in on yield generator and got this message: IndexError: list index out of range followed by many 'failed to send ping message on socket' and irc errors 13:28 < waxwing> oh you meant, tumblebit itself irritates them. i thought you meant tweeting :) 13:28 < belcher> sorry i was unclear 13:29 < belcher> weex scrub your log and put it on pastebin 13:29 < waxwing> weex: can you give us the stack trace or, the line number where you have the indexerror 13:29 < weex> message_channel.py line 285 13:29 < weex> wil do a paste 13:30 < belcher> there is a script that scrubs private information, located in logs/ 13:30 < weex> oh nice 13:30 < waxwing> huh, looks like you don't have any orders/offers. hmm. 13:31 < waxwing> should really catch that in message_channel, because it can happen on startup 13:31 < waxwing> i have a vague memory we saw this before 13:31 < waxwing> if you have only 1 utxo and you take part in a join, you !cancel and have no offers until it confirms 13:33 < waxwing> or just have a do-nothing in on_orderbook_requested if it's empty. better. 13:33 < waxwing> kinda surprised if we haven't fixed that before, i may be forgetting something 13:34 < weex> should i restart yeild generator then, the irc messages make me think it's not connected 13:34 < weex> the log didn't have the stack trace in it but i can still paste the scrubbed log if needed 13:35 -!- King_Rex [~King_Rex@unaffiliated/king-rex/x-3258444] has joined #joinmarket 13:35 < waxwing> weex: sorry i can't be 100% sure, but most likely the simplest thing for you to do is to shut down (if it isn't already crashed), wait for a confirmation, and then restart and it should be OK. that's *if* i'm interpreting it right. 13:35 < waxwing> but, sanity check: have you started a transaction? 13:35 < weex> not that i know 13:35 < waxwing> search 'potentially earned' in the log 13:36 < waxwing> well no, better 'saw tx on network' 13:36 < weex> nope 13:36 < waxwing> in logs/.log right? 13:36 < weex> yup 13:36 < weex> i restarted it 13:37 < waxwing> ok, the other option is more basic: when you started up, it failed to actually create an offer. at this point it'll be better to actually post a scrubbed log. 13:37 < waxwing> i still suspect that what i described above is an existing bug though, belcher , thoughts? 13:37 < belcher> yes 13:38 < waxwing> i can fix it right now if i've understood it right; just return in on_orderbook_requested if self.orderlist is empty right 13:40 < weex> joinmarket is a very neat project, i'd been hearing about it for a while but finally decided to look more into it so ran through most of the setup last night 13:41 < waxwing> weex: did the payment into your wallet have a confirm when you started up? 13:41 < weex> should have, one sec 13:42 < weex> yup 13:42 < weex> i had seen that 'we have no coins' kind of message but don't see it this time 13:43 < waxwing> ah ok 'we have no coins' would explain the condition; but it's our error if we don't shut down in that scenario. i thought we did. 13:44 < weex> yeah it continued after [MainThread ] [ERROR] do not have any coins left 13:44 < waxwing> wallet-tool shows unconfirmed by default; whereas for usage only confirmed coins are used. 13:44 < weex> i'm curious as to why 5 levels of mixdepth are shown by wallet-tool.py by default 13:44 < weex> it confused me a little so i funded the second level before 13:44 < weex> but then i guess it was too little 13:44 < waxwing> you can read about the reasons for the "mixdepth" design on the wiki 13:45 < weex> cool, yeah i'm looking forward to reading up 13:45 < waxwing> it's perfectly fine to start with only 1 mixdepth funded 13:53 -!- juscamarena [~justin@47.148.176.74] has quit [Ping timeout: 265 seconds] 13:55 < weex> love that continuously compounded interest rate calc, as long as it's not negative 13:57 < belcher> it goes negative if you initiate a lot of coinjoins (with sendpayment or tumbler) 13:59 < weex> orders can be removed and reposted right? or are they just posted and expire? 14:00 < weex> if i hit ctrl-c on yeild generator does that leave stale orders behind is really my question 14:00 < belcher> they expire if the bot that made them quits 14:01 < belcher> looks like someone accidently sent coins to an example address on the wiki https://insight.bitpay.com/address/1JPFmg1RSa2gtzcsow9fBjwdvWPsxcP3eX 14:01 < belcher> that address is from here https://github.com/JoinMarket-Org/joinmarket/wiki/Using-the-JoinMarket-internal-wallet#funding-wallet-and-displaying-balance 14:02 < belcher> both transactions are mined within the same block, i wonder if the original owner got them back or theres a bot watching every address there 14:03 < weex> might be a good idea to change a char or two on those addys 14:03 < belcher> yeah 14:04 < weex> the privkey is there too then? 14:04 < belcher> yeah the mnemonic recovery seed is there as an example 14:04 < belcher> someone once accidently sent coins to an example address for which there was no privkey, and pm'd me asking if i had it 14:05 < weex> i wouldn't be surprised if that was in some bot's wallet dictionary 14:06 < waxwing> doubtless there are bots constantly trawling github for private keys 14:09 -!- juscamarena [~justin@47.148.176.74] has joined #joinmarket 14:25 -!- juscamarena [~justin@47.148.176.74] has quit [Ping timeout: 258 seconds] 14:28 -!- juscamarena [~justin@47.148.176.74] has joined #joinmarket 14:33 -!- juscamarena [~justin@47.148.176.74] has quit [Ping timeout: 245 seconds] 14:33 -!- juscamarena [~justin@47.148.176.74] has joined #joinmarket 16:23 -!- Empty2k12 [~Empty2k12@p4FEDFC3B.dip0.t-ipconnect.de] has quit [Remote host closed the connection] 17:06 < weex> if you want to add more funds to a wallet, does the yield generator need to be restarted or will it notice the new funds at some point 17:07 < belcher> it will notice 17:07 < belcher> although restarting makes it notice faster : 17:07 < belcher> :p 17:10 -!- juscamarena [~justin@47.148.176.74] has quit [Quit: Leaving] 17:10 -!- juscamarena_ [~justin@47.148.176.74] has joined #joinmarket 17:12 < weex> looks like i had one join, though i'm running core on another machine so swapped localhost for the local ip address in the code, guess we'll see on the next join if the notify works 17:14 < belcher> you have to edit joinmarket.cfg for that too iirc 17:14 < belcher> since by default the notify thread only binds to localhost 17:18 -!- juscamarena_ [~justin@47.148.176.74] has quit [Quit: Leaving] 17:18 -!- juscamarena [~justin@47.148.176.74] has joined #joinmarket 17:18 < weex> didn't see that in the .cfg file, but found the string in yieldgenerator.py 17:20 < belcher> ah good, probably that 17:20 < belcher> iv never done it before but i remember something 17:23 < juscamarena> I wouldn't trust them 17:24 < juscamarena> wrong chat* disregard 18:31 -!- fqtw_ [~me@port-92-192-77-238.dynamic.qsc.de] has joined #joinmarket 18:34 -!- juscamarena [~justin@47.148.176.74] has quit [Remote host closed the connection] 18:35 -!- fqtw [~me@port-92-192-79-225.dynamic.qsc.de] has quit [Ping timeout: 248 seconds] 19:14 -!- King_Rex [~King_Rex@unaffiliated/king-rex/x-3258444] has quit [Remote host closed the connection] 19:21 -!- juscamarena [~justin@47.148.176.74] has joined #joinmarket 19:41 < GithubBot5678> [joinmarket] instagibbs opened pull request #688: fixup README installation tar command (master...readmefixup-1) https://git.io/vMtUp 19:54 < instagibbs> which module is "Queue"? getting "no module named" error 20:07 < instagibbs> used python3 venv nevermind... 20:49 < GithubBot5678> [joinmarket] juscamarena opened pull request #689: Clear up installation using virtualenv (develop...juscamarena-readme-clarification) https://git.io/vMtk6 21:13 < juscamarena> ah, I should prob pull that to master 21:17 < GithubBot5678> [joinmarket] juscamarena opened pull request #690: Clear up installation using virtualenv (master...juscamarena-virtualenv-clearity) https://git.io/vMtIu 22:02 < weex> 24 pull requests, are all of those in process or some stale?