--- Day changed Tue Nov 22 2016 00:14 -!- gielbier [~michiel@unaffiliated/gielbier] has quit [Ping timeout: 245 seconds] 00:46 -!- interested [5fd3bce1@gateway/web/freenode/ip.95.211.188.225] has quit [Ping timeout: 260 seconds] 03:20 -!- Yohkii [~Yohkii___@unaffiliated/yohkii] has quit [Quit: Leaving] 04:25 -!- tergi [4a4aed8d@gateway/web/freenode/ip.74.74.237.141] has quit [Quit: Page closed] 04:51 -!- tergi [4a4aed8d@gateway/web/freenode/ip.74.74.237.141] has joined #joinmarket 05:31 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has joined #joinmarket 08:54 -!- instagibbs [~instagibb@pool-100-15-114-3.washdc.fios.verizon.net] has quit [Ping timeout: 268 seconds] 09:00 -!- instagibbs [~instagibb@pool-100-15-114-3.washdc.fios.verizon.net] has joined #joinmarket 09:56 < tergi> is it possible to move a wallet from one system to another or do you have to restore it from the seed? 09:56 < tergi> i tried copy the json over and the wallet-tool.py wont accept the password 09:57 <@waxwing> it should definitely accept the same password 09:57 <@waxwing> the password is just used to unlock the encrypted seed 10:04 < tergi> hmmmm thats strange then. 10:07 < tergi> I am moving the python stuff into a small VM. i just completed the setup and copied over the config file and the wallet file. 10:08 <@waxwing> VM is Linux presumably? i'm not sure how but perhaps windows/linux crossover could cause a problem. or non-ascii password perhaps. 10:08 <@waxwing> but just guessing. 10:09 <@waxwing> the password is just used to create an aes encryption/decryption key, once it's decrypted you get the master seed for the bip32 wallet. what exception is thrown? 10:10 < tergi> just says password not accepted 10:11 <@waxwing> eyeball the json files on the two systems, see if you can see a diff? 10:11 < tergi> Its all alpha Upper Lower and Numeric no specials 10:11 < tergi> though it is 100 characters long about 10:11 <@waxwing> yeah i remember double checking, i don't think a very long password is any issue. it's hashed iirc 10:12 < tergi> yea. ill see if i can pick out anythin gin the files they are the same size. everything needed for the wallet related to the hash etc is stored inside the json file right/ 10:12 <@waxwing> yes just the json file in wallets/.json 10:13 <@waxwing> put the wallet file in that location, but *don't* add wallets/ to the call. ie do python wallet-tool.py .json 10:14 < tergi> right 10:14 < tergi> yea they look the same 10:14 <@waxwing> yeah it's double sha2 hashed, so password length gives no issue unless it's megabytes or something :) 10:14 < tergi> without doing a diff 10:15 <@waxwing> permissions? it can be read? (but nah that wouldn't be the error) 10:16 <@waxwing> ping me if you have any progress, i'm a bit stumped atm 10:17 < tergi> n/p I will play around more tonight if i get time. 10:17 < tergi> Thanks for thinking on it 11:33 -!- instagibbs [~instagibb@pool-100-15-114-3.washdc.fios.verizon.net] has quit [Remote host closed the connection] 11:33 -!- instagibbs [~instagibb@pool-100-15-114-3.washdc.fios.verizon.net] has joined #joinmarket 11:38 -!- instagibbs [~instagibb@pool-100-15-114-3.washdc.fios.verizon.net] has quit [Ping timeout: 260 seconds] 11:43 -!- instagibbs [~instagibb@pool-100-15-114-3.washdc.fios.verizon.net] has joined #joinmarket 11:55 < JM-IRCRelay> [AlexCato] @tergi: maybe you have a different keyboard setting active? In some locales, z and y are switched, etc 12:09 < Empty2k12> How common is it that a CJ transaction is not confirming in over 24 hours? 12:14 < JM-IRCRelay> [AlexCato] very uncommon. But the current overload of the bitcoin network combined with pretty unlucky block finding (and declining hashpower) are not helping 12:14 < JM-IRCRelay> [AlexCato] we were pretty spoiled by 8min block times the last 2 weeks, because hashrate increased like mad at that time 12:16 < JM-IRCRelay> [AlexCato] so anything's possible. There's usually fewer traffic on the network on weekends, but there's some time to go for that 12:20 < Empty2k12> We just need scaling. And i'm not talking about lighning 12:37 < belcher> hopefully segwit will activate quickly, joinmarket work(ed) on segnet https://www.reddit.com/r/joinmarket/comments/4fhoc9/segwit_integration/ 12:37 < belcher> aside: segwit has been in development for more than 7 months? time flies 12:38 < belcher> looks like the agora botnet joker tried spamming me in pm today 12:38 < belcher> does he think he can make my irc client crash or something? his aims are unclear, i bet its simply "for the lulz" 12:45 < Empty2k12> Who is responsible for the Subreddit theme? I dislike that clicking on joinmarket in the banner brings you to the reddit main page. On other subreddits there are two links: the left one brings you to reddit.com while the right one brings you to reddit.com/r/subreddit 12:57 < belcher> it was made by u/chuckymcgee, i actually mentioned that to him and he said he'd fix it.. 12:57 < belcher> if you know how to do reddit themes i can give you modship so you can do it 13:04 <@waxwing> belcher: the first segnet testnet was up like Dec 2015 :) 13:04 <@waxwing> belcher: the agora script kiddie was hitting everyone today, not just nicks in our chan 13:04 < belcher> ah 13:04 < belcher> so its against agora itself rather than joinmarket 13:05 <@waxwing> smuggler said as much yesterday, yes 13:05 <@waxwing> it's not the first time 13:06 < belcher> takes me back... to nearly a decade ago of teenage script kiddies ddosing each other 13:10 <@waxwing> re segwit, it's kind of far from my mind now, but if people are inclined, they can start thinking about a 0.3 pit for segwit + p2sh. might be worth starting to write a wishlist/gathering of features to be added. 13:10 <@waxwing> 0.3 protocol, not pit :) 13:11 <@waxwing> i think the word pit appeared in my head because it would be natural to have 0.2 and 0.3 pits in parallel even more than it was natural to have 0.1 and 0.2 in parallel 13:11 <@waxwing> or just like in the reddit thread, 'swreloffer' etc 13:11 < belcher> yep it would be backwards compatible 13:11 < belcher> just add a new offer type, in fact id planned for a while to refactor the code a bit to make it easier to add new offer types since i had some other ideas for new ones 13:12 < belcher> "just" add a new offer type :D 13:12 <@waxwing> to update you on my status, this is the last thing i've done: https://github.com/AdamISZ/joinmarket-clientserver 13:13 < belcher> what is the client part of joinmarket in your mind? 13:13 <@waxwing> a couple of days ago i got an electrum tx working again in this model, the idea'd be that you could install the daemon and the client code separately, then the client code can run with any wallet/bitcoin backend in *theory* 13:13 < belcher> aah, so then the backend is on an always-on daemon 13:13 <@waxwing> the idea here is basically similar to what i discussed before, where the "server" (daemon or not) is responsible for the jm protocol as current, it needs libnacl and irc and handles that 13:13 <@waxwing> yeah 13:14 < belcher> got it 13:14 <@waxwing> and the client is responsible for bitcoin and cjpeer (currently haven't looked at maker, only taker so far) code 13:14 <@waxwing> so when i load it in electrum, it automatically recognizes that the jm secp bitcoin code isn't there, and loads the bitcoin libraries from electrum 13:14 <@waxwing> it does podle as well using electrum 13:15 <@waxwing> one hairy part was that we use bitcoin signatures in the jm messaging protocol 13:15 <@waxwing> so what happens is there's a 2-way asynchronous messaging between client and daemon, and daemon requests message signatures and verifications from the client 13:15 < belcher> right so electrum would have to ask for the password twice from the user? 13:16 <@waxwing> actually the way it works right now is the plugin only needs to ask once 13:16 <@waxwing> that also applies if there's more than one input utxo; while the password is 'set' the keystore is unlocked 13:16 < belcher> ok great 13:17 < Empty2k12> belcher: I will take a look at the reddit theme tomorrow! :) 13:17 < belcher> Empty2k12 whats your reddit username? 13:17 < belcher> my status is i was working on the tor broadcast method, now im fixing up patientsendpayment to work and be a bit better, then ill work on the "connect to a single trusted node" blockchain interface 13:17 < belcher> thinking about the "connect to a single trusted node" blockchain interface because i think a lot of people are using joinmarket on tails with blockr.io... which is almost pointless 13:18 <@waxwing> i wouldn't go as far as "almost pointless", it's distinctly suboptimal though :) 13:19 < belcher> alright sure :) 13:19 < belcher> as always, depends who you're hiding from 13:19 < Empty2k12> belcher: Same as here, Empty2k12. Can't guarantee anything though. Would I also be allowed to change other visual aspects about the theme? 13:20 < belcher> depends what you mean by visual aspects, but yes 13:21 < belcher> if you get it wrong and people complain its easy to revert :) 13:21 < belcher> tbh i dont really mind at all as long as its usable 13:22 < belcher> invited you as mod 13:22 < Empty2k12> belcher: tbh some aspects look like 2001. 13:22 < Empty2k12> belcher: Thanks. 13:22 < belcher> how awful, its current-year after all ;) 13:23 < belcher> i cant really talk, joinmarket is still a CLI program... what is that.. 1950s? 13:25 < midnightmagic> nothing wrong with cli 13:25 < midnightmagic> SO SAY I! 13:25 < belcher> beep; echo "the eagle has landed" 13:29 <@waxwing> is there a way to have multiple installation 'targets' using python setup.py / setuptools? 13:33 <@waxwing> maybe the solution is just to have more than one setup.py 13:35 -!- bsm1175321 [~mcelrath@38.121.165.30] has left #joinmarket [] 14:00 < Empty2k12> belcher: updated subreddit theme to link to reddit.com/ on left click, reddit.com/r/joinmarket on right click 14:00 < belcher> thank you! 14:00 < Empty2k12> please report if anything breaks, will try fixing that 14:00 < belcher> thats great, it matches how all other subreddits are 14:01 < Empty2k12> Maybe the subreddit theme should be on a github repo itself so we can accept user contributions for it as well 14:02 < Empty2k12> anyways i'm finally going to sleep, its way too late 14:02 < belcher> how does it actually work? is there a single css file or something? 14:02 < belcher> okay goodnight 14:02 < Empty2k12> Yeah, i split the logo 14:02 < Empty2k12> into logo and text 14:02 < Empty2k12> logo is logo, text is the subreddit link 14:03 < Empty2k12> This may or may not break something, since the text is not part of the subreddit "logo" anymore 14:04 < belcher> ty 14:04 -!- teenis [~teenislol@2a01:d0:d6f9::1] has quit [Ping timeout: 246 seconds] 14:04 < belcher> ill let you know if i notice something off 14:04 < Empty2k12> I can update it tomorrow so the css clips the text from the full logo so the logo is technically complete, even though the reddit website uses two separate images to compose the logo 14:05 < Empty2k12> Hard to explain. Bye 14:05 -!- teenis [~teenislol@2a01:d0:d6f9::1] has joined #joinmarket 15:42 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Remote host closed the connection] 16:54 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket 17:23 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Ping timeout: 245 seconds] 18:56 -!- Empty2k12_ [~smuxi@p57907245.dip0.t-ipconnect.de] has joined #joinmarket 18:56 -!- Empty2k12 [~smuxi@p579079C3.dip0.t-ipconnect.de] has quit [Ping timeout: 244 seconds] 19:08 < tergi> well. i have to say im not much of a debian expert... but seems like the password just doesnt get entered correctly. typed in manually or pasted (both using SSH with Putty on windows as the client). 19:08 < tergi> I generated a new wallet and transferred it to windows and that worked fine. 19:09 < tergi> if i paste the password into the commandline just to see it, it looks ok also 19:19 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket 19:22 < pigeons> tergi that's weird. i doubt its debian, i've always used that for joinmarket. you didnt try the same wallet though on windows you tried a different one so maybe you have the wrong password 19:23 < tergi> No, its correct. I have one working wallet i setup on my windows PC. i decided now that im happy with running YG, that i want to move it into debian to try and isolate it from my main PC a bit. i setup Deb, and installed the JM software 19:23 < tergi> copied the wallet file over and the config file 19:23 < tergi> should work... 19:25 < pigeons> so wallet-tool.py says wrong password? 19:25 < tergi> Yes 19:27 < tergi> i thought maybe it was some odd implementation difference in the libs maybe between os's but the linux to windows direction seems to work ok 19:27 < pigeons> the wallet is in the "wallets" directory? 19:27 < tergi> Yes 19:28 < pigeons> look in the wallet file in a text editor 19:28 < tergi> I did, they looked identical 19:29 < pigeons> well then that leaves putty 19:29 < tergi> yea... but im not sure what it would be doing wrong, when i paste the password into a plain text editor nano or on the commandline directly its correct 19:29 < pigeons> what is the exact error you are getting 19:30 < tergi> Just the notification from the wallet-tool.py that the password didnt work and it reprompts i dont know exactly what the wording is. 19:30 < pigeons> well paste it 19:32 < tergi> Enter wallet decryption passphrase: 19:32 < tergi> Incorrect password 19:33 < tergi> Enter wallet decryption passphrase: 19:35 < pigeons> give the whole command you are running 19:35 < pigeons> the wallet-tool command of course, not a payment :) 19:35 < pigeons> and what directory you are running it from 19:36 < tergi> ~/joinmarket-0.2.2$ python wallet-tool.py wallet.json 19:37 < tergi> :~/joinmarket-0.2.2$ ls wallets 19:37 < tergi> wallet.json 19:37 < tergi> running as regular user 19:37 < pigeons> do this: python wallet-tool.py wallet 19:38 < tergi> IOError: wallet file not found 19:39 < pigeons> i wonder if a /r/n or something could mess it up 19:40 < tergi> Yea, i am not sure really. but i wouldnt think so, since my test wallet worked ok, 19:41 < tergi> and i tried typing in my password manually 19:41 < pigeons> your test wallet was also moved from windows? 19:42 < tergi> No. that was made on debian and moved to windows to see if the other direction worked 19:42 < pigeons> so then you dont know 19:43 < pigeons> there is a program in debian repo called "dos2unix" you can use or you can manually remove any carriage return or use sed 19:43 < tergi> i dont see how a /r/n would get in the mix 19:43 < pigeons> by moving it from window 19:43 < pigeons> s 19:43 < pigeons> it has one when you make it on windows 19:43 < tergi> you mean inside the wallet file? 19:43 < pigeons> yes 19:44 < tergi> hmm ok i would have figured the json file format would have dealt with that with the delimiters 19:44 < pigeons> use dos2unix or sed or an editor to remove any carriage returns from wallet.json 19:44 < tergi> ok 19:44 < pigeons> might as well try right 19:45 < tergi> It did not seem to make a difference 19:45 < pigeons> and at the "file format" level, json is a text file, which will have CRLF on windows and LF on unix 19:45 < tergi> used dos2unix 19:46 < pigeons> ok even though they look identical try copying the wallet over again 19:46 < tergi> ill make a new wallet on windows and move it over and see if that works. maybe it is my password its 100 characters long. I know waxwing said it shouldnt matter but 19:46 < tergi> at this point im thinking its the only thing left that it could be. 19:47 < pigeons> i would try copying again too 19:47 < tergi> i have already done that 19:47 < tergi> tried binary and ascii xfer over ssh 19:47 < tergi> copied the wallet text and pasted it into a file 19:48 < tergi> doesnt seem to matter 19:49 < pigeons> at least it works on the windows side, so even though its definately weird and shouldnt happen, you can at least sweep to a new wallet on debian (once you test that wallet!) 19:49 < tergi> yup, its the long password 19:49 < pigeons> interesting, yeah waxwing will probably be interested 19:50 < tergi> indeed 19:50 < tergi> probably should open an issue. ugh, what a job to list out all these steps 19:50 < pigeons> and we know it isnt a clipboard buffer because you somehow typed 100 characters in correctly manually too 19:50 < tergi> i did it 3 times manually 19:51 < tergi> not saying i couldnt have screwed it up 3 times obviously 19:51 < pigeons> lol i couldnt do it once manually 19:51 < pigeons> but i bet you did it right 19:57 < tergi> interestingly, if i make a test wallet with a 100 character password same as the other wallet on deb, it works . 19:57 < tergi> so im not sure whats going on 19:57 < tergi> nothing makes sense 19:59 < tergi> huh, but when moved back to windows it fails to accept the same password 19:59 < tergi> interesting indeedd 20:02 < pigeons> try a different ssh client for fun 20:07 < tergi> hmm what other one is there haha 20:08 < pigeons> i had to use windows recently and if you install git for windows you get a great bash shell and ssh terminal that is much better than putty 20:09 < pigeons> i hear openssh is native from ms on very recent windows 20:10 < tergi> oh? yea i know bash is supposed to be coming but i dont know if its released. 20:11 < tergi> i used smartty and it didnt work either 20:11 < tergi> oh well. im tossing on the towel for the night. issue is open for tracking and such so hopefully we can get to the bottom of this eventually. 20:12 < tergi> i might switch to this smartty client though. Putty is nice but this has the file transfer stuff built in, nice one window tabbed interface... 20:12 < tergi> easier to read 20:13 < pigeons> no really, try git for windows for your ssh needs 20:20 < tergi> alright ill check into it 20:49 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has quit [Quit: Leaving.] 21:45 < Empty2k12_> I have a CJ transaction stuck for over 72 hours now. What would happen when nodes delete the TX from their Mempool and the TX eventually never confirms? Did I just loose my 0.1 BTC in value? 21:46 < pigeons> no you didnt lose it 21:47 < Empty2k12_> Because I have 0.1 BTC in inputs in the transaction? 21:49 < pigeons> the utxo of yours in that transaction is still valid to spend 21:49 < pigeons> yes 21:50 < pigeons> I don't know the best way to access it with joinmarket. you can get the wallet to show you the private key in the worst case but i would wait for someone more knowledgable, 21:50 < pigeons> but i do know you did NOT lose it 21:51 < pigeons> there are some relatively recent changes to joinmarket where its possible thaat input is blacklisted and jm makers wont include it in a join 21:51 < pigeons> i havent followed the exact details but you didnt lose it 21:51 < Empty2k12_> Thats good! Thanks. I know that I either need to spend with from another wallet or resync the blockchain for my coins to reappear. I will wait some more hours and try that then 21:52 < pigeons> yep. by "resync the blockchain" its more forcing your wallet to forget that transaction 21:54 < Empty2k12_> Yeah. Thank you very much. I guess it made sense that I would have my output txvalue(- CJ profit) as a input. 21:55 < pigeons> the same output is still available, there is no cj profit for anyone if it didnt confirm 21:55 < pigeons> same input whatever 21:58 < Empty2k12_> Yeah. Thanks! 23:40 -!- lnostdal [~lnostdal@62.90-149-73.nextgentel.com] has quit [Read error: Connection reset by peer] 23:41 -!- lnostdal [~lnostdal@62.90-149-73.nextgentel.com] has joined #joinmarket