--- Day changed Tue Jun 28 2016
00:08 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
03:44 -!- lnostdal [~lnostdal@64-81-11.connect.netcom.no] has joined #joinmarket
04:12 -!- viasil [~viasil@198.12.75.25] has quit [Ping timeout: 240 seconds]
04:50 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket
05:06 -!- p15 [~p15@155.91.145.64.unassigned.bringover.net] has quit [Ping timeout: 250 seconds]
05:25 -!- lnostdal [~lnostdal@64-81-11.connect.netcom.no] has quit [Ping timeout: 246 seconds]
05:44 < belcher_> gmaxwell waxwing fluffypony i linked RedAcor who runs cyberguerilla IRC the list of known chainalysis IPs and he said the bot didnt match any of them
05:44 < fluffypony> curious 
05:53 -!- viasil [~viasil@198.12.75.25] has joined #joinmarket
05:54 < belcher_> well they could easily get an alternate ip
07:25 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #joinmarket
08:24 -!- lnostdal [~lnostdal@64-81-11.connect.netcom.no] has joined #joinmarket
08:45 < OverlordQ> Yeah
08:46 < OverlordQ> Cheap as dirt to use EC2 to setup a proxy network
09:27 -!- coins123 [~coins123@unaffiliated/coins123] has quit []
10:03 <+JM-IRCRelay> [lorem] hey, so this is a bit offtopic here, but is there a way to access the bitcoin channels on freenode through tor? i found some references to qpb relay which midnightmagick runs, but no specics on how to access it
10:09 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has quit [Read error: Connection reset by peer]
10:10 < OverlordQ> not sure
10:19 -!- lnostdal [~lnostdal@64-81-11.connect.netcom.no] has quit [Ping timeout: 258 seconds]
10:27 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #joinmarket
10:29 < grubles> is message=Anti-Leech fairly new?
10:29 < grubles> seems like a couple of people are spamming !orderbook and Anti-Leech
11:00 -!- lnostdal [~lnostdal@64-81-11.connect.netcom.no] has joined #joinmarket
11:00 -!- molz [~molly@unaffiliated/molly] has joined #joinmarket
11:04 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 244 seconds]
11:07 -!- lnostdal [~lnostdal@64-81-11.connect.netcom.no] has quit [Ping timeout: 276 seconds]
11:53 < jm_user> tor and irc are quite mutually exclusive at best i have found, unless you come up with some cuistome shell accounts or gateways. unfortunately.
11:54 < OverlordQ> some networks have hidden service IRC servers, but freenode disabled theirs
12:04 < pigeons> i mentioned OFTC the other day
12:13 < jm_user> how does the +JM-IRCRelay work?
12:17 < jm_user> having issues  with JM and bitcoin-core node access. Still no joy after 3 or 4 -rescans any pointers?
12:28 -!- molly [~molly@unaffiliated/molly] has joined #joinmarket
12:31 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 246 seconds]
12:35 < OverlordQ> pretty sure the JM-IRCRelay is relaying matrix to irc
12:35 < OverlordQ> I think
12:36 < OverlordQ> jm_user: What exactly is the error/issue?
12:36 < waxwing> no, it's a Cgan bridge
12:36 < OverlordQ> ah
12:36 < waxwing> seconded, jm_user you'd need to say what you're trying to do
12:46 -!- OverlordQ [~ovrlrdq@199.101.100.58] has quit [Remote host closed the connection]
12:47 < grubles> maybe he needs to wallet-tool.py -g 60
12:49 < waxwing> could be, and sometimes bumping addr_req_count helps (although not necessary, and hacking code, bleh). what should never be necessary is rescanning multiple times.
12:49 < waxwing> well, hmm, if recovering i can't remember now if once is enough.
12:50 < waxwing> but if not recovering shouldn't be needed full stop
12:50 < grubles> i think i've had to rescan more than once when using -g 60
12:50 < waxwing> alexcato : not sure, but i may have reproduced your error condition.
12:50 < pigeons> i have one wallet i cant recvoer at all
12:51 < pigeons> i ran it 200 times
12:51 < pigeons> i metnioned it the other day
12:51 < waxwing> grubles: were you recovering, or did you have a joinmarket wallet.json?
12:51 < grubles> recovering from seed
12:51 < pigeons> ah maybe i should try recovering from seed, i was running the baket up wallet.json
12:52 < waxwing> pigeons: yeah keep a copy, the indices can help you figure out where you are
12:52 < waxwing> pigeons: maybe you needed  a large gap limit. but, if you already have a wallet.json, you shouldn't have even needed that measure.
12:52 < grubles> i didn't even know you could backup from the wallet.json
12:53 < waxwing> i'm not sure there's any meaning to "recover from backup", if you have the json you have the wallet. i was just recommending keeping it to refer to the indexes.
12:53 < pigeons> it tells you importing addresses and run it again, usually rn it a few dozen times and your good to go, but this one doesnt. i have an idea why, but i dont see any other transactions doing that so it will really give away a lot of mine if i mention it
12:54 < waxwing> pigeons: yeah, what i'm saying is, look at the indexes being created in the new json and compare with the old. see if the indexes are advancing.
12:54 < grubles> i guess i didn't mean recover from wallet.json but having the addresses imported into -qt
12:54 < pigeons> ok yeah
12:56 < waxwing> yeah, seems like we're all on the same page. usually it's: if you have the json already, you'll at worst need to run several times to import enough extra; if you don't then you may need a big -g so it can search far enough forwards.
12:57 < waxwing> and if you're on a different/new bitcoind then you might need to -rescan so it can see the transactions
12:58 < pigeons> right. usually that's fine. in this case i did all those things
12:58 < pigeons> i'll try again latr restoring from seed and compare the indexes 
12:59 < waxwing> pigeons: almost certainly doesn't help, but the 1-10 list here *might* help you understand something: http://0bin.net/paste/gCSoYSCCEcOsCYmo#3ZjlEicKTeFAK+y9Br1ZH40GWgmMqgR2YAHe1wNbVef
12:59 < waxwing> ignore the text at the top, that was me musing about something but not relevant
13:00 < waxwing> huh, 1-13 not 1-10
13:00 < pigeons> thanks
13:27 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
13:28 -!- OverlordQ [~ovrlrdq@199.101.100.58] has joined #joinmarket
13:28 < OverlordQ> well that was interesting
13:28 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket
13:36 -!- _zack [50543825@gateway/web/freenode/ip.80.84.56.37] has joined #joinmarket
13:36 < _zack> hello
13:37 < _zack> anybody about?
13:38 -!- OverlordQ [~ovrlrdq@199.101.100.58] has quit [Changing host]
13:38 -!- OverlordQ [~ovrlrdq@mediawiki/OverlordQ] has joined #joinmarket
13:40 -!- _zack [50543825@gateway/web/freenode/ip.80.84.56.37] has quit [Client Quit]
13:40 < OverlordQ> somebody got into my server over the serial connection and starting poking around for bitcoin wallets :|
13:41 < waxwing> dang .. serial connection..
13:41 < OverlordQ> yeah, so either somebody at the host, or a leak from the host
13:45 < OverlordQ> jokes on them, wallet.dat is watch-only
13:46 < pigeons> jokes on them, this is my dogecoin|dao|ixcoin box
13:47 < OverlordQ> heh
13:47 < OverlordQ> So yeah, I needed a good reason to kill the box and now I do :D
13:49 < jm_user> I have got bitcoin-core running and would like to change from blockr to core for the jm yield script.
13:50 < jm_user> OverlodQ: >ou have a serial link on your server?
13:50 < OverlordQ> jm_user: It's got IPMI
13:51 < jm_user> OverlordQ: Ah. OK.
13:53 < jm_user> realized thta i needed wallet support, which is now complied in, buts till not really working with JM.
13:54 < OverlordQ> full core w/ wallet support isn't implemented yet
13:54 < OverlordQ> it only imports watch-only addresses to bitcoin for now
13:54 < jm_user> the wallet is in JM, but the watch only does not work. at least i cannot get it to.
13:55 < jm_user> but core requires wallet support for watch only no?
13:57 < OverlordQ> I dont think
13:58 < waxwing> it requires wallet support in the sense that Bitcoin Core needs to be compiled with support for wallets.
13:59 < OverlordQ> Oh yes, sorry. was thinking of compiling for electrum
14:10 < waxwing> alexcato now wondering whether the problem isn't simply that the code doesn't recover if *all* message channels are lost. there is a single on_welcome_trigger which is enforced to only trigger once. i will look more carefully later.
14:11 < jm_user> is the output of wallet-tool.py supposed to be the same between blockr and core interface?
14:13 < waxwing> sure
14:18 < jm_user> then i have a problem. I keep egtting the message that I may run bitcoind with  -rescan option if recovering an old wallet, but nothing else.
14:19 < jm_user> "restart Bitcoin Core with -rescan if you're recovering an existing wallet from backup seed otherwise just restart this joinmarket script
14:19 < jm_user> "
14:20 < jm_user> how can i debug this?
14:20 < waxwing> first rescan should be enough
14:21 < waxwing> after that, just rerun it a few times; this might well be needed if your wallet's been in use a lot.
14:21 < jm_user> well, i have rescanned 3 times now. takes over 3h each, but still no joy.
14:21 < waxwing> it needs to import all the addresses you've used. one thing you can do is open the wallet.json and look at the numbers in the indexes.
14:22 < waxwing> again, "first rescan should be enough"
14:22 < waxwing> if the numbers are high like [(1000, 1000)...] it means it needs to import a lot of addresses
14:24 < jm_user> [[2, 295], [0, 184], [0, 172], [0, 201], [0, 273]] - seems reasonable? 
14:24 < waxwing> sure. in that case it should work after the first few times, maybe 3 or so.
14:24 < waxwing> if not, something is wrong
14:25 < jm_user> it does say that it is importing 300 addresses, but no further sensible output after that. only the rescan message. Ho can i debug further?
14:25 < waxwing> hang on, i'll grab a link
14:26 < waxwing> hmm, first sanity check: can you do rpc call "getaddressesbyaccount" on your jm wallet account name
14:28 < jm_user> standby
14:28 < waxwing> you should see a line like "rpc: getaddressesbyaccount: ['joinmarket-wallet-xxxxx'] when you run, to see the name. then try it with bitcoin-cli
14:29 < waxwing> then if that works you could also try rpc listtransactions <walletname> 1000 0 true (something like that) to sanity check if it can see transactions.
14:30 < waxwing> i'm only suggesting these sanity checks since it's the first time you've used this Core instance, maybe something is set up wrong
14:31 < jm_user> thanks for the pointers. will try this. Just realize that i need to fix some libraries after a dist-upgrade gone wrong. so this will take a little time  to get bitcoin-cli working again.
14:32 < waxwing> ok np, i'm away for now
14:50 < jm_user> bitcoin rpc interface seems fine and spewes out the expected info via bitcoin-cli
14:51 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
14:51 < jm_user> any idea what thsi means: too few addresses in [(0, 1), (1, 1), (2, 1), (3, 1), (4, 1)]
14:51 < jm_user> when running  wallet-tool.py
15:08 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Ping timeout: 250 seconds]
15:11 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket
15:13 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket
15:23 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 244 seconds]
15:38 -!- MattRK [~MattRK@ip98-168-128-134.ok.ok.cox.net] has quit [Ping timeout: 240 seconds]
15:40 -!- MattRK [~MattRK@ip98-168-128-134.ok.ok.cox.net] has joined #joinmarket
16:05 -!- akoko [~u@77-46-245-49.dynamic.isp.telekom.rs] has quit [Ping timeout: 260 seconds]
16:07 -!- akoko [~u@77-46-245-49.dynamic.isp.telekom.rs] has joined #joinmarket
16:12 -!- akoko [~u@77-46-245-49.dynamic.isp.telekom.rs] has quit [Ping timeout: 260 seconds]
16:14 -!- akoko [~u@77-46-245-49.dynamic.isp.telekom.rs] has joined #joinmarket
16:15 -!- grubles [~grubles@unaffiliated/grubles] has joined #joinmarket
16:23 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 244 seconds]
16:27 -!- grubles [~grubles@unaffiliated/grubles] has joined #joinmarket
18:59 -!- fqtw__ [~me@x5d803633.dyn.telefonica.de] has joined #joinmarket
19:03 -!- fqtw_ [~me@x5d803df9.dyn.telefonica.de] has quit [Ping timeout: 240 seconds]
19:54 < adlai> jm_user: that means you need to import more addresses, which is done by rerunning the script
20:04 -!- p15 [~p15@155.91.145.64.unassigned.bringover.net] has joined #joinmarket
22:23 -!- p15 [~p15@155.91.145.64.unassigned.bringover.net] has quit [Ping timeout: 250 seconds]
22:42 -!- mkarrer [~mkarrer@48.red-83-47-111.dynamicip.rima-tde.net] has quit []
22:46 -!- mkarrer [~mkarrer@48.red-83-47-111.dynamicip.rima-tde.net] has joined #joinmarket
22:51 -!- moli [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer]
22:51 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket