--- Day changed Wed Mar 29 2017 00:07 -!- juscamarena [~justin@] has quit [Ping timeout: 240 seconds] 00:10 -!- juscamarena [~justin@] has joined #joinmarket 00:16 -!- Michail1 [~michail@michail.com] has quit [Ping timeout: 260 seconds] 00:17 -!- Michail1 [~michail@michail.com] has joined #joinmarket 00:20 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has joined #joinmarket 00:30 -!- MaxSan [~one@] has quit [Ping timeout: 240 seconds] 00:57 -!- MaxSan [~one@] has joined #joinmarket 01:00 -!- Michail1 [~michail@michail.com] has quit [Ping timeout: 268 seconds] 01:01 -!- Michail1 [~michail@2603:3023:a04:2900:217:a4ff:fef0:e3fc] has joined #joinmarket 01:47 -!- pigeons [~pigeons@] has joined #joinmarket 01:47 -!- pigeons is now known as Guest99195 01:49 -!- Guest99195 is now known as pigeons 01:59 -!- griest [49280799@gateway/web/freenode/ip.] has joined #joinmarket 02:00 < griest> what is a reasonable miner/tx fee for each participant? 02:01 < griest> The tumbler tells me that it is 50000 but that seems high 02:03 -!- Beverly [~Beverly@] has quit [Remote host closed the connection] 02:04 -!- Bud [~Bud@] has joined #joinmarket 02:09 < griest> @Bud? 02:11 < MaxSan> usually works out as a % 02:11 < MaxSan> i have seen beteween 0.002 and 0.07% ish 02:11 < MaxSan> of total TX ^^ 02:17 < griest> @MaxSan oh does that include maker fees? 02:17 < MaxSan> yeah 02:17 < MaxSan> you dont need an @ sign for irc btw :) 02:18 < griest> so to get an estimate of the total fees, I would simply multiply the miner/tx fee estimate by the number of transactions? 02:18 < griest> oh okay lol 02:18 < griest> MaxSan 02:26 < griest> um so the tumbler just segfaulted 02:28 < MaxSan> weird 02:29 < MaxSan> you running against a node or 02:29 < MaxSan> some service? 02:29 < griest> full node 02:30 < griest> im on tails btw 02:31 < griest> MaxSan it gave me a torsocks error "unable to resolve" and then segfaulted 02:33 < MaxSan> you cant run via torsocks 02:33 < MaxSan> i get that too 02:34 < MaxSan> ummm 02:34 < MaxSan> waxwing: ^^ 02:34 < MaxSan> or belcher ^^ 02:34 < MaxSan> there is a way to run it im sure 02:34 < MaxSan> one of those two could help you I think better 02:35 < griest> well i run it with torify, is this what you mean? 02:36 < griest> `torify python tumbler.py .....` 02:36 < griest> when I run it without torify it just hangs 02:39 < griest> so it goes: all makers have sent their signatures; txid = ; torsocks error: unable to resolve; seg fault 02:41 -!- Michail1 [~michail@2603:3023:a04:2900:217:a4ff:fef0:e3fc] has quit [Ping timeout: 246 seconds] 02:43 -!- Michail1 [~michail@michail.com] has joined #joinmarket 02:49 < griest> MaxSan it crashes right after sending some bitcoins, are they gone forever? 02:49 < MaxSan> nah 02:49 < griest> how do i recover them? 02:49 < MaxSan> they are either still in your wallet or been sent to the address you requested 02:49 < griest> oh 02:49 < griest> okay 02:50 < MaxSan> as long as you have the seed value even if its corrupted your fine 02:50 < griest> yes i have it 02:50 < MaxSan> if you run 02:50 < MaxSan> python wallet-tool.py wallet.json 02:50 < MaxSan> and check the balance 02:50 < MaxSan> you can see if its sent 02:50 < MaxSan> it sounds like it hung before sending 02:51 < MaxSan> so should still be there 02:52 < griest> well bitcoin core acts like it has been sent 02:53 < griest> there is bc in mix depth 1 02:53 < griest> and in the internal addresses 02:53 < MaxSan> check the address on an explorer 02:56 < griest> check my receiving address? 03:00 < griest> okay so the transaction is unconfirmed, but it does show that the address has 0 btc 03:06 < griest> MaxSan you wanted me to check the external addresses in the joinmarket wallet, right? 03:08 < MaxSan> yeah 03:08 < MaxSan> check where it says the coins are 03:08 < MaxSan> on a third party block explorer 03:08 < MaxSan> make sure its the same 03:08 < MaxSan> if its seen by someone else you know the tx has propogated around the network 03:10 < griest> make sure what is the same? 03:10 < griest> MaxSan 03:11 < MaxSan> the address with the coins in? 03:14 < griest> yeah I'm sure the address is right I copy-pasted it 03:15 < griest> I can see the coins I sent in. It gives me a list of unconfirmed transactions 03:17 < MaxSan> thats fine then 03:17 < MaxSan> just wait for it in a block 03:17 < MaxSan> not sure on the crash that is odd 03:19 < griest> so then the coins should arrive in the addresses I specified? will they be tumbled at that point even though the tumbler crashed? 03:58 < MaxSan> yeah 03:58 < MaxSan> if they are in with a bunch of other addresses, they have been tumbled 04:04 < griest> so the only important part of the tumbler script is the very beginning? that's odd. should i keep running the tumbler until all of my bitcoins have been used? 04:09 < waxwing> griest: read the final section of the tumbler page on the wiki 04:10 < waxwing> if it crashed somewhere in the middle, you haven't lost coins, but the process hasn't completed, so the coins won't *all* be in the destination addresses. 04:10 < waxwing> some of them may be, or not, depends how far it got. 04:11 < waxwing> so were you running JM as in joinmarket-org/joinmarket, and was it the latest release 0.2.2? do you still have the terminal where the crash happened? 04:11 < griest> yes i still have the terminal 04:11 < waxwing> i haven't seen a segfault but this is tails with torsocks, i don't really know, but it would be of interest to see what that looks like 04:12 < griest> is there any incriminating info in the terminal output? 04:12 < griest> or can i copy paste it without any worries? 04:12 < waxwing> umm, private, not incriminating :) 04:12 < waxwing> well unless you have a rather unorthodox terminal i guess :) 04:12 < griest> well yeah that's what i mean i guess 04:12 < griest> hang on 04:13 < waxwing> just isolate the part with the crash. yeah in general output could have personal info 04:13 < waxwing> in particular addresses and txids 04:13 < waxwing> there is a scrub-log.py script, but i suspect it isn't of interest here. just wanted to see the exact message before the segfault 04:14 < griest> well it crashes after it says "all makers have sent their signatures" then the next line is txid = 04:14 < griest> and then torsocks error: unable to resolve 04:14 < griest> and then seg fault 04:14 < waxwing> the code usually handles connection failures to IRC gracefully and just keeps trying to reconnect. this is something to do with Tor/TAILS/socks 04:14 < waxwing> just "unable to resolve", nothing else? huh 04:14 < griest> yeah 04:14 < griest> i can paste it if you really want me to 04:15 < waxwing> no i just assumed you weren't giving the full message, but if that's the full one, fine 04:15 < griest> no hang on 04:15 < waxwing> i have little idea what to do about it. this was started with `python tumbler.py ..`, in a terminal, on TAILS, which version? 04:16 < waxwing> the position in the flow suggests to me that it's crashing when about to push a transaction. what is your blockchain_source in your joinmarket.cfg? 04:16 < griest> `torify python tumbler.py ....` 04:16 < waxwing> right 04:16 < griest> bitcoin core full node 04:16 < griest> so blockchain source is bitcoin-rpc 04:16 < waxwing> ok 04:17 < waxwing> was this the first transaction in the run? 04:17 < waxwing> damn this is as hard to understand as what ananteris was saying, i'm still hoping he'll get back to me with what caused his hanging. 04:17 < waxwing> he was also using Bitcoin Core on TAILS, wonder if there's a connection 04:18 < griest> full torsocks error is: `Unable to resolve. Status reply 4 (in socks5_recv_resolve_ptr_reply() at socks5.c:829) 04:18 < griest> i think it was the first transaction 04:19 < waxwing> griest: to try to figure out what's going on you could consider doing a sendpayment.py run , with -N 0, which will just send funds without coinjoin (so pretty cheap), and see if it can push the transaction successfully or whether you get the same error 04:20 < griest> should I just send it to another joinmarket address in the same wallet? 04:21 < waxwing> griest: yes you can do that safely. send to an external address in another mixdepth for example. or, hmm, the same mixdepth is fine i guess. i don't see any problem with that. 04:22 < griest> okay about to run `torify python sendpayment.py
` 04:22 < waxwing> looking for other cases of this error, here's an example: https://labs.riseup.net/code/issues/11736 04:22 < griest> okay about to run `torify python sendpayment.py
-N 0` 04:23 < griest> yeah i already found that page 04:23 < griest> setting AllowOutbounLocalHost 1 fixed another issue I was having 04:23 < griest> unfortunately setting it to 2 didn't solve the issue 04:23 < griest> this issue that is 04:23 < waxwing> griest: right i had to do that too. i think this changed somewhat in recent-ish TAILS, old versions didn't need that. 04:24 < waxwing> right. this is all a bit beyond me, but at least we need to find something reproducible. 04:25 < griest> i also had to mess with the iptables, do you want to see that command? 04:25 < waxwing> sure, please 04:25 < waxwing> i made a note of something similar somewhere but got confused. did you refer to https://github.com/joinmarket-org/tailsjoin at some point? 04:27 < griest> sudo iptables -I OUTPUT 2 -p tcp -s -d -m owner --uid-owner amnesia -j ACCEPT 04:27 < griest> yeah i wish tailsjoin worked 04:28 < griest> not even close though 04:28 < griest> i had to write a couple custom scripts to even get all the prereqs for joinmarket installed 04:28 < waxwing> yeah that exact iptables line is in the old tailsjoin repo 04:28 < griest> pip and tails do not play well together 04:29 < waxwing> if you tried it from the joinmarket-org/tailsjoin repo, might be nice to write an issue with what's wrong there. i don't blame people if not though. 04:29 < waxwing> griest: indeed there are difficulties along those lines. 04:30 < griest> btw joinmarket is not the only program that throws torsocks errors 04:31 < waxwing> ok. i don't use TAILS much, but in any case an actual segfault is a pretty extreme outcome. 04:33 < griest> i reproduced it 04:33 < griest> i ran a tumbler twice 04:33 < griest> so i ran the sendpayment 04:33 < griest> and it asks if i would like to push to the network 04:33 < waxwing> so here's what i can't make sense of: there are several rpc calls before the one that pushes the transaction; why would it crash on that one in particular? 04:33 < griest> yes right? 04:34 < waxwing> griest: well yes :) it only pushes coins from your address to your address 04:34 < waxwing> if it's reproducible there, good in a way, but i'm at a loss. 04:34 < griest> do i need to start bitcoin-qt with torify? 04:35 < waxwing> maybe try using bitcoin-cli and see if it works on command line? 04:35 < waxwing> because under the hood joinmarket is just doing json rpc calls with the same commands (same json rpc api) 04:35 < waxwing> but .. i guess this is somehow all mixed up with how torify works 04:36 < waxwing> i keep coming up with theories like 'because you run tumbler with torify, therefore the json rpc calls don't work', but it makes no sense, because the pushtx() call is not the first rpc call that joinmarket makes, there are several others 04:36 < griest> what about the interrupted tumblings though? 04:36 < griest> do i need to do something to finish them? 04:37 < waxwing> there is in fact a sanity check immediately on starting up joinmarket, where it calls the rpc 'getblockchaininfo' to check it's working 04:37 < waxwing> re: restarting see the end of the wiki page i mentioned above 04:37 < griest> so i need to get it functioning in order to recover the coins? 04:38 < griest> yeah it used to fail on the first json rpc call 04:38 < griest> before I set AllowOutboundLocalHost 04:38 < griest> 1 04:38 < waxwing> so did sendpayment work? 04:39 < griest> no 04:40 < waxwing> reproduced same error? 04:40 < griest> i think the amount was too small 04:40 < waxwing> oh :) 04:40 < griest> error pushing = -26 64: dust 04:40 < griest> should I just send all BTC in one address to another? 04:40 < waxwing> be aware that fees are much less with -N 0 (because you don't have tons of inputs) 04:41 < griest> although after the dust error it does say that the transaction was sent 04:42 < waxwing> ah interesting, that's an error in our/my coding then, i'll check, maybe it isn't checking the return value. weird. 04:43 < griest> i only sent 100 satoshis though 04:43 < griest> if that matters 04:43 < waxwing> yes, indeed. i forgot to check the return value. still, at least you still see the error message, so you know it didn't work. 04:43 < waxwing> well yes it matters in the sense that you can't do that :) the -N 0 suggestion was to attempt to reproduce the error. tumbler is very complicated, it would be more unambiguous if we could reproduce the segfault in that simple case. 04:44 < waxwing> but if you don't want to, that's fine. 04:44 < griest> so should I just send a large amount of satoshis? 04:45 < waxwing> just anything reasonable should be fine. 04:46 < griest> also, in the tailsjoin script, it sets the rpc_host to but in the wiki it sets to localhost 04:46 < griest> could that be affecting it? 04:46 < griest> also, sendpayment completed with no error 04:47 < waxwing> griest: yes i was afraid that was the case. that makes the situation more complicated i guess :( 04:48 < waxwing> thing is, if the error is connected with the IRC connections (sendpayment -N 0 doesn't use IRC at all), then i'm at a loss to know what's going on. because the terminal output you showed clearly shows that the segfault happened after all signatures were collected, and the transaction was about to be pushed to the Bitcoin network. 04:49 < griest> yeah 04:49 < griest> thats just the way of things i guess 04:50 < griest> what are my options? 04:50 < griest> can i switch to using the web blockchain? 04:52 < waxwing> not really, it's bad privacy, and blockr doesn't even work at all over Tor, there are bc.i and electrum interfaces but they're hardly tested and i doubt will work (at least, reliably), on TAILS, even ignoring privacy. 04:52 < griest> so what should I do? 04:52 < griest> debugging this is a rabbit hole 04:53 < waxwing> this remains a sore spot; Core, probably pruned, while a pain, ought to be the viable solution. i was happy to be able to get the electrum plugin working on TAILS, but it only does single sendpayments. 04:53 < waxwing> griest: are you asking how to get your coins "out"/back to somewhere else? you can use sendpayment -N 0 if you need to. and you can use amount 0 for sweeping out of mixdepths. 04:54 < waxwing> you can also do various other things i guess. 04:56 < griest> but really no chance of actually tumbling them? 04:57 < waxwing> well either we have to fix the bug in TAILS (is it a bug in torify? maybe), or you can run it not on TAILS. 04:57 < griest> what is the platform with the best support? 04:57 < griest> and would i have to clean install joinmarket? 04:58 < waxwing> ubuntu and variants i guess; prob debian also fine. 04:58 < griest> i can do ubuntu 04:59 < griest> does that leak any info though? 04:59 < griest> privacy is obv a big consideration here 04:59 < waxwing> you can run the IRC stuff over Tor. for Core, there is tor support within it. 05:00 < griest> what about join market though, should i get all my coins to mix depth of 0 or leave them where they are? 05:00 < waxwing> it's ok for tumbler if they're not all in mixdepth 0 (e.g. some coins in 1 also is fine) 05:01 < waxwing> i'm wondering about that "Unable to resolve" error, maybe it is connected with localhost v as you suggest. but, complete guess, oh well. 05:02 < griest> yeah...whoever wrote tailsjoin knew tails pretty well i guess 05:02 < griest> so I'm thinking should be right 05:02 < griest> is there any harm to running the tumbler again? 05:03 < waxwing> run wallet-tool and then just set the parameters correctly for what you see. wait for confirmation of any pending tx before restarting. 05:04 < griest> `torify python wallet-tool.py ` runs fine 05:04 < waxwing> as per https://github.com/JoinMarket-Org/joinmarket/wiki/Step-by-step-running-the-tumbler#tips--further 05:04 < griest> with 05:05 < griest> looks like everything is in mix depth 0 or 1 05:05 < griest> ^^ with 05:07 < griest> should I try to restart the tumbler from a mix depth or do a clean run? 05:07 < waxwing> you can try from mixdepth 0, since there are still coins in it 05:07 < waxwing> do you know if any txs completed? i guess not. 05:08 < waxwing> (btw this is why i added TUMBLE.log to the new version - it needs to be easier for users to see what's happened) 05:09 < griest> any txs from the failed tumblings? 05:09 < griest> the txs were confirmed 05:09 < griest> if thats what you mean 05:09 < waxwing> yes. although come to think of it, also wait for confirmation of the sendpayment -N 0 you did. 05:10 < griest> yeah i just checked 05:10 < griest> its confirmed 05:10 < waxwing> sure, give it a shot. so, you're saying, the failed tumbler runs *did* have some txs confirmed? 05:10 < griest> yeah 05:10 < griest> i checked on a bitcoin explorer 05:10 < waxwing> so that means it's for sure an intermittent error. which makes it super-hard to debug, no idea how to isolate it. 05:11 < waxwing> so i can't see how 127 v localhost could really make any difference. 05:11 < griest> nor I 05:11 < waxwing> well meh *maybe*, but really long shot 05:11 < griest> there is some extra debug info in the logs btw 05:12 < griest> so [info] all makers sent their sigs 05:12 < griest> [info] txid = 05:12 < griest> [debug] rpc:sendrawtransaction 05:12 < griest> [debug] rpc: getaccount 05:12 < griest> and thats all 05:13 < griest> so i guess it seg faults on rpc: getaccount 05:13 < waxwing> there is scrub-log.py that you can use to remove private info 05:13 < waxwing> yeah that might be interesting i guess. although no clue right now. 05:13 -!- Bud [~Bud@] has quit [Remote host closed the connection] 05:13 < waxwing> Core version for info? 05:13 < griest> alright gonna try the tumbler 05:14 < griest> bitcoin core? 05:14 < waxwing> yes 05:14 < griest> 0.13.2 05:14 -!- Marion [~Marion@] has joined #joinmarket 05:15 < waxwing> what are the timestamps on sendrawtransaction and getaccount? 05:15 < waxwing> or, the difference between them anyway 05:15 < griest> milliseconds 05:15 < griest> about 15 ms 05:15 < waxwing> ok. just nice to put these things down in case it gives someone an idea. 05:16 < griest> i can post a log if you want 05:16 < griest> and open an issue 05:16 < waxwing> run scrub-log and then maybe extract that section at the end. 05:17 < waxwing> and give the command line flags and the version info as above, then yeah, an issue would be nice, thanks. 05:18 < griest> issue on main joinmarket repo? 05:18 < waxwing> yes, let's say 05:36 < griest> waxwing: https://github.com/JoinMarket-Org/joinmarket/issues/727 05:36 < waxwing> griest: good stuff, thanks :) 05:37 < waxwing> wow is it 2.11 already? i'm still on 2.6 05:37 < waxwing> or is it 3.0 by now 05:37 < griest> thanks for the help, I'm gonna head off now but I'll be back later to bang my head against this a bit more 05:37 < griest> yeah 3.0 is in beta still i think 05:37 < griest> hey maybe that bug won't be there on 3.0 05:38 < griest> or maybe it'll have friends, who knows 06:05 -!- Marion [~Marion@] has quit [Remote host closed the connection] 06:13 -!- goregrind [~goregrind@unaffiliated/goregrind] has quit [Ping timeout: 240 seconds] 07:06 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Ping timeout: 264 seconds] 09:07 -!- MaxSan [~one@] has quit [Ping timeout: 260 seconds] 09:52 -!- MaxSan [~one@] has joined #joinmarket 12:19 -!- griest [49280799@gateway/web/freenode/ip.] has quit [Ping timeout: 260 seconds] 13:12 -!- MaxSan [~one@] has quit [Ping timeout: 246 seconds] 13:37 -!- MaxSan [~one@] has joined #joinmarket 13:58 -!- nkuttler [~nkuttler@unaffiliated/nkuttler] has quit [Ping timeout: 258 seconds] 13:59 -!- nkuttler [~nkuttler@unaffiliated/nkuttler] has joined #joinmarket 16:34 -!- deafboy [quasselcor@cicolina.org] has quit [Remote host closed the connection] 16:37 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket 17:37 -!- MaxSan [~one@] has quit [Ping timeout: 258 seconds] 17:43 -!- Giszmo [~leo@pc-240-13-215-201.cm.vtr.net] has quit [Quit: Leaving.] 19:24 -!- Rspigler [~Rspigler@] has joined #joinmarket 19:35 -!- Rspigler [~Rspigler@] has quit [Quit: Textual IRC Client: www.textualapp.com] 19:40 -!- zxccxz [5db78007@gateway/web/freenode/ip.] has quit [Ping timeout: 260 seconds] 22:17 -!- core [~core@unaffiliated/core] has quit [Excess Flood] 22:18 -!- core [~core@unaffiliated/core] has joined #joinmarket 22:31 -!- xcvvcx [53e42f33@gateway/web/freenode/ip.] has quit [Ping timeout: 260 seconds] 22:56 -!- zxccxz [5db79885@gateway/web/freenode/ip.] has joined #joinmarket 23:51 -!- xcvvcx [53e42f33@gateway/web/freenode/ip.] has joined #joinmarket 23:55 -!- zxccxz [5db79885@gateway/web/freenode/ip.] has quit [Ping timeout: 260 seconds] 23:55 -!- xcvvcx [53e42f33@gateway/web/freenode/ip.] has quit [Ping timeout: 260 seconds]