--- Day changed Mon Oct 17 2016 01:20 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has quit [Quit: Leaving.] 03:13 -!- lnostdal [~lnostdal@90.149.73.62] has joined #joinmarket 04:12 * waxwing is putting in code to sendpayment to send coins direct without JM (using -N 0). got it basically working but need to do a ton of testing. 04:45 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has joined #joinmarket 04:53 -!- DeathShadow--666 [~IDSE@S0106a84e3f595813.vc.shawcable.net] has quit [Ping timeout: 250 seconds] 05:58 -!- lnostdal [~lnostdal@90.149.73.62] has quit [Quit: lnostdal] 06:06 < JM-IRCRelay> [waxwing] joinparty: good news, thanks! 06:07 < GithubBot5678> [joinmarket] AdamISZ opened pull request #637: add direct send feature from mixdepth using -N 0 in sendpayment scrip… (develop...direct_send) https://git.io/vPPhs 07:59 * adlai is still travelling, will review soon... 09:29 -!- JJ [dfb6f65f@gateway/web/freenode/ip.223.182.246.95] has joined #joinmarket 10:10 < arubi> I must be doing something wrong, running a few bots on regtest and local irc server, all but one bot are running yigens, last is running tumbler. it all runs fine but after killing the tumbler (ctrl+c) I can't use the wallet in any other program /except/ for the tumbler (not even wallet-tool display), getting the error: http://paste.debian.net/plainh/5a236a2c 10:10 < arubi> this is consistent with all bot instances and a tumble doesn't need to actually take place. simply running tumbler.py, stopping and trying wallet-tool results in an error. I checked and a new field appears in the wallet after tumbler e.g. '"index_cache": [[4, 2], [0, 9], [0, 4], [0, 0]]', if I remove this field, wallet.json works again: http://paste.debian.net/plainh/4a41db13 10:11 < waxwing> arubi: are you running the bugfix i pushed yesterday? 10:12 < waxwing> also, have you tried yg-runner.py (i guess not) it does exactly that :) 10:12 < arubi> hmm let me check 10:13 < arubi> yea I guess not :) should I follow "develop" ? 10:14 < arubi> oh I see what I did now 10:14 < waxwing> yes develop is always the latest 10:14 < arubi> was following some local branch by mistake.. 10:15 < arubi> yea I figured, git pull returned up to date so it was weird.. 10:15 < arubi> thanks. gonna try now 10:17 < waxwing> if you do tumbler without non-defaults it'll create 4 mixdepths and other scripts may complain, it's really quite bad that the new way of syncing introduced that extra fragility. 10:19 < arubi> should I explicitly ask other scripts to look at higher depths after tumbler then? 10:21 < waxwing> actually i'm not sure now why you were getting an error, i want to chase that up first. my fix was for if the tumbler created an index_cache *longer* than 5, not shorter. 10:21 < waxwing> oh i see, you were running wallet tool and it was taking default 5 10:21 < arubi> need any files before I wipe everything and start the new pull? 10:22 < waxwing> it's the deficiency of only checking that index_cache is non-empty, not checking if it's the right length, hmm. 10:22 < waxwing> same bug manifesting in a different way, oh well, a bit more work to do 10:22 < arubi> at least it's regtest coins :) 10:23 < waxwing> there's no coin safety issue here, just crash annoyance 10:23 < waxwing> you can specify the mixdepths you want in wallet-tool anyway 10:23 < arubi> yea I see, just joking. wallet tool works when removing the index_cache field 10:23 < waxwing> you could do -m 4 to it 10:24 < waxwing> but will fix next 10:24 < arubi> (trying) 10:25 < arubi> ah that works! cool. I'm just trying to get up to speed with the new version. might now that core has HD too and coin backup will get a lot easier. thanks again 10:26 < arubi> might as well* 10:33 < waxwing> arubi: if you get a chance to try out the instructions in the Testing wiki page, that'd be nice :) or did you already? (since you said you were running local ircds) 10:35 < arubi> I set it up by "feel", the only caveat I'd warn people about is "miniircd _has_ to have a motd" because else the scripts just stall on "connecting". really I just assumed I wasn't following proper instructions and didn't report :\ 10:36 < waxwing> you wouldn't have had to deal with that if you used our test setup :) 10:37 < waxwing> we have a copy of the miniircd repo, i do remember that particular nastiness 10:37 < waxwing> the test setup starts and stops regtest and miniircd for you. 10:43 < arubi> waxwing, well 1. I am using miniircd from jm-org repo, 2. I wanted a more manual test env. for really breaking things :) 10:44 < arubi> or maybe I really missed what the test setup is about and it does exactly what I want with 2. 10:44 < waxwing> hey go for it :) i will always take an opportunity to 'advertise' the test setup in the hope that some other people run it sometime; it'd be quite helpful 10:45 < waxwing> well, the scenario you described where you wanted to be able to manually try things out against an existing pit: i also often want that, i just run py.test test/ygrunner.py to get 4 yg bots up in a pit, copy-paste the seed so i have a full wallet, and then run various taker scripts. 10:46 < waxwing> here you can specify how many coins you want in each mixdepth when you run it: https://github.com/JoinMarket-Org/joinmarket/blob/develop/test/ygrunner.py#L35 10:47 < waxwing> ignore the stale comment above, that creates 5 wallets (4 ygs and 1 "spare" for you to use), and prints out the seed for that "spare" to the console 10:47 < arubi> doh. that sounds a lot easier than what I'm doing and has the same effect. I did run the "Tests" a bunch of times and it worked great. gonna use the proper way now as I can see it will save me a bunch of messing with things 10:48 < waxwing> i see from the comments at the top of the file, i originally did it so i could easily test the -qt app, saved me a ton of time trying to do that in testnet 10:49 < arubi> oh yea testnet is flaky for when you really want precise answers in short time. that's why I set it all up for regtest 10:52 < grubles> ok I don't know if I haven't had enough coffee or what but I'm getting: joinmarket.jsonrpc.JsonRpcError 10:52 < grubles> joinmarket.cfg is setup correctly and everything 10:53 < grubles> setup to communicate with my local bitcoin-qt, i mean 10:53 < waxwing> huh, someone else complained about that on github recently, and i don't know what it might be. maybe you can hack it to show the error message if all else fails 10:54 < waxwing> which command was it trying to execute? (should be just above in the log i think) 10:54 < grubles> python2 wallet-tool.py 10:54 < grubles> raise JsonRpcError(response["error"]) 10:55 < waxwing> yes, but just before that, does it show which command it was calling? 10:56 < grubles> self.rpc('importaddress', [addr, wallet_name, False]) <- this? 10:56 < waxwing> yes. something funny going on here. 10:57 < waxwing> it was able to do an initial call OK (there is an rpc call right at the start of sync) 10:58 < waxwing> this worked: https://github.com/JoinMarket-Org/joinmarket/blob/develop/joinmarket/blockchaininterface.py#L567 10:58 < waxwing> but importaddress didn't, hmm. is your node wallet-enabled? 11:00 < waxwing> grubles: going afk in a moment 11:28 < grubles> waxwing, is your node wallet-enabled? <- yes 11:56 -!- clobba [~clobba@37.220.13.51] has joined #joinmarket 12:56 < waxwing> grubles: couple of suggestions to help us figure it out: (1) try doing the importaddress manually with an rpc call (same wallet name and address ofc), also (maybe better) add a line "print(str(response))" above this line: https://github.com/JoinMarket-Org/joinmarket/blob/develop/joinmarket/jsonrpc.py#L117 13:03 -!- deafboy_ is now known as deafboy 13:13 < gmaxwell> I've made a banlist of bitcoin peers that are connecting to everyone and monitoring transactions, you might want to ban them on your own nodes. 13:13 < gmaxwell> http://0bin.net/paste/V0GAccklhV+huNVC#8uKrkZB0NYEHakf+GEf6Bz7995wvwjpYiYddPzAU71e < in CLI friendly form 13:13 < gmaxwell> http://0bin.net/paste/6t296tLNIUrLAGI4#yQCgdTXPtsfA1WqKj5Y0qXO1JE0OVfmfmgo55EwSd6n < in bitcoin-qt debug console (ready to paste) friendly form 13:14 < gmaxwell> this will ban them for 6 months. 13:14 < waxwing> gmaxwell: what do we know about 'Snoopy' ? 13:14 < gmaxwell> 12:23 < wumpus> gmaxwell: number of connections went from 54 to 14 after applying that banlist :) 13:15 < gmaxwell> I think snoopy is some university's propagation monitoring probe, as I vaguely recall. 13:15 < kakobrekla> how did you find out about those nodes ? 13:16 < gmaxwell> kakobrekla: they're (1) behaving strangely in ways that prove they are not ordinary nodes, and (2) were connected to many nodes on many different networks, in a way no benign node would. (most of them are connected to every node that can be reached, some of them multiple times) 13:16 < kakobrekla> so you scanned all the nodes yourself? 13:17 < gmaxwell> I don't want to go into the 'strangely' details in public, else I tell the spys how to behave more faithfully. 13:17 < gmaxwell> kakobrekla: no, they came to me. 13:17 < waxwing> how do we see how many connections we have? i think i might have dropped 7 13:17 < gmaxwell> these are nodes connecting _out_ to almost everyone. 13:17 < gmaxwell> waxwing: 7 out of 20? you can run a getnetworkinfo or a getinfo to see the connection count. 13:18 < waxwing> gmaxwell: yeah out of 20. i did getnetworkinfo but missed it first time. it's gone down to 13 indeed. 13:20 < waxwing> we do (optionally) distribute transactions between JM peers to randomise source somewhat, so that's another extra defence. 13:24 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket 13:47 -!- DeathShadow--666 [~IDSE@S0106a84e3f595813.vc.shawcable.net] has joined #joinmarket 14:02 -!- DeathShadow--666 [~IDSE@S0106a84e3f595813.vc.shawcable.net] has quit [Remote host closed the connection] 14:11 -!- DeathShadow--666 [~IDSE@S0106a84e3f595813.vc.shawcable.net] has joined #joinmarket 14:14 -!- clobba [~clobba@37.220.13.51] has quit [Ping timeout: 250 seconds] 14:16 -!- clobba [~clobba@37.220.13.51] has joined #joinmarket 14:25 < midnightmagic> gmaxwell: thanks 14:37 < kakobrekla> gmaxwell how do you know that those nodes are connected to every other reachable node, im looking at protocol spec and i dont see a way howd you go about it - asking the node 14:40 < gmaxwell> kakobrekla: by checking many nodes run by myself and other bitcoin developers. 14:41 < gmaxwell> it is exceptionally unlikely that someone will be connected to, say, 12 out of 12 nodes unless they are connected to almost everyone. 14:41 < gmaxwell> (doubly so since sane software won't connect out to more than 8 peers) 14:52 -!- molz [~molly@unaffiliated/molly] has joined #joinmarket 14:56 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 260 seconds] 15:43 -!- mol [~molly@unaffiliated/molly] has joined #joinmarket 15:46 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 260 seconds] 15:52 -!- molz [~molly@unaffiliated/molly] has joined #joinmarket 15:55 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 265 seconds] 16:22 -!- coins123 [~coins123@unaffiliated/coins123] has quit [Ping timeout: 256 seconds] 16:23 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 16:24 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 16:27 -!- belcher [~belcher@unaffiliated/belcher] has quit [Client Quit] 16:33 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 16:47 -!- JJ [dfb6f65f@gateway/web/freenode/ip.223.182.246.95] has quit [Quit: Page closed] 17:15 -!- mol [~molly@unaffiliated/molly] has joined #joinmarket 17:18 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 250 seconds] 18:51 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-lzkpqzhxfiujuwdu] has quit [Ping timeout: 248 seconds] 18:54 -!- btcdrak [uid165369@gateway/web/irccloud.com/x-nbgrzgpbqrokfpzj] has joined #joinmarket 19:10 < GithubBot5678> [joinmarket] WyseNynja opened pull request #638: ignore .DS_Store (develop...ignore_ds_store) https://git.io/vP1SE 19:25 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has quit [Quit: Leaving.] 19:38 -!- clobba [~clobba@37.220.13.51] has quit [Read error: Connection reset by peer] 20:24 -!- molz [~molly@unaffiliated/molly] has joined #joinmarket 20:28 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds] 20:56 -!- Cory [~Cory@unaffiliated/cory] has joined #joinmarket 21:45 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds] 21:59 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket 22:33 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds] 22:33 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket 22:46 -!- Krafty [1810d321@gateway/web/freenode/ip.24.16.211.33] has joined #joinmarket 22:46 -!- Krafty is now known as TailsUser 22:47 < TailsUser> I've got $6 in a joinmarket wallet file. I tried plugging the seed key into electrum, but it didn't work. I must be missing something simple. 22:48 < TailsUser> Maybe there's a space at the end or something silly. 22:51 < TailsUser> Well this is annoying. 22:59 < TailsUser> yay figured out the -p command. 22:59 -!- moli [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer] 23:00 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket 23:28 -!- molz [~molly@unaffiliated/molly] has joined #joinmarket 23:31 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds] 23:33 -!- coins123 [~coins123@unaffiliated/coins123] has joined #joinmarket