--- Day changed Mon Sep 03 2018 01:33 -!- Zenton [~user@unaffiliated/vicenteh] has joined #c-lightning 01:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 245 seconds] 02:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 02:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 03:25 -!- grubles_ [~grubles@gateway/tor-sasl/grubles] has joined #c-lightning 03:27 -!- grubles [~grubles@gateway/tor-sasl/grubles] has quit [Ping timeout: 250 seconds] 04:21 -!- bitonic-cjp [~bitonic-c@2001:981:9573:1:14ed:fcff:fe73:cf5b] has joined #c-lightning 05:29 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 05:30 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 05:38 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 06:02 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 06:30 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 06:31 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 06:34 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 08:10 -!- bitonic-cjp [~bitonic-c@2001:981:9573:1:14ed:fcff:fe73:cf5b] has quit [Quit: Leaving] 08:28 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 08:36 -!- drgrid [~TheCharla@109.236.87.57] has quit [Read error: Connection reset by peer] 08:38 -!- drgrid [~TheCharla@109.236.87.57] has joined #c-lightning 08:48 -!- maitra [~voltron@59.153.120.164] has joined #c-lightning 09:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 10:21 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 10:26 -!- daouzo23 [~daouzo23@178.115.128.7.wireless.dyn.drei.com] has joined #c-lightning 10:35 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 272 seconds] 10:38 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 252 seconds] 10:39 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 11:12 -!- grubles_ is now known as grubles 11:14 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 11:17 -!- maitra [~voltron@59.153.120.164] has quit [Quit: WeeChat 1.9.1] 12:05 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 12:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 12:38 -!- daouzo23_ [~daouzo23@178.115.128.7.wireless.dyn.drei.com] has joined #c-lightning 12:41 -!- daouzo23 [~daouzo23@178.115.128.7.wireless.dyn.drei.com] has quit [Ping timeout: 240 seconds] 12:48 -!- Zenton [~user@unaffiliated/vicenteh] has joined #c-lightning 13:00 -!- polydin [~delphi@ip-69-80-248-129.wireless.static.fire2wire.com] has joined #c-lightning 13:05 < shesek> If anyone wants to give Spark a try, I published a bunch of public regtest instances you can use at https://www.reddit.com/r/Bitcoin/comments/9ckw47/introducing_spark_a_minimalistic_lightning/e5c2cyu/ 13:19 -!- daouzo235__ [~daouzo23@178.115.128.7.wireless.dyn.drei.com] has joined #c-lightning 13:23 -!- daouzo23_ [~daouzo23@178.115.128.7.wireless.dyn.drei.com] has quit [Ping timeout: 246 seconds] 13:25 -!- grubles [~grubles@gateway/tor-sasl/grubles] has joined #c-lightning 13:58 < molz> shesek, im so confused with those regtest instances, do you have a guide for testnet? 14:02 -!- polydin [~delphi@ip-69-80-248-129.wireless.static.fire2wire.com] has quit [Ping timeout: 245 seconds] 14:15 < shesek> molz, do you have a bitcoind node or a c-lightning node? 14:19 < molz> yes and yes 14:20 < molz> oh i guess grubles has his guide here: https://medium.com/@notgrubles/spark-a-new-gui-for-c-lightning-2cf2f024500c 14:20 < shesek> install nodejs (https://nodejs.org/en/download/package-manager/), then "$ sudo npm install -g spark-wallet" and "$ spark-wallet -l /path/to/clightning" (or just "spark-wallet" if its at the default location of ~/.lightning) 14:21 < shesek> or, if you prefer docker, $ docker run -v ~/.spark-docker:/data -p 9737:9737 -v ~/.lightning:/etc/lightning shesek/spark-wallet --login molz:superSecretPass 14:21 < molz> it seems complicated, i wish more apps to be made with less complication 14:22 < molz> oh i have no clue about docker and from the complaints i've seen i prefer not to use docker 14:22 < shesek> are you using linux? which distro? 14:27 < molz> ubuntu 14 14:27 < molz> this can be used on an android, correct? 14:28 < shesek> yes, there's an android app, but it needs to connect to a spark server that you'll need to setup first 14:32 < molz> hm ok 14:32 < molz> shesek, thanks i'll look at this later 14:32 < shesek> your ubuntu is quite old and has an outdated version of nodejs in its repositories. you can install a newer version of nodejs by following the instructions at https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions 14:32 < molz> hm ok 14:33 < shesek> but I would suggest going the docker route on ubuntu 14 14:33 < molz> my ubuntu is on a vps server... i noticed i had trouble with nodejs because someone else also asked me to check out their app 14:34 < molz> wait, actually i have ubuntu 16 14:37 < shesek> ah, that's better, but still has an old version of nodejs :-( updating it to a recent version with the instructions from that link should be pretty straightforward, though 14:37 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 14:38 < shesek> you could also upgrade using the "n" package: $ sudo npm install -g n && sudo n 8.11.3 14:38 < molz> shesek, are you familiar with WSL on windows? 14:39 < molz> i have WSL and it's Ubuntu 18, maybe i can try it there too 14:39 < molz> but in the past i tried to run bitcoind and c-lightning node on WSL, didn't work out 14:39 < shesek> on ubuntu 18 you can just "apt install nodejs" to get a recent version 14:40 < molz> ok 14:40 < shesek> but if you already have a running bitcoind node, probably best to use that than re-syncing... 14:40 < molz> ok 14:40 < shesek> and no, I'm not familiar with WSL, haven't been using windows for a long time 14:44 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 246 seconds] 14:46 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 15:12 -!- blockchainbilly [2f377206@gateway/web/freenode/ip.47.55.114.6] has joined #c-lightning 15:12 < blockchainbilly> I updated from c-lightning 0.5.x to 0.6.1rc1 tonight. I wasn't sure how to do it properly so I just made a new folder and cloned the c-lightning repo there and rebuilt it. When I run lightningd from this folder it still has access to the history from the older version (listfunds and listpayments). I'm just wondering where is this information stored/how is it getting it from a separate folder? 15:16 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 15:21 < blockchainbilly> Also worth asking, what is the proper way to upgrade through git? 15:21 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds] 15:22 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 15:23 < blockchainbilly> Disregard the first question please, I found out using listconfigs that the lightning-dir is stored separately. 15:23 < blockchainbilly> Is this the best place to come and ask c-lightning related questions? 15:24 < shesek> blockchainbilly, git pull && ./configure && make 15:25 < blockchainbilly> okay thanks, that is what I tried and it didn't work. does it have to be on one line? or any other requirements before doing so? 15:25 < shesek> and yes, the lightning data dir is separate and defaults to ~/.lightning. you can change that by running lightningd with --lightning-dir 15:25 < shesek> it doesn't have to be one line, and there shouldn't be any other requirements 15:26 < shesek> how did it not work? 15:27 < blockchainbilly> maybe i needed to run as sudo, let me retry 15:28 < blockchainbilly> sorry, I am still pretty green when it comes to Linux 15:28 < shesek> sudo shouldn't be required 15:29 < shesek> did you ./configure? iirc it became mandatory somewhere between v0.5 and v0.6 15:29 < blockchainbilly> Yes I did 15:29 < blockchainbilly> The error was: 15:29 < blockchainbilly> tools/generate-wire.py --header connectd/gen_connect_wire.h connect_wire_type < connectd/connect_wire.csv > connectd/gen_connect_wire.h /bin/sh: 1: cannot create connectd/gen_connect_wire.h: Permission denied connectd/Makefile:78: recipe for target 'connectd/gen_connect_wire.h' failed make: *** [connectd/gen_connect_wire.h] Error 2 rm external/libwally-core/src/secp256k1/libsecp256k1.la 15:30 < blockchainbilly> sudo took care of it 15:32 < blockchainbilly> I was running on mainnet, and now I want to stop my bitcoind / c-lightning and restart them on testnet. Is this as simple as stopping them and restartin with --network=testnet or do I need to do something differently? Last time I tried getting c-lightning working on testnet I think I couldn't because I had originally set it up for mainnet 15:37 < molz> blockchainbilly, testnet is like mainnet, how did you get your mainnet node to work to begin with? 15:38 < blockchainbilly> I followed a guide for setting up a channel to buy from the Blockstream store back in February. I'll try to find the link 15:39 < molz> oh that's a bad way to do it 15:39 < molz> you learned nothing 15:40 < blockchainbilly> haha might not be the best way, but I certainly learned along the way. 15:41 < blockchainbilly> e.g. I could probably set up a channel now on my own much easier. 15:42 < blockchainbilly> I think I did it very similar to how I just did it now (compile from source, run bitcoind on mainnet, then run lightningd on mainet) 15:42 < molz> blockchainbilly, here's the install guide: https://github.com/ElementsProject/lightning/blob/master/doc/INSTALL.md 15:42 < shesek> blockchainbilly, you'll need to start lightningd with "--network testnet" and with a different "--lightning-dir" 15:43 < shesek> (i.e. not ~/.lightning, which is already on mainnet) 15:43 < molz> c-lightning is so easy to set up, im a windows user and i can do this 15:43 < blockchainbilly> ah okay, I think the different --lightning-dir is the problem 15:43 < blockchainbilly> @molz I agree it is easy, I installed c-lightning no problem. 15:43 < blockchainbilly> But didn't realize I had to use a different --lightning-dir to run on testnet 15:44 < molz> i don't 15:44 < molz> i just use a different user 15:44 < blockchainbilly> Ah I see 15:44 < shesek> blockchainbilly, is it possible you initially installed c-lightning as root? make should not normally require sudo 15:44 < molz> shesek, i install c-lightning at root ) 15:44 < shesek> if you did, run "chmod -R /path/to/clightning-git/" to reset the ownership back to you 15:45 < molz> easy and faster to update 15:45 < molz> for all users 15:45 < blockchainbilly> Probably yeah, I have a habit of using sudo for a lot of things when I can't get them working initially lol 15:45 < shesek> after that, you should be able to update c-lightning without sudo 15:45 < shesek> hrm, sorry, chown and not chmod 15:45 < shesek> "chown -R /path/to/lightning-git" 15:48 < blockchainbilly> Okay I did that thanks. It still shows a lot of the files as root, but the folders as my user 15:59 < shesek> you might still be seeing "root" as the group. you can "chmod -R : /path/to/clightning-git" to reset both the owner and the group 16:06 < blockchainbilly> ah okay, great. thanks a lot! just syncing up to testnet now, will report back if I have any questions. Hoping to give Spark a try 16:11 -!- akrmn [~akrmn@109.red-81-36-231.dynamicip.rima-tde.net] has joined #c-lightning 16:46 < shesek> you're welcome. good luck. would love to hear your thoughts after giving it a spin :) 17:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 17:24 -!- deusexbeer [~deusexbee@080-250-077-052-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 17:26 < blockchainbilly> Will ping you if/when I get it up and running. Started c-lightning on testnet, passed in empty directory that I just created as lightning-dir, and it created the files in there, gave this message: 17:26 < blockchainbilly> 2018-09-04T00:19:30.974Z lightningd(11557): Creating database 2018-09-04T00:19:31.120Z lightning_hsmd(11565): HSM: created new hsm_secret file 2018-09-04T00:19:31.509Z lightningd(11557): Unable to estimate CONSERVATIVE/2 fee 2018-09-04T00:19:31.521Z lightningd(11557): Unable to estimate ECONOMICAL/4 fee 2018-09-04T00:19:31.626Z lightningd(11557): Unable to estimate ECONOMICAL/100 fee 17:26 < blockchainbilly> Followed by "Server started with public key ..." and now it just keeps repeating the 3 lines about unable to estimate fee 17:27 < blockchainbilly> It's only been going like that for ~3 minutes so I'm going to just let it go for now in case it's syncing or something? But does this seem like a familiar error/problem to anyone? 17:30 < blockchainbilly> Ok, disregard that question too, I forgot to run with debug logs. It is syncing. 19:46 -!- daouzo235__ [~daouzo23@178.115.128.7.wireless.dyn.drei.com] has quit [Ping timeout: 272 seconds] 21:03 -!- maitra [~voltron@59.153.120.164] has joined #c-lightning 21:06 < maitra> Is it possible to run c-lightining with bitcoind regtest mode?? 21:31 -!- polydin [~delphi@ip-69-80-248-129.wireless.static.fire2wire.com] has joined #c-lightning 21:38 < molz> yes 21:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 21:49 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 21:52 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 252 seconds] 22:08 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.1] 22:11 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 23:03 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection]