--- Day changed Wed Jan 04 2017 01:12 -!- Giszmo [~leo@46.128.114.214.dynamic.cablesurf.de] has joined #joinmarket 01:52 -!- windsok [~windsok@45.63.59.8] has quit [Ping timeout: 272 seconds] 01:54 -!- fqtw [~me@port-92-192-106-145.dynamic.qsc.de] has joined #joinmarket 02:06 -!- berndj [~berndj@mail.azna.co.za] has quit [Ping timeout: 256 seconds] 02:19 -!- windsok [~windsok@45.63.59.8] has joined #joinmarket 04:38 < waxwing> belcher: the couple of things i mentioned in the issue is enough, plus i should have mentioned you do need your ssh key configured. 04:38 < waxwing> let me know if i can help, otherwise i can of course just merge anything you want me to right now 04:40 < waxwing> i'll start now with any no-brainers 04:42 < GithubBot5678> [joinmarket] AdamISZ closed pull request #694: Removed an infinite loop that resulted in a 4gb log file (develop...inf-loop-fix) https://git.io/vMmrS 04:44 < waxwing> 679 still waiting for fix ; empty2k12 not here? 04:53 < GithubBot5678> [joinmarket] AdamISZ pushed 2 new commits to develop: https://github.com/JoinMarket-Org/joinmarket/compare/5d1b96029e5b...9862e5e5badd 04:53 < GithubBot5678> joinmarket/develop 8e8b9a1 instagibbs: fixup README installation step 04:53 < GithubBot5678> joinmarket/develop 9862e5e Adam Gibson: Merge #691: fixup README installation steps... 04:56 < waxwing> i'll see if i can do a little test run of patientsendpayment before merge. belcher : would be great to add a test for it to the suite. 05:00 -!- windsok [~windsok@45.63.59.8] has quit [Ping timeout: 248 seconds] 05:23 < waxwing> commented. will wait for your call belcher 05:32 -!- windsok [~windsok@45.63.59.8] has joined #joinmarket 05:32 < belcher> waxwing i think yes lets merge patient 05:32 < waxwing> ok, will do; any plan to do a test though? there's a few different modes. 05:33 < waxwing> it'll be hard admittedly, well, relatively time consuming anyway 05:33 < belcher> eventually 05:33 < waxwing> gotcha. also going to merge the most recent 05:34 < waxwing> you've got some aberrant trailing whitespaces there, not that i care :) 05:35 < GithubBot5678> [joinmarket] AdamISZ pushed 1 new commit to develop: https://github.com/JoinMarket-Org/joinmarket/commit/58a55f9ece653a11dd42fa8a2d9010c10c368743 05:35 < GithubBot5678> joinmarket/develop 58a55f9 Adam Gibson: Merge #687: improved patientsendpayment now that the new protocol allows it to work... 05:36 < GithubBot5678> [joinmarket] AdamISZ pushed 1 new commit to develop: https://git.io/vMOxf 05:36 < GithubBot5678> joinmarket/develop 05b758c Adam Gibson: Merge #695: Removed configurable mixdepths from yieldgens, also reworded error message... 05:37 < GithubBot5678> [joinmarket] AdamISZ closed pull request #690: Clear up installation using virtualenv (master...juscamarena-virtualenv-clearity) https://git.io/vMtIu 05:38 < belcher> so github-merge.py requires you to configure you ssh key? im guessing it connects to github using ssh 05:39 < waxwing> belcher: yeah 05:39 < waxwing> sensible thing to do anyway 05:39 < waxwing> i don't *think* it works without. pretty sure. 05:40 < waxwing> that virtualenv thing juscamarena : see my comment. well hardly a big deal either way. 05:47 < waxwing> yuck, 589 *should* be a no-brainer but the whole mixdepths thing became such a tangle :( 05:49 < belcher> AlexCato wants to merge 1 commit into JoinMarket-Org:develop from unknown repository 05:50 < belcher> did he delete his branch? 05:50 < waxwing> yeah that's weird isn't it. maybe. 05:58 < waxwing> i could easily spend 8 hours a day testing and reviewing PRs and issues and not run out of work, like ever, at this rate :) 05:58 < waxwing> needless to say i am not going to do that i think :) 05:59 < waxwing> mr !orderbook-tourettes is still at it 06:01 < waxwing> i can only assume they are trying to get a high time resolution DB of the orderbook, but don't they realise they get that anyway? 06:05 < waxwing> belcher: chose 480 if you like. small victories :) 06:06 < waxwing> close 06:06 < belcher> there is no PR #480 06:07 < waxwing> issue 06:07 < belcher> ah yes 06:12 < waxwing> belcher: is 661 also addressed? i think so? 06:13 < belcher> oh yes 06:13 < belcher> i didnt even remember that 06:13 < belcher> that issue 06:14 < waxwing> i guess we could make much greater use of labels to help us find old issues that relate to something new 06:14 < waxwing> (i.e. in this case the label 'patientsendpayment') 06:30 -!- quitobro [640c6e95@gateway/web/freenode/ip.100.12.110.149] has joined #joinmarket 06:32 < quitobro> morning guys/gals :) 06:33 < quitobro> question about tumbling. so let's say i have 100 BTC to make it a round number. i want to mix/tumble all those coins. 06:34 < quitobro> i am supposed to break it into 3 or 4 chunks and send to the ~4 or 5 addresses in my wallet that have the *same* mix depth? 06:34 < belcher> yes 06:34 < belcher> well 3 addresses is fine 06:36 < quitobro> okay and they all should be at same mix depth right? 06:36 < quitobro> are these 2 the same mix depth: 06:36 < quitobro> m/0/1/0/000 06:36 < quitobro> m/0/1/0/001 06:36 < quitobro> OR these two: 06:36 < quitobro> m/0/1/0/000 06:36 < quitobro> m/0/2/0/000 06:36 < quitobro> i think it's the 2nd exmaple yea? 06:38 < waxwing> the first one is two addresses in external on the same mixdepth 06:39 < waxwing> see https://github.com/JoinMarket-Org/joinmarket/wiki/Using-the-JoinMarket-internal-wallet#funding-wallet-and-displaying-balance 06:39 < waxwing> the first chunk of "external" there (000-005) they are the same mixdepth, that's what we mean 06:39 < waxwing> umm https://github.com/JoinMarket-Org/joinmarket/wiki/Add-Pushbullet-notifications-to-your-Yield-Generator 06:39 < waxwing> https://github.com/JoinMarket-Org/joinmarket/wiki/Add-Telegram-Notifications-to-your-Yield-Generator 06:39 < waxwing> umm 06:39 < waxwing> weex: i think maybe this should have been discussed? 06:40 < waxwing> belcher: ping, see ^ 06:40 < belcher> yeah i was thinking about those, they might be more appropriate as a reddit or forum post 06:41 < waxwing> well for all i know it's A-OK, but i haven't even looked at it yet. btw also a problem with the wiki is the ordering of the articles. 06:41 < waxwing> i remember when i added the "source commitments for joins", the "managing the wallet" fell off the bottom of the view. 06:41 < waxwing> for me, anyway 06:42 < belcher> yep 06:42 < belcher> we could put the links on the main wiki page 06:43 < waxwing> you can add a custom sidebar. at least it would be nice to have those two pages *not* at the top, although actually as of right now, if none of us have reviewed them they should be (temporarily) removed. 06:44 < waxwing> if i just delete them do they stay in the history? 06:44 < waxwing> i'll wait. 07:00 -!- quitobro [640c6e95@gateway/web/freenode/ip.100.12.110.149] has quit [Ping timeout: 260 seconds] 07:04 < weex> waxwing: ? 07:07 < waxwing> weex: you've added wiki pages for those notification tools, you should have discussed it with us first. 07:07 < weex> I don't think that was me 07:07 < waxwing> oh sorry heh 07:08 < waxwing> why did i think that was you? github user is meedamian 07:08 < weex> But I agree the sidebar is confusing 07:08 < waxwing> indeed, it's quite annoying i don't see an option to reorder the list. hopefully it can be done, that'd be much better. 07:08 -!- Yohkii [~Yohkii@unaffiliated/yohkii] has joined #joinmarket 07:11 -!- Yohkii [~Yohkii@unaffiliated/yohkii] has quit [Quit: Mutter: www.mutterirc.com] 07:22 -!- windsok [~windsok@45.63.59.8] has quit [Ping timeout: 272 seconds] 07:27 -!- buckowski [buckowski@gateway/shell/elitebnc/x-xtxtxsmfkylvdoqf] has quit [Quit: ereet] 07:30 -!- buckowski [buckowski@gateway/shell/elitebnc/x-qyywcfhgncfdthsc] has joined #joinmarket 07:33 -!- Netsplit *.net <-> *.split quits: arubi 07:42 -!- Netsplit over, joins: arubi 07:45 -!- quitobro [b84b6304@gateway/web/freenode/ip.184.75.99.4] has joined #joinmarket 07:45 < quitobro> so, 'mixdepth' refers to a chunk of contiguous wallet addresses - just confirming 07:45 < quitobro> example from the doc: 07:45 < quitobro> docs* 07:45 < quitobro> external addresses m/0/0/0 xpub6Btm9LzaCFjWozatijp1sQ68a9eTAzfv2MS2SGei8NTyhCMc8UkqENm8xagcukVtZwDecgeBzn5zA4CKqq887Pp5u7F4ZG9S1DaDXH64dQT m/0/0/0/000 1JPFmg1RSa2gtzcsow9fBjwdvWPsxcP3eX new 0.00000000 btc m/0/0/0/001 1AaCpeMit59ExfSvP3M3bTnMkhXgecSPeY new 0.00000000 btc m/0/0/0/002 1NmDrVbtk6kfAYbBVo7Miv8eCYHHefZkjs new 0.00000000 btc m/0/0/0/003 1NKitLXm7FdgbHuENvFXRCxVH32N5XXMQ5 new 0.00000000 btc m/0/0/0/004 1 07:46 < waxwing> technically it refers to an "account" in bip32 parlance, one branch for 'external' and one for 'internal' - the former being addresses to pay into 07:46 < quitobro> i'm going to send my BTC in groups of 4 (25% each) to 4 addresses in one of my wallet's mixdepth groupings 07:46 < belcher> yes pretty much, mixdepths are seperate identities 07:48 < quitobro> cool. qq regarding this example from the tumbling docs: 07:48 < quitobro> https://www.dropbox.com/s/xgnsosdgbpn4j5s/Screenshot%202017-01-04%2010.48.04.png?dl=0 07:49 < quitobro> in this example the user is sending BTC from their coinjoin wallet *to* multiple addresses located... where 07:49 < belcher> to their electrum wallet, in that example 07:50 < quitobro> cool, so they're basically tumbling their coins on the way out, got it 08:03 -!- windsok [~windsok@45.63.59.8] has joined #joinmarket 08:03 < quitobro> hey guys - do i need to wait for a certain n confirmations before running a yield generator with new coins i've just sent to my wallet? 08:04 < belcher> no you dont 08:04 < quitobro> the wallet shows the coins as being 'used' at the addresses i sent them to 08:04 < belcher> anyway your yieldgen will detect it anyway and start using them 08:05 < belcher> so you're running a yieldgen and tumbler both at the same time? 08:05 < quitobro> tumbler is only used to do an obfuscated send out from the wallet right? 08:06 < belcher> its for attempting to break the link between addresses 08:07 < quitobro> it is only used in the context of sends though right 08:07 < belcher> what do you mean? 08:07 < belcher> sends as opposed to just holding, yes 08:07 < quitobro> like you don't tumble the coins in place 08:07 < quitobro> gotcha 08:07 < belcher> you could, if you send them to your own wallet 08:08 < quitobro> oooh. to a different mix depth? 08:08 < belcher> for example yes 08:08 -!- fqtw [~me@port-92-192-106-145.dynamic.qsc.de] has quit [Ping timeout: 272 seconds] 08:09 < quitobro> nice - good idea, tx for the suggestion 08:25 -!- Giszmo [~leo@46.128.114.214.dynamic.cablesurf.de] has quit [Quit: Leaving.] 11:09 <+JM-IRCRelay> [mrnice] having a problem sending a transaction: 11:09 <+JM-IRCRelay> [mrnice] python sendpayment.py -N 0 -m x --fast wallet.json 0 address 11:09 <+JM-IRCRelay> [mrnice] Would you like to push to the network? (y/n):y 11:10 <+JM-IRCRelay> [mrnice] error pushing = -xx yy: bad-txns-inputs-spent 11:10 < waxwing> are you using Core or blockr? 11:11 <+JM-IRCRelay> [mrnice] core 11:11 < waxwing> hmm. that's strange, your Core instance should be up to date, i'm not sure how it could have got the status of your utxos wrong. 11:11 <+JM-IRCRelay> [mrnice] this level had a problem previously and could not complete for some reason. 11:12 <+JM-IRCRelay> [mrnice] the level does show coins with: 11:13 <+JM-IRCRelay> [mrnice] python wallet-tool.py --fast wallet.json display 11:13 < waxwing> btw did you change the index_cache to make syncing work quicker? 11:14 < waxwing> i guess at this point you could start by sanity checking whether each of the addresses shown to have balance do indeed have it; it seems to be saying that one of the utxos is "stale" (i.e. already spent) 11:14 <+JM-IRCRelay> [mrnice] no. moving coins to the new wallet. tried smaller numbers twice and both instance had less coins. 11:14 < waxwing> ah, i see. well that's annoying, eh. 11:15 < waxwing> you seem to have hit a particularly unlucky combination of circumstances. i'd start by doing that sanity check. 11:15 <+JM-IRCRelay> [mrnice] yeah, ok. will check that. How can i do that with the local node instead of a web based block explorer? 11:16 < waxwing> i'd have to check the rpc command. it should be fine to do because you've imported those addresses. 11:17 <+JM-IRCRelay> [mrnice] I will try moving the node to a rpi3. Hopefully that will help also with some more speed. 11:17 <+JM-IRCRelay> [mrnice] yeah. nevermind I will read up or use a web block explorer. thanks. 11:17 < waxwing> listunspent seems like it'll have the info, obviously you'll need to filter. 11:18 <+JM-IRCRelay> [mrnice] right yes. 11:18 < waxwing> well we're happy to help, especially since this seems like an unusual situation. i find it hard to understand why you've got "inputs spent" after a sync. 11:18 < waxwing> since -N 0 is literally just going to take the full set of utxos it sees as valid in that mixdepth, *immediately* after sync. 11:19 < waxwing> well, -N 0 + amount 0 11:20 < waxwing> yeah i really can't see how that could happen. you've *just* queried your node. youre not running any other jm bots at the same time are you? 11:21 <+JM-IRCRelay> [mrnice] no only ther "interactive" sendpayment, which does a not so fast sync first. 11:22 < waxwing> the fast option for sync applies just the same for interactive/non-interactive (you mean coinjoin/non-coinjoin) 11:23 <+JM-IRCRelay> [mrnice] I mean "interactive" because it takes over 1h to sync the wallet in this case. 11:24 < waxwing> which mixdepth is it? i wonder if there's something screwy that could happen there. 11:24 < waxwing> oh, before you were saying even with --fast it was over 1h? 11:24 < waxwing> back in a sec 11:24 <+JM-IRCRelay> [mrnice] -m 1 11:25 < waxwing> hmm no i can't see any possibility of a problem with mixdepth 1 11:26 <+JM-IRCRelay> [mrnice] im running the wallet tool again now and will then dump the output for reference, check addresses individually and get back with findings when done. 11:26 < waxwing> at this point i would be sanity checking each address in the mixdepth against an external block explorer to see if there's a disparity (coins spent) 11:26 < waxwing> yeah 11:26 < waxwing> sorry it's probably obvious but i can't see what would cause it 11:27 <+JM-IRCRelay> [mrnice] yeah. I am thinking it may be some quirk with the large/ slow wallet or possibly a timout of sorts in the code? 11:28 < waxwing> there's no timeout with sync (as you see :) ), we do have timeouts for confirmation threads but doesn't apply here 11:28 < waxwing> again though, was it --fast that took 1 hr? 11:28 < waxwing> not that it changes anything for this new issue, just wanted to be clear on the symptoms you described before 11:29 <+JM-IRCRelay> [mrnice] --fast takes over 1h with the 150k+ index_cache for the level, yes. 11:29 < waxwing> right in the "interactive" comment above you said "1h in this case" 11:30 < waxwing> i just didn't understand what you meant by "interactive" i guess 11:30 <+JM-IRCRelay> [mrnice] waiting for a reaction of the script for 1h is not very "interactive" is all ;-) 11:31 < waxwing> did you previously try the non --fast option? 11:32 <+JM-IRCRelay> [mrnice] I think by mistake a few times, but interrupted it *way* before completion. 11:32 -!- grbs [~grubles@unaffiliated/grubles] has quit [Quit: brb] 11:32 < waxwing> please note that a lot of these questions are me "feeling around", i don't necessarily have fixed ideas in mind. as you can imagine it's often very hard to debug problems with this kind of software because we can't look at all the data. 11:33 < waxwing> scrubbed logs help, but doesn't apply here. 11:34 < waxwing> i have a vague idea about a reason the --fast might be taking so long here, but don't want to get sidetracked by it really. so did you say you tried reducing the number in index_cache to < 150k and it resulted in coins not showing up? 11:35 -!- waxwing [~waxwing@62.205.214.125] has quit [Quit: Leaving] 11:35 -!- waxwing [~waxwing@62.205.214.125] has joined #joinmarket 11:36 -!- Netsplit *.net <-> *.split quits: Pilate, +JM-IRCRelay, gowness, CoJaBo, Rix, ratoder, core 11:36 < waxwing> sorry just re-connected, may have missed a message 11:36 -!- JM-IRCRelay [~RelayBot@dyn208-233.ph.ic.ac.uk] has joined #joinmarket 11:36 -!- CoJaBo [~aztec@c-73-175-29-36.hsd1.pa.comcast.net] has joined #joinmarket 11:36 -!- Netsplit over, joins: ratoder 11:36 -!- Netsplit over, joins: core 11:36 -!- JM-IRCRelay [~RelayBot@dyn208-233.ph.ic.ac.uk] has quit [Changing host] 11:36 -!- JM-IRCRelay [~RelayBot@unaffiliated/belcher] has joined #joinmarket 11:36 -!- Pilate [~pilate@pilate.io] has joined #joinmarket 11:36 -!- CoJaBo [~aztec@c-73-175-29-36.hsd1.pa.comcast.net] has quit [Changing host] 11:36 -!- CoJaBo [~aztec@unaffiliated/cojabo] has joined #joinmarket 11:36 < waxwing> mrnice did you see my last message ending "... showing up"? 11:36 -!- Rix [~rix@unaffiliated/rix] has joined #joinmarket 11:36 -!- Pilate is now known as Guest39715 11:37 < JM-IRCRelay> [mrnice] reading now. 11:38 -!- Netsplit over, joins: gowness 11:38 < JM-IRCRelay> [mrnice] waxwing: no problem. Am happy to debug this intertactively if possible. 11:40 < JM-IRCRelay> [mrnice] waxwing: two of the index_cache numbers are over 150k. Tried 15k for starters and "lost" some coins. Tried 30k and still "lost" coins. So did no further testing and proceedeed to moving coins. 11:41 < waxwing> gotcha. 11:41 < JM-IRCRelay> [mrnice] The time/benefit seemed not worth further testing. 11:41 < waxwing> and you're sure you reverted the index_cache field to exactly what it was before? sorry, have to ask :) 11:42 < waxwing> although, huh, even if you didn't it wouldn't result in this error, so forget that. 11:43 < JM-IRCRelay> [mrnice] well, cannot sear on it now, but pretty sure, would have to check, but only that possibly the last digits are different. 11:44 < waxwing> hang on. is it possible you tried to do this once, and it pushed, and now you're trying again? hmm, hardly likely. no i think i should just wait until you've done that sanity check before asking anything else. 11:45 < JM-IRCRelay> [mrnice] tried, but failed. Also there are no coins on the address. Already checked that. 11:45 < waxwing> no coins on which address? 11:45 < JM-IRCRelay> [mrnice] the recipient address, sorry. 11:45 < waxwing> oh, i see 11:47 < JM-IRCRelay> [mrnice] Anyone have any info an mining hw availability? Looking at S9's specifically? 11:49 < waxwing> double check the joinmarket.cfg in your jmkt directory doesn't have "blockr" in it mrnice. 11:50 < JM-IRCRelay> [mrnice] waxwing: no. 11:51 < waxwing> oh silly me, i just realised that whatever is causing this is also what caused the infinite loop problem you had. 11:52 < waxwing> so shouldn't be surprised this is happening. for some reason your wallet thinks it has a utxo which is actually already spent. and for some reason this is persisting. 11:52 < waxwing> did you ever import/export keys from this wallet to another/from another? 11:53 < JM-IRCRelay> [mrnice] oh! 11:53 < JM-IRCRelay> [mrnice] no import/exports no. 11:55 < waxwing> whatever weird scenario i can dream up, i can't get it to make sense. if utxo A is spent, then the process of syncing should see that. 11:55 < JM-IRCRelay> [mrnice] is it possible to interrup the script *at a critical point* to cause this? 11:56 < JM-IRCRelay> [mrnice] the yg script that is? 11:56 < waxwing> it shouldn't be, no, the syncing process should recognize the current state 11:57 < waxwing> it's more conceivable to get errors like: not recognizing coins you do currently own; but not "thinking you have coins when they are no longer there" 11:58 < JM-IRCRelay> [mrnice] right 11:59 < waxwing> let me know when you've managed to do that sanity check 12:02 < JM-IRCRelay> [mrnice] yes sure. 12:03 < waxwing> i suppose right now if i was looking at this on my own machine, i would just be doing `listunspent`, dumping it and then filtering it by account name, then comparing it with the output of wallet-tool. 12:04 < waxwing> because that's what the code does, in function sync_unspent() in BitcoinCoreInterface, in joinmarket/blockchaininterface.py 12:04 < waxwing> whatever (hopefully only one?) utxo that is behaving weirdly should be at least isolatable like this 12:06 < JM-IRCRelay> [mrnice] ;-) much faster... 12:06 < waxwing> for reference https://github.com/JoinMarket-Org/joinmarket/blob/master/joinmarket/blockchaininterface.py#L813-L824 12:13 < JM-IRCRelay> [mrnice] waxwing: hold on. how do I find out which is the righ jm wallet instance? "joinmarket-wallet-xxxxxx" 12:13 < waxwing> hmm to do it manually without waiting 1hr :) let me think. 12:13 < waxwing> first, if you have already stored a copy of the wallet-tool output it's showed there. 12:14 < waxwing> also it'll show up in the log files of any previous runs (the files in logs/) 12:14 < waxwing> oh hmm maybe it doesn't show up? for ygs at least. 12:15 < waxwing> damn, no i don't think it does. we can do it with python without too much hassle, hang on. 12:15 < JM-IRCRelay> [mrnice] well, I have at least 2 jm wallets which I have used concurrently in the past days. Could this have caused a problem? 12:16 < JM-IRCRelay> [mrnice] not in parallel, but during the same time period serially. 12:17 < waxwing> in theory as long as they're separate it should be fine; each wallet has its own "account" in Core, with a separate name, so everything is stored separately. 12:17 < waxwing> is the other one functioning OK? 12:18 < waxwing> if it is, run wallet-tool on it, look at its name, then you know the name you want is the other one :) 12:18 < waxwing> oh damn even wallet-tool doesn't show the name :( 12:22 < waxwing> mrnice do you still need the name or are we past that now? (i think we are) 12:33 < waxwing> we seem to have a situation where Core is reporting a utxo as unspent in 'listunspent' in a "joinmarket-xxx" account, but it is actually spent. 12:33 < waxwing> just an update from PM discussion with mrnice 12:33 < waxwing> the node is synced. 12:33 < waxwing> (and the utxo spending was a while back, weeks or something) 12:40 -!- Guest39715 [~pilate@pilate.io] has quit [Changing host] 12:40 -!- Guest39715 [~pilate@infoforcefeed/pilate] has joined #joinmarket 12:40 -!- Guest39715 is now known as Pilate 12:51 < belcher> waxwing weird! 12:52 < waxwing> continuing chat in PM, i'm seeing less and less likelihood of that not being the case. 12:53 < waxwing> it looks like the tx spend that was not "seen" by listunspent was a normal JM tx, and the yg continued to run normally for a while until the infinite loop hit. 12:53 < waxwing> i'm musing now about whether this has happened before, it seems a little unlikely that anyone else could have had this and *not* eventually hit the infinite loop. 12:54 < waxwing> what's particularly annoying is that it doesn't seem to correct itself, it just persistently records this utxo as unspent. 12:59 < JM-IRCRelay> [mrnice] btw: this may have been introduced by the pre 0.2.2 JM version. 13:08 < JM-IRCRelay> [mrnice] Can now confirm that this pre dates the 0.2.2 JM changeover. 13:13 < waxwing> mrnice and before you were using which version? 13:13 < waxwing> to be clear, the evidence suggests that it's unlikely to matter which version, but anyway, for info 13:36 < adlai> belcher: largest btc purchase i ever made was from a guy who bought them in .ar 13:36 < belcher> argentina? 13:36 < waxwing> .ar is a good place for bitcoin pirates :) 13:40 < waxwing> maybe it's wences cesares 13:43 * adlai motions for #joinmarket-support or #joinmarket-dev or #noob-noise or somesuch 13:43 < adlai> not that i don't like helping people, but the scrollbacks are only getting longer 13:44 < waxwing> we could do joinmarket-dev, not against that idea at all 13:44 < waxwing> hassle maintaining bridges though 13:44 * adlai creates #joinmarket-ninjas 13:44 < adlai> no need for bridges 13:45 < adlai> short-term talk happens here 13:45 < waxwing> slack? /me runs away 13:45 < adlai> long-term talk happens there 13:45 < waxwing> some people do -dev but don't want freenode 13:45 < waxwing> (Tor etc) 13:45 < adlai> fuck slack. and freenode supports tor now, doesn't it? 13:45 < waxwing> you have to be registered right 13:45 < waxwing> it was a joke, take it easy :) 13:46 * adlai grins 13:46 < adlai> #joinmarket-ninjas is ready for use 13:46 < waxwing> what's wrong with "-dev"? 13:46 < adlai> too ballmer ( https://www.youtube.com/watch?v=Vhh_GeBPOhs ) 13:47 < waxwing> people don't have much cognitive bandwidth, make it easy for them? 13:48 * adlai registers both, use either one you like :) 14:01 -!- deafboy [quasselcor@cicolina.org] has quit [Ping timeout: 264 seconds] 14:03 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket 14:18 < juscamarena> slack isn't that bad. It just runs like shit. haha 14:18 < adlai> how about the fact that it's a centralized piece of melena? 14:19 -!- Netsplit *.net <-> *.split quits: arubi 14:20 < belcher> i only use slack because many others do... and only through an irc bridge 14:20 -!- quitobro [b84b6304@gateway/web/freenode/ip.184.75.99.4] has quit [Ping timeout: 260 seconds] 14:21 * adlai spent a while irc-bridged to a slack, couldn't take the cognitive bandwidth and recently dropped out 14:22 < waxwing> tumblebit slack has enabled an irc server, so no bridge needed, suits me fine, just another server in my list 14:23 < waxwing> i'd also prefer not to use it, but that's not so bad 14:24 < adlai> how does one go about joining that? tumblebit.slack.com doesn't seem to allow registration 14:25 < belcher> waxwing adlai ever thought about going to bitcoincore slack? its alright over there 14:25 < waxwing> ah yes. i think you need an account. with an account you can get a one-time password to log in. 14:25 < waxwing> sorry forgot that bit :) 14:25 * adlai does have a slack.com account 14:25 < belcher> i had to get an invite, i dont know if they changed policies 14:26 < adlai> belcher: honestly, i haven't considered it because c++ is too foreign a language for me to be of much use over there 14:26 < adlai> do you think it's worth lurking? 14:26 < belcher> lol it doesnt involve any developing 14:26 < waxwing> i don't really want to run the slack client on anything. actually i spend too much time on IRC as it is :) 14:26 < belcher> all the c++ core developres are on freenode 14:26 < belcher> no the bitcoin slack is for the general public 14:27 < belcher> its less geeky than irc 14:27 < adlai> ah. i think i have enough social media already. 14:27 < belcher> i have slack irc on the same client as freenode 14:27 < waxwing> oh, so you have it set up like tumblebit belcher ? 14:27 < belcher> yep 14:27 < waxwing> oh ok, i might do that, doesn't hurt, thanks 14:28 * adlai refloats the question about the tumblebit slack 14:28 < belcher> i actually have 11 irc servers open right now.. 14:28 < belcher> although 1 of them is the miniircd running on my own computer 14:28 < waxwing> adlai: yeah like i say, i forgot, you need to get the 1 time password. you'd need to ask ethan for an invite i *think* 14:28 < waxwing> 11 wow, i only have .. 6 i think 14:29 < waxwing> no 5, only 1 miniircd :) 14:29 * adlai is down to 4 :P 14:29 < adlai> although if i lurk in tumblebitcoincoreslack, i'll be tied with waxwing 14:31 < waxwing> that sounds ... undesirable :) 14:39 < adlai> with, not to! 14:40 < waxwing> oh, like equal. heh. 14:40 < waxwing> late here :) 14:40 < juscamarena> he, joined the core slack through irc too? 14:40 < adlai> maybe sleep? although we all have our work to do 15:06 < adlai> "Our python code only supports python3" (tumblebit) 15:06 < adlai> looks like we have the beginnings of a beautiful dichotomy, between jm being stuck on 2, and this 15:07 < belcher> recodes into python3 accepted :) 15:07 < belcher> or c++ even 15:09 < adlai> better yet, --c++ 15:11 < lebeev> I was considering paying someone for a twisted rewrite 15:11 < lebeev> but I spotted one on github 15:12 < lebeev> is that less terrible than the main jm 15:13 < belcher> a rewrite of twisted? or joinmarket using twisted? 15:13 < lebeev> joinmarket using twisted 16:26 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Remote host closed the connection] 16:36 -!- instagibbs [~instagibb@pool-100-15-114-3.washdc.fios.verizon.net] has quit [Ping timeout: 264 seconds] 16:37 -!- instagibbs [~instagibb@pool-100-15-114-3.washdc.fios.verizon.net] has joined #joinmarket 17:04 -!- juscamarena [~justin@47.148.176.74] has quit [Remote host closed the connection] 17:29 -!- juscamarena [~justin@47.148.176.74] has joined #joinmarket 18:41 < adlai> lebeev: it's not production-ready, but you're welcome to test and report problems you find to waxwing 18:41 < adlai> (it's his project so far, although with full blessing of the JoinMarketFoundation) 18:42 < belcher> waxwing is working on a rewrite with twisted? i thought that was that guy whos name started with g 18:49 -!- juscamarena [~justin@47.148.176.74] has quit [Quit: Leaving] 18:52 < adlai> ;;seen glenn h tarball, phd 19:05 -!- Netsplit *.net <-> *.split quits: dee-vee_, OverlordQ 19:05 -!- OverlordQ [~ovrlrdq@199.101.100.58] has joined #joinmarket 19:05 -!- dee-vee [~dv@root-core.org] has joined #joinmarket 19:11 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket 19:16 -!- windsok [~windsok@45.63.59.8] has quit [Ping timeout: 258 seconds] 19:52 -!- windsok [~windsok@45.63.59.8] has joined #joinmarket 23:05 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #joinmarket 23:32 -!- coins123 [~coins123@unaffiliated/coins123] has quit []