--- Day changed Tue Jan 23 2018
00:04 -!- CubicEarths [~cubiceart@2600:1012:b013:3519:91b2:f398:a78e:cf23] has quit [Remote host closed the connection]     
00:08 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ogwamnltuwbbzzoq] has quit [Quit: Connection closed for inactivity]     
00:10 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-vrbjgzskduprsivf] has joined #c-lightning     
01:26 -!- plankers [~plank@c-73-2-4-197.hsd1.ca.comcast.net] has quit [Ping timeout: 268 seconds]     
02:33 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
02:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 265 seconds]     
03:22 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vNwR3
03:22 -githubby:#c-lightning- lightning/master 9408195 ZmnSCPxj: lightning-cli: Add support for null argument.
04:06 -githubby:#c-lightning- [lightning] jjnaude opened pull request #736: Minor doc fix (master...master) https://git.io/vNwuF
04:28 < DrOlmer> I keep getting the following on the logs: "lightningd(22835): Broadcasting tx {TXHEX}: 26 error code: -26  error message: 16: bad-txns-vout-empty"
04:28 < DrOlmer> anyone bumped into it?
04:33 -githubby:#c-lightning- [lightning] cdecker closed pull request #631: Remove unused help text field from struct json_command. Use consistent wording. (master...unused-help-test-in-struct-json_command) https://git.io/vN4o5
04:33 -githubby:#c-lightning- [lightning] cdecker closed pull request #729: Allocate hex buffer on heap since it can be very large. (master...crash-getlog) https://git.io/vNV20
04:58 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-vrbjgzskduprsivf] has quit [Quit: Connection closed for inactivity]     
05:32 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-geiowgbexzgypmle] has joined #c-lightning     
05:38 -!- buZz [~buzz@unaffiliated/buzz] has joined #c-lightning     
05:38 < buZz> how do i use c-lightning without bitcoind/bitcoin-cli on the same machine?
06:08 < buZz> would be really nice if lightningd could just do RPC calls by itself without external assistance :P this is pretty childish
06:46 < DrOlmer> buZz: maybe you could do SSH tunneling but could be awkward and not sure if the speed will be an issue (probably not)
06:46 < buZz> RPC already uses networking, there's no need to tunnel anything
06:47 < DrOlmer> ah ye right :P
07:00 -githubby:#c-lightning- [lightning] cdecker opened pull request #740: Purge channels from the DB after they have been irrevocably committed (master...forget-channels) https://git.io/vNwQW
07:09 -!- xocite [local@gateway/vpn/privateinternetaccess/xocite] has joined #c-lightning     
07:10 -githubby:#c-lightning- [lightning] cdecker closed pull request #716: Build fixes and increased cross-platform compatibility (master...building) https://git.io/vNaVj
07:11 < xocite> All my transactions have CHANNELD_AWAITING_LOCKIN.  Is this expected?  The transaction already has a lot of confirmations. 
07:11 -githubby:#c-lightning- [lightning] practicalswift opened pull request #741: Warn instead of crash when extract_feerate(...) fails (master...warn-instead-of-fail-on-extract_feerate-failure) https://git.io/vNw76
07:20 -!- CubicEarths [~cubiceart@201.191.199.160] has joined #c-lightning     
07:22 -!- CubicEarths [~cubiceart@201.191.199.160] has quit [Remote host closed the connection]     
07:51 -!- lugg [uid274294@gateway/web/irccloud.com/x-wrtcwfvtkkhshzdu] has joined #c-lightning     
07:52 < lugg> hi, running into an issue with getroute... it's returning "Could not find a route" and I'm wondering if there's any way to know why
08:08 -!- xabbix [4fb1a15d@gateway/web/freenode/ip.79.177.161.93] has joined #c-lightning     
08:09 < xabbix> Trying to pay for items on blockstream's store, connected to a peer and have a channel open with confirmed funds. When trying to pay, I'm getting this error message: htlc 22 failed from 0th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE) - Any ideas what I'm doing wrong? `listpeers` shows a peer with "connected": true and "state": "CHANNELD_NORMAL" and funds looks ok and sufficient
08:10 < lugg> xabbix: I'm doing the same
08:11 < lugg> and I'm having a problem finding a route, heh
08:11 < lugg> early days, support is thin
08:11 < xabbix> lugg: I have 2 routes available to the store..
08:11 < lugg> how can you tell you have the routes? did the getroute command work for you?
08:12 < lugg> my invoice expires in 6 mins, lol
08:12 < xabbix> lugg: you can use the getroute command to find out if you have routes to their store
08:13 < xabbix> something like getroute 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 200000000 0
08:13 < lugg> ah.     
08:13 < lugg> Yeah I get: adam@Random:~/lightning/cli$ ./lightning-cli getroute 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 180000000 0
08:13 < lugg> "Could not find a route"
08:13 < lugg> :(     
08:13 < xabbix> :(     
08:14 < buZz> same here
08:14 < buZz> does it need open channels?
08:14 < lugg> listpeers shows a peer with "state" : "CHANNELD_AWAITING_LOCKIN", instead of the "gossip" it said earlier
08:14 < lugg> I have no idea what that means
08:14 < buZz> i have peers that are gossipping, but i think it needs channels aswell
08:14 < lugg> buZz: afaik it requires an open channel and a route
08:14 < buZz> ah right
08:15 < lugg> well, the open channel just means that you have funds on the network that can be spent (I think)
08:15 < lugg> the route enables the actual payment mechanism
08:15 < lugg> and that's where I'm flopping
08:15 < lugg> I'm trying to debug but the getlog command doesn't return anything (despite launching with the --log-level=debug)
08:16 < lugg> it's all good, though -- a true learning experience
08:18 < lugg> if I close a channel, will I get the funds back immediately?
08:25 -githubby:#c-lightning- [lightning] practicalswift opened pull request #743: Adjust log level for fee rate warnings (master...update_feerates-log-level) https://git.io/vNreB
08:30 -!- CubicEarths [~cubiceart@201.191.199.160] has joined #c-lightning     
08:43 -!- CubicEarths [~cubiceart@201.191.199.160] has quit []     
08:46 -!- c-tester [ac618a6a@gateway/web/freenode/ip.172.97.138.106] has joined #c-lightning     
08:47 < c-tester> hello, how to start c-lightning on main net?  I have bitcoind running and synced...
08:47 < c-tester> also, what network ports should be opened 
08:56 < lugg> c-tester: you have c-lightning downloaded and compiled, right?
08:56 < lugg> from there it's just: lightningd/lightningd --network=bitcoin --log-level=debug
08:59 < c-tester> thx lug.. need to download and compile
09:02 < lugg> c-tester: the (relatively simple) steps are on https://github.com/ElementsProject/lightning
09:03 < c-tester> excellent, thx
09:06 < buZz> is it normal that fundchannel takes a while?
09:08 < buZz> ah there we go
09:13 < c-tester> buzz, are you on main net?
09:14 < buZz> yeah
09:14 < buZz> currently on "CHANNELD_AWAITING_LOCKIN" which i guess means wait :P
09:14 < c-tester> cool, ill be there soon also..
09:14 < lugg> buZz: yeah from what I've learned, it means the funding tx hasn't confirmed yet
09:15 -!- jb55 [~jb55@d108-172-210-7.bchsia.telus.net] has joined #c-lightning     
09:15 < lugg> buZz: you can see the funding tx right there in the listpeers command, and then check it out to see its status
09:15 < lugg> mine had a tiny fee so I guess I'll be waiting a while, heh
09:15 < buZz> ahhh indeed, ty
09:15 < buZz> 70sat/b for me, should be fine
09:15 < buZz> 1conf already
09:15 < lugg> I think I was at 50
09:16 < buZz> mempool kinda suggests even ~25sat/b should work atm
09:16 < buZz> just could take a couple blocks
09:16 < lugg> I've been waiting for a couple of hours, but it's no big deal
09:16 < buZz> :)     
09:17 < buZz> fancy that it uses bech32 internally
09:17 < lugg> yeah
09:17 < lugg> blockchain.info doesn't know what to do with it :P
09:19 < buZz> ^_^     
09:20 < c-tester> what are the network port requirements for c-lightning
09:21 < buZz> eh dno, i'm behind double NAT with no ports open
09:21 < buZz> still works
09:21 < c-tester> ok     
09:22 < lugg> I think you can open 9735 if you want to ensure connectivity
09:28 < c-tester> got it.
09:37 < grubles> what is the correct uri for c-lightning? i get "id pubkey@ip:port" not valid
09:38 < grubles> for connecting to a peer, i mean
09:38 < xocite> Try id pubkey ip 
09:38 < grubles> that is not valid either
09:39 < xocite> What's the invocation and error message?  
09:39 < xocite> for me it's lightning-cli connect pubkey ip
09:40 < grubles> lightning-cli connect pubkey@ip
09:40 < grubles> or     
09:40 < grubles> lightning-cli connect pubkey@ip:port
09:40 < xocite> You don't need the '@'.  Just have a space between pubkey and ip
09:40 < grubles> yeah ok i was wondering if it was that
09:40 < grubles> i thought i saw someone have a similar issue
09:40 < grubles> ok thanks
09:40 < xocite> cool no problem :)
09:41 < grubles> wait that doesn't work either
09:41 < grubles> does it require the port?
09:42 < c-tester> ok so I launched  lightningd/lightningd --network=bitcoin --log-level=debug and have a screen full of "adding block",  seems to have stopped scrolling, will I get back to my command prompt?
09:42 < xocite> only if it's not 9735
09:42 < xocite> There's not a command prompt in lightningd, use lightning-cli
09:43 < c-tester> ok, but should I control-C to get back to my ubuntu prompt
09:43 < xocite> What are you trying to do?
09:44 < xocite> If you want to stop it use `lightning-cli stop`
09:44 < c-tester> I want to run c-lightning open and fund a channel
09:44 < lugg> c-tester: you launched it in your active terminal
09:44 < c-tester> I guess i did
09:44 < lugg> if you close the terminal or ctrl-c, you'll kill the process
09:44 < lugg> you can leave it alone, or close it and maybe run it behind screen
09:45 < c-tester> right.. i think Ill install screen and run it in another terminal?
09:45 < lugg> that's what I do :)
09:45 < lugg> sudo apt install screen
09:45 < lugg> then screen... then enter... and then you can have as many virtual/background screens as you want
09:45 < c-tester> unless it can run as a daemon?
09:45 < lugg> do you know how to switch between them?
09:45 < lugg> not sure about the daemon, hmm
09:45 < c-tester> yeah have that written down somewhere...
09:46 < lugg> Ctrl-a c to make a new screen ... Ctrl-a n to move to the next screen (cycling through them)
09:47 < c-tester> ok, thx...  
09:47 < c-tester> now the blocks are being added periodically, these are part of lightning sidechain?
09:47 < lugg> when I run lightningd --help I don't see any option for a daemon
09:48 < lugg> I think they are, yeah
09:48 < lugg> I just found a problem, ugh
09:48 < lugg> lightning_gossipd(2093): TRACE: Failed connected out for 035f1498c929d4cefba4701ae36a554691f526ff60b1766badd5a49b3c8b68e1d8, will try again
09:48 < lugg> that's my peer with my open channel
09:49 -!- xocite [local@gateway/vpn/privateinternetaccess/xocite] has quit [Ping timeout: 246 seconds]     
09:49 < lugg> when I listpeers, now I see "connected: false" :(
09:51 -!- xocite [local@gateway/vpn/privateinternetaccess/xocite] has joined #c-lightning     
09:51 -!- xocite [local@gateway/vpn/privateinternetaccess/xocite] has quit [Client Quit]     
09:58 < c-tester> when i do a listpeers shows blank
09:58 < c-tester> { "peers" :  	[  ] }
09:59 < c-tester> what is that url that shows main net nodes?  
10:00 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has left #c-lightning []     
10:00 < grubles> hrm so lightning-cli connect pubkey ip does not work either. 
10:09 < buZz> grubles: connect key ip port
10:09 < buZz> so : lightning-cli connect 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 104.198.32.198 9735
10:12 < grubles> ahh ok so the port is required
10:12 < grubles> buZz, thanks!
10:13 < buZz> \o yw
10:14 < c-tester> grubles, you were able to fund your lightning instance?
10:15 < grubles> i'm about to try :p
10:15 < c-tester> ok. and BuZz, where did you find that node /ip to connect to?
10:15 < grubles> that's the blockstream store node
10:16 < c-tester> I dont see it listed on their site
10:17 < grubles> i don't think it is but cdecker tweeted it 
10:18 < c-tester> ok I see he did.. https://twitter.com/Snyke/status/953428932866560001
10:18 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-geiowgbexzgypmle] has quit [Quit: Connection closed for inactivity]     
10:18 < buZz> c-tester: i used https://lnmainnet.gaben.win/
10:19 < c-tester> excellent thanks.
10:24 -!- jb55 [~jb55@d108-172-210-7.bchsia.telus.net] has quit [Ping timeout: 240 seconds]     
10:25 < c-tester> so if we run cli/lightning-cli getinfo it returns our public key... shouldn't that be visible on that gaben.win site?
10:29 < grubles> it is i think
10:34 < c-tester> { "id" : "0201c0a1c3fdbefdd72fba461df6500f7ed773f3d9d63f794634c973c70dbc096b", "port" : 9735, "address" :  	[  ], "version" : "v0.5.2-2016-11-21-1659-gfeb7340", "blockheight" : 505751, "network" : "bitcoin" }
10:35 < c-tester> thats what mine looks like... not sure why the address field is empty
10:35 < grubles> because you didn't open up 9735 i think
10:36 < c-tester> yeah it's open.
10:42 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has joined #c-lightning     
10:42 < c-tester> wonder if 8333 needs to open also.
10:47 < buZz> my address is empty aswell
10:51 -githubby:#c-lightning- [lightning] jjnaude closed pull request #736: Minor doc fix (master...master) https://git.io/vNwuF
10:51 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has joined #c-lightning     
10:58 < c-tester> ok maybe thats normal then... perhaps that site is not updated in real time
11:07 -!- xabbix [4fb1a15d@gateway/web/freenode/ip.79.177.161.93] has quit [Quit: Page closed]     
11:09 < jojeyh> on running lightningd i get an error saying bitcoin-cli can't get RPC credentials, anybody know how to fix?
11:10 < jojeyh> No authentication cookie, which I assume is locked when running bitcoind
11:14 < buZz> mkdir .bitcoin
11:14 < buZz> scp bitcoin:.bitcoin/bitcoin.conf .bitcoin
11:14 < buZz> :P     
11:15 < buZz> also add a rpcconnect=bitcoin.yourlan line to the bitcoin.conf
11:15 < buZz> and dont forget starting lightningd with -network bitcoin ^_^
11:20 < c-tester> how are nodes named,  is there a conf file entry?
11:23 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #c-lightning     
11:28 < grubles> ok so when i go to fund a channel with fundchannel, is there a way to specify the transaction fee?
11:28 -!- pocket [4da2683e@gateway/web/freenode/ip.77.162.104.62] has joined #c-lightning     
11:31 < jojeyh> ah danke buZz
11:31 < buZz> yw     
11:32 < buZz> grubles: you do a bitcoin-cli settxfee prior
11:32 < buZz> maybe settxfee 0.001  (its per 1000 bytes)
11:33 < grubles> ah ok
11:33 < grubles> thx     
11:34 < jojeyh> wat you can choose litecoin as network
11:34 < jojeyh> dope
11:34 < buZz> yeah LTC has segwit aswell
11:35 < buZz> couple other coins aswell, so i guess there will be more options in the future :)
11:35 < jojeyh> that would be awesome if the app is just used for almost all chains
11:35 < buZz> in theory you could do LTC payments with only a BTC LN node
11:35 < jojeyh> in theory lol
11:36 < buZz> heh well, i havent seen it used in practise outside of lab ;)
11:36 < jojeyh> how can a person contribute who has mid-level software skills?
11:36 < buZz> by writing mid-level code? :D
11:36 < jojeyh> hahaha
11:36 < jojeyh> i deserved that
11:36 < jojeyh> lol     
11:37 < buZz> https://github.com/ElementsProject/lightning/issues 
11:37 < jojeyh> back to work i guess
11:37 < jojeyh> i'll figure this shit out
11:37 < buZz> maybe start with that? just read through, try to find bits to help
11:37 < jojeyh> ok i will go through the issues 
11:37 < jojeyh> it will probably be a good amount of time before i can really contribute
11:37 < buZz> takes a while to 'sync in' to any FOSS dev team
11:37 < jojeyh> yea totally
11:38 < buZz> yeah maybe an idea to just consume the posts to /issues for a week or 2-4
11:38 < jojeyh> cool thanks will do
11:38 < buZz> \o     
11:41 < c-tester> Should I bother to fund my lightningd before my node is visible on the https://lnmainnet.gaben.win/
11:42 < buZz> mine still hasnt appeared , but i dont have port forwarded to the node, so maybe i'm not counted
11:47 < grubles> buZz, hrm i think settxfee is deprecated?
11:47 < pocket> Where is the wallet data saved?
11:48 < pocket> c-tester do you have a channel open?
11:51 < buZz> grubles: works for me :P i agree finer control would be nicer
11:58 < c-tester> pocket.. no channel open yet.
11:58 < c-tester> i have both 9735 and 8333 ports open.
12:01 < c-tester> ok i have run "connect" to 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 104.198.32.198 9735
12:02 < c-tester> running cli/lightning-cli listchannels show 6 active channel ids
12:09 < c-tester> just ready this is how you set alias and color during launch.   lightningd --rgb=ff00ff --alias=myaliasname
12:09 < pocket> Maybe you have to connect to a channel but im
12:10 < pocket> not sure
12:13 < c-tester> listchannels now shows huge list of active channels
12:14 < tweaks> c-tester: that site uses the lnd network graph.. and the lnd describegraph returns the edges and vertices of the payment channel graph
12:16 < c-tester> tweaks, are you saying there is another graph for c-lightning?  thought all the clients comply with bolt protocols
12:16 < tweaks> im saying it looks like you need an open channel
12:20 < buZz> i have a channel open but i dont see myself
12:24 < c-tester> i did connect to 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 104.198.32.198 9735
12:24 < c-tester> that is blockstreams store
12:24 < buZz> you should see that in getpeers
12:24 < grubles> you have to connect to a peer, then open a channel 
12:24 < buZz> and nodes with a channel open will show the channel under it
12:24 < buZz> (channel to you, that is)
12:25 < c-tester>  cli/lightning-cli listpeers { "peers" :  	[  		{ "state" : "GOSSIPING", "id" : "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432", "netaddr" :  			[ "104.198.32.198:9735" ], "connected" : true, "owner" : "lightning_gossipd" } ] }
12:25 < c-tester> thats my list peers output
12:25 < buZz> ok, so no open channel yet
12:26 < buZz> you need ./lightning-cli fundchannel 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 10  
12:26 < buZz> to put in 10 satoshi :P
12:26 < buZz> hehe
12:26 < buZz> maybe you want to fund the channel for more?
12:27 < buZz> remember that it'll use the fee bitcoin-cli uses
12:27 < buZz> so you might wanna settxfee before that
12:28 < c-tester> right... i will need to up that fee... 
12:33 < pocket> is c-l using bitcoind's wallet.dat?
12:35 < buZz> i dont believe it does
12:36 < pocket> hmm     
12:37 < pocket> Where is the node's name configured, any idea?
12:37 < buZz> --rgb <arg>                    RRGGBB hex color for node
12:37 < buZz> --alias <arg>                  Up to 32-byte alias for node
12:37 < buZz> on lightningd
12:38 < pocket> THX     
12:38 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Quit: Leaving.]     
12:40 < buZz> oooo i see myself on the map now \o
12:41 < tweaks> yep, and you chose yellow
12:42 < buZz> should have used FF9900 instead ;)
12:47 < jojeyh> while running lightningd all the other lightning*d processes are defunct
12:47 < jojeyh> anybody else get this?
12:47 < buZz> yeah those are seperate processes
12:47 < buZz> and doing nothing , so defunct :)
12:47 < jojeyh> i know its not that big of a deal that there a few zombies
12:48 < jojeyh> just wondering why that is
12:48 < buZz> check 'ps aux' , they are different threads
12:48 < buZz> with different purposes
12:48 < jojeyh> yeah i get that just wondering if this is normal behavior ?
12:48 < jojeyh> i've never seen it before 
12:48 < buZz> yeah totally
12:48 < jojeyh> okie dokie
12:58 < grubles> so how can i spam payments between me and my channel partner 
13:00 < pocket> Between you and the whole network
13:00 < pocket> if your partner is connected to other nodes
13:01 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-lwcabvtkfmybtjpt] has joined #c-lightning     
13:06 < pocket> What things can i do to up the security off the node?
13:10 -!- tlp [~tlp@unaffiliated/tlp] has joined #c-lightning     
13:11 < jojeyh> so i've got two nodes running on testnet just on my local network, connected the nodes and funded the channel
13:11 < jojeyh> state of peer is @ CHANNELD_AWAITING_LOCKIN but the funding transaction originally used defs has 6 confirms
13:11 < jojeyh> what am i doing wrong?
13:16 < jojeyh> is it 1 confirmation from the command 'lightning-cli fundchannel' ?
13:16 < jojeyh> or the original tx send to the wallet ?
13:16 < buZz> 6 from that afaik
13:16 < buZz> 1 or 2 for it to be usable by you, 6 to become public
13:17 < jojeyh> sorry which one
13:17 < buZz> the fundchannel one
13:17 < jojeyh> ah ok i will wait patiently then
13:17 < buZz> :)     
13:17 < jojeyh> -__-
13:46 < vigorousbearhunt> "failed: WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)"
13:46 < vigorousbearhunt> Any ideas? I wont to buy a blockchino.
13:49 < pocket> I think i got that error when i accidentally copied mainnet node details to connect my testnet node to
13:57 < vigorousbearhunt> Oh. I think I never messed with LN on mainnet, and the ACINQ browser clearly shows my node on the map, along with my channels. I am not connected to the endurance node though.
13:58 < vigorousbearhunt> I heard that if you are connected to endurance the coffee payments work. I might have to do with routing and channel balance saturation.
13:58 < pocket> Connect to Nederland
13:58 < pocket> it will work:) dont it
13:59 < pocket> https://explorer.acinq.co/#/n/029dbd7baa96252b6f000e3522ab1b81884a43c47d517c5effde0160e67c6961c1
13:59 < pocket> done it*
14:03 < vigorousbearhunt> cool. Is that your node?
14:06 < pocket> jup     
14:06 < grubles> should two entries show up if i grep listchannels for my node id?
14:06 < grubles> if i only have one channel open
14:06 < vigorousbearhunt> cool
14:07 < vigorousbearhunt> grubles, I have 2 channels open, and grep returns four. So yeah :p
14:08 < grubles> ok just checking lol
14:08 < vigorousbearhunt> I had the same question
14:08 < vigorousbearhunt> pocket, Looks like I'm out of luck. TRACE: Failed connected out for 0298d0c6987e2e64451c7f723e15aff4dfca92f0e3973d214e206257abb0d1dd55, will try again. Never stops.
14:08 < pocket> hmmm
14:10 < pocket> u connected first?
14:11 < pocket> vigorousbearhunt
14:11 < vigorousbearhunt> yup     
14:12 < vigorousbearhunt> ./lightning-cli connect 029dbd7baa96252b6f000e3522ab1b81884a43c47d517c5effde0160e67c6961c1 77.162.104.62:9735 
14:13 < pocket> maybe without the port
14:14 < grubles> you need a space between the ip and the port
14:14 < pocket> if the port is not 9735 i think it needs to be seperated by a space
14:14 < grubles> and no colon
14:14 < pocket> right
14:15 < vigorousbearhunt> hmm     
14:17 < ianthius> hey guys, i sent btc to a 'newaddr' it has 3 confirmations, but isn't showing in the 'listfunds' is it waiting for 6 confs or something? curious if anyone knows
14:17 -!- Satti- [~ubuntu@199.66.90.209] has joined #c-lightning     
14:17 < vigorousbearhunt> It loops through these 4 lines. Over and over again. https://pastebin.com/raw/bmWtqiNV
14:17 < vigorousbearhunt> ianthius, Do are you on mainnet?
14:18 < pocket> I got this: Ignoring node announcement, it's outdated
14:18 < pocket> maybe thats you
14:19 < mlz> so Elaine's store is using clightning but when i open a channel with her store using almost the max amount to fund the channel i get this error: 
14:19 < mlz> ~$ lncli openchannel 02c8ebb98a0f133b19fb7bc982ec233d2db32b59d1f1ec178c9bb091a4e2c8d72c 16700000 2000
14:19 < mlz> [lncli] rpc error: code = Code(216) desc = to_self_delay 2006 larger than 432
14:20 < mlz> clightning has so many errors with fees.. i hope the devs can solve this 
14:21 < pocket> Try connecting to another node mlz
14:21 < mlz> hm?     
14:21 < pocket> connect with me for example
14:21 < mlz> that does NOT solve anything
14:21 < mlz> no thanks
14:24 < ianthius> vigorousbearhunt: yes, i am on main
14:24 < mlz> and here i'm opening a channel with someone's LND node with the same amounts, no problem:  
14:24 < mlz> ~$ lncli openchannel 02139a5bc1f1c929c04530a99160f2072e2a731f14c666abf87479510912279c11 16700000 2000
14:24 < mlz> {     
14:24 < mlz>         "funding_txid": "f4bafae537e3edf3a069dd0d2115f3d952e0a0412c3c437d00a32bbe181afcee"
14:24 < mlz> }     
14:25 < pocket>  The sender SHOULD set `to_self_delay` sufficient to ensure the sender can irreversibly spend a commitment transaction
14:25 < ianthius> weird i can't find the blocks hash in my logs, my node must not be getting recent blockss..
14:26 < vigorousbearhunt> ianthius, Whatever you do, be careful not to loose funds.
14:28  * ianthius gives thumbs up and smiles
14:28 < ianthius> i'll be just fine.
14:28 < ianthius> :)     
14:29 < pocket> Did removing the port help?
14:29 < pocket> vigorousbearhunt
14:29 < vigorousbearhunt> ianthius, thumbs up
14:30 < vigorousbearhunt> pocket, no, lightningd panicked and couldn't sop trying to connect to your node
14:30 < pocket>  :O     
14:31 < vigorousbearhunt> I restarted
14:31 < vigorousbearhunt> pocket, And it still tries to connect to 0298d0c6987e2e64451c7f723e15aff4dfca92f0e3973d214e206257abb0d1dd55 after restarting
14:31 < vigorousbearhunt> There should be a conf file somewhere
14:32 < vigorousbearhunt> Found it. It's a hidden folder ./lightning
14:32 < vigorousbearhunt> .lightning *
14:33 < pocket> There are some configurations in the sqlite file
14:33 < ianthius> cdecker: my node is stuck on block 505701, my bitcoind is running just fine... how should i debug to help the most? Note: it IS a pruned node, but hasn't has an issue like this yet in the last 3 days i have been running it.
14:43 < vigorousbearhunt> pocket, I messed up, your channel is 029dbd7baa96252b6f000e3522ab1b81884a43c47d517c5effde0160e67c6961c1 and NOT 0298d0c6987e2e64451c7f723e15aff4dfca92f0e3973d214e206257abb0d1dd55
14:43 < vigorousbearhunt> It will take some time to investigate
14:44 < pocket> I wouldnt have noticed that either
14:47 < jojeyh> 1 confirmation of funding transaction should result in channel state 'CHANNELD_AWAITING_LOCKIN`
14:47 < jojeyh> ?     
14:47 < jojeyh> i've got 3 confirms but still AWAITING_LOCKIN
14:49 < vigorousbearhunt> jojeyh, I should be CHANNELD_NORMAL after 1 conf
14:49 < jojeyh> thats why i thought
14:49 < jojeyh> what*
14:50 < jojeyh> not sure why it hasn't updated
14:50 <@cdecker> ianthius, can you file an issue on github? Sounds like it could be related to #709
14:50 < vigorousbearhunt> jojeyh, Try "lightning-cli listchannels | grep your_node_id_using_getinfo" after 6 confirmations
14:51 < jojeyh> vigorousbearhunt, ok
14:51 < vigorousbearhunt> It should be public : true
14:51 < pocket> @cdecker the hsm sectet is used as a seed for the bitcoin addresses right?
14:52 < ianthius> cdecker: yes, i can. I just restarted it and now it's height got smaller (505671)! :0
15:01 < ianthius> can logs be posted on the internet? i assume it will have ip addresses, what else of identifying info? certainly not private keys...
15:09 -!- lugg [uid274294@gateway/web/irccloud.com/x-wrtcwfvtkkhshzdu] has quit [Quit: Connection closed for inactivity]     
15:17 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning     
15:24 < jojeyh> vigorousbearhunt, 6 confirms and still in CHANNELD_AWAITING_LOCKIN
15:27 < vigorousbearhunt> jojeyh, I'm not sure what to do on that. did you try the grep command?
15:27 < jojeyh> i did not but only because 'lightning-cli listchannels' returns nothing anyways
15:27 < jojeyh> i must be missing a step
15:28 < jojeyh> i will go over the specs and figure out
15:28 < jojeyh> tbc     
15:32 < vigorousbearhunt> jojeyh, yeah, lightning-cli listchannels lists every sigle channel in the network, it should be well over 1k lines for testnet
15:32 < jojeyh> ah well that could be a problem lol
15:33 < jojeyh> are there usual reasons for it being empty?
15:39 < vigorousbearhunt> I have no idea. The c-lightning readme is simple to follow. Start all over again. I should work.
15:40 < vigorousbearhunt> I would speculate that you need at least one connection in arder to all all the nodes
15:41 < jojeyh> ah the node i am connecting to is on my local network
15:41 < jojeyh> but even then i should still be able to create a channel on my local network?
15:42 < jojeyh> and my two nodes would only see each other and there would be one channel
15:44 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has quit [Ping timeout: 256 seconds]     
15:51 < vigorousbearhunt> I guess that's true.
15:51 < vigorousbearhunt> pocket, Just for the sake of history, lnd.bitrefill.com is down. cannot even resolve to ip
15:51 < vigorousbearhunt> It was not my fault
15:52 < vigorousbearhunt> I'll try to close the channel
15:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
15:58 < jojeyh> would it make any difference if i moved the executables into /usr/bin instead of running htem from the lightning folder?
16:02 < vigorousbearhunt> jojeyh, I don't think it would. Mine are inside a folder in the user direcory
16:03 < jojeyh> hmm time for some more reading :)
16:05 -!- Satti- [~ubuntu@199.66.90.209] has quit [Ping timeout: 240 seconds]     
16:14 -!- heuristics [68e87794@gateway/web/freenode/ip.104.232.119.148] has quit [Quit: Page closed]     
16:23 -!- aproc [~aproc@2605:6000:e503:8300:5988:360b:d899:4044] has joined #c-lightning     
16:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 248 seconds]     
16:25 -!- pocket [4da2683e@gateway/web/freenode/ip.77.162.104.62] has quit [Ping timeout: 260 seconds]     
16:32 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 264 seconds]     
16:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
16:46 -!- shesek [~shesek@bzq-84-110-60-135.cablep.bezeqint.net] has joined #c-lightning     
16:46 -!- shesek [~shesek@bzq-84-110-60-135.cablep.bezeqint.net] has quit [Changing host]     
16:46 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
16:54 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 248 seconds]     
16:56 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #c-lightning     
17:08 < jojeyh> going through the README.md i see that when connecting to a node it explicitly emphasizes 'remote' as **remote** so i'm guessing its not ok to connect to a local node
17:08 < jojeyh> can anybody confirm this?
17:08 < jojeyh> seems like something work fixing
17:08 < jojeyh> worth* 
17:16 < vigorousbearhunt> jojeyh, It could be, but I'm not sure.
17:22 -!- lugg_ [uid274294@gateway/web/irccloud.com/x-pnyczzsddmaoqqqr] has joined #c-lightning     
17:25 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has quit [Quit: Leaving]     
17:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
17:49 < jojeyh> is there a testnet node open hosted by blockstream or some other good folk?
18:45 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]     
19:04 < truk_> Hello! Ok, I have a question. I'm currently on live net and when I send a payment I'm getting hit with- "first peer not ready: WIRE_UNKNOWN_NEXT_PEER"
19:22 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 256 seconds]     
19:26 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning     
19:34 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
19:46 -!- cluelessperson [~cluelessp@unaffiliated/cluelessperson] has joined #c-lightning     
19:47 < cluelessperson> hi there.
19:47 < cluelessperson> Does c-lightning support mainnet?
19:47 < tweaks> yes     
19:47 < tweaks> https://github.com/ElementsProject/lightning
19:47 < tweaks> install then: lightningd/lightningd --network=bitcoin --log-level=debug
19:48 < tweaks> on a sync'd node with bitcoind, and done.
19:50 < cluelessperson> swet
19:51 < cluelessperson> tweaks: do I need to configure an RPC host,port,user,pass ?
19:52 < tweaks> not if its on the same node
19:52 < cluelessperson> tweaks: uh, how does it determine the credentials?  I have my node setup with stuff in   /etc/bitcoin/bitcoin-mainnet.conf  as an example
20:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
20:16 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds]     
20:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
20:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]     
20:58 -!- Ulmo [1804e4d5@gateway/web/cgi-irc/kiwiirc.com/ip.24.4.228.213] has joined #c-lightning     
20:59 < Ulmo> Hello! I just restarted my lightningd, and the channels are all listed as "active:false" and "public:false", but before I shut down lightningd before, it had many active channels. How long does it take for them to become active again?
21:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
21:13 < Ulmo> just restarted my lightningd, and the channels are all listed as "active:false" and "public:false", but before I shut down lightningd before, it had many active channels. How long does it take for them to become active again?
21:14 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning     
21:29 -githubby:#c-lightning- [lightning] jb55 opened pull request #752: bitcoin: add test programs to ALL_TEST_PROGRAMS (master...bitcoin-makefile-fixes) https://git.io/vNo4z
21:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds]     
21:36 -!- Ulmo [1804e4d5@gateway/web/cgi-irc/kiwiirc.com/ip.24.4.228.213] has quit [Remote host closed the connection]     
21:37 -!- Ulmo [1804e4d5@gateway/web/cgi-irc/kiwiirc.com/ip.24.4.228.213] has joined #c-lightning     
21:37 < Ulmo> If no one here can answer me, where can I read about lighting-c's process for turning a channel "active" after a restart?
21:38 < Ulmo> never mind
21:38 < Ulmo> It took about an hour!  wow.
21:38 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection]     
21:39 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
21:40 < Ulmo> well, on one of my nodes, it completed, but on the other, it has not yet completed.
21:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
21:48 -!- c-tester [ac618a6a@gateway/web/freenode/ip.172.97.138.106] has quit [Quit: Page closed]     
21:53 < Ulmo> they're both complete.
21:53 < Ulmo> Now getting "WIRE_FEE_INSUFFICIENT"
21:53 < Ulmo> for a payment I'm sending
22:15 -!- jojeyh [~delphi@2602:306:b8b6:b970:20ff:29a4:c81c:7488] has quit [Ping timeout: 276 seconds]     
22:17 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds]     
22:21 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
22:30 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]     
22:34 -!- Ulmo [1804e4d5@gateway/web/cgi-irc/kiwiirc.com/ip.24.4.228.213] has quit [Ping timeout: 260 seconds]     
23:38 -!- takinbo [sid19838@gateway/web/irccloud.com/x-cfoexchavewmtllj] has joined #c-lightning     
23:41 -!- lugg_ [uid274294@gateway/web/irccloud.com/x-pnyczzsddmaoqqqr] has quit [Quit: Connection closed for inactivity]