--- Day changed Thu Jan 25 2018
00:04 < cncr04s> is there any docs on exactly what lightning does/can do, ie how payments/channels/and transactions work
01:13 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]     
01:13 -!- amp__ [~amp@24.136.5.183] has joined #c-lightning     
01:27 -!- ebx_ [~ebx@12.226.6.52] has joined #c-lightning     
01:27 -!- ebx [~ebx@12.226.6.52] has quit [Ping timeout: 252 seconds]     
01:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
02:07 -!- ebx_ [~ebx@12.226.6.52] has quit [Read error: Connection reset by peer]     
02:07 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
02:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]     
02:51 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
02:58 -!- p3tr [~p3tr@srv.p3tr.cz] has joined #c-lightning     
03:01 < p3tr> hi there! i'm trying out lightning on testnet but it seems to me my payments are trying to get routed through nodes that i have previously had channels with but are now closed... is this some known issue or am i doing something wrong?
03:02 < p3tr> when i try to make the payment it fails with: "first peer not ready: WIRE_UNKNOWN_NEXT_PEER"
03:02 < p3tr> when i check the route to the recipient the first node is one to which i had previously had an open channel, but i closed it
03:03 < p3tr> though listpeers shows the channel, but with state CHANNELD_SHUTTING_DOWN
03:08 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #770: Stuck in awaiting lockin fix (master...stuck-in-awaiting-lockin) https://git.io/vNiJx
03:08 < rusty> p3tr: very latest git should fix this, I think.  What version?
03:10 -!- mark__ [b94187ac@gateway/web/freenode/ip.185.65.135.172] has joined #c-lightning     
03:11 < p3tr> rusty: ah - i just updated about an hour ago, but this locked up channel has been there for a couple of days
03:11 < p3tr> only now have i had time to get here and complain ;)
03:13 < rusty> Ah!  yeah, I just merged cdecker's fix which properly deactivates channels as we go down.  But maybe not in retrospect?  Christian?
03:13 < p3tr> seems to be the case since its still there, trying to run close on it again just says "Peer is in state CHANNELD_SHUTTING_DOWN"
03:13 <@cdecker> They should get deactivated on the first reconnect attempt, assuming they can get past the handshake
03:14 <@cdecker> Oh yeah, and close should also deactivate them
03:15 < p3tr> hm, looking at listpeers i see that the peer in question has "connected": false
03:15 < p3tr> let me try to connect to it
03:17 < p3tr> hm, this might be the culprit: doing connect to that peer does nothing (the command is still hanging)
03:17 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer]     
03:24 < p3tr> the question is though, why does the selected route begin with a peer i have no open channel with? or am I misunderstanding the issue?
03:52 -githubby:#c-lightning- [lightning] cdecker closed pull request #770: Stuck in awaiting lockin fix (master...stuck-in-awaiting-lockin) https://git.io/vNiJx
04:19 < p3tr> looking at github it seems these are known issues so i will fait for a fix :)
04:36 -!- mn3monic [~xxwa@host82-204-dynamic.49-79-r.retail.telecomitalia.it] has quit [Read error: Connection reset by peer]     
05:01 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 268 seconds]     
05:12 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-igrkulieriyritqa] has quit [Quit: Connection closed for inactivity]     
05:14 < mark__> is there something extra that needs to be done to get c-lightning to work on centos7? lightningd doesn't seem to be able to bind correctly to port 9735
05:14 < buZz> mark__: i'd assume some selinux or apparmor tweaking
05:15 < mark__> selinux is not active
05:16 < mark__> when I look with lsof I get the following: lightning 12080        centos    4u     IPv6             192925       0t0      TCP *:9735 (LISTEN)
05:16 < mark__> but nothing for IPv4
05:17 < mark__> and the log for lightningd tells me lightning_gossipd(12080): TRACE: req: type WIRE_GOSSIPCTL_INIT len 126 lightning_gossipd(12080): TRACE: Creating IPv6 listener on port 9735 lightning_gossipd(12080): TRACE: Failed to bind on 2 socket: Address already in use
05:18 < mark__> I haven't made any changes from default to activate ipv6 in any way
05:24 < mark__> sorry, I actually just realised that selinux was active on this server
05:24 -!- vitaminc_ [~vitaminc@192.5.151.254] has quit [Ping timeout: 248 seconds]     
05:25 -!- vitaminc [~vitaminc@192.5.151.254] has quit [Ping timeout: 260 seconds]     
05:25 < mark__> any advice on what changed is needed to get lightningd working with selinux
05:27 -!- amp__ [~amp@24.136.5.183] has quit [Quit: Leaving]     
05:28 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning     
05:42 < mark__> I turned off selinux but still get the same problem 
05:47 -!- shesek [~shesek@5.102.207.185] has joined #c-lightning     
05:47 -!- shesek [~shesek@5.102.207.185] has quit [Changing host]     
05:47 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
06:26 -!- sam___ [484f79d5@gateway/web/freenode/ip.72.79.121.213] has joined #c-lightning     
06:27 < sam___> Good morning! I'm the one who opened https://github.com/ElementsProject/lightning/issues/759
06:28 < sam___> just added a comment. I'm available to troubleshoot live if you want
06:28 < sam___> also, I have a few other questions. 1) how do I find my PubKey? I don't see my node listed in https://lnmainnet.gaben.win/
06:29 < sam___> 2) how do I set an Alias?
06:29 < p3tr> sam___: set alias using: --alias 
06:30 < p3tr> (when starting lightning)
06:31 < sam___> awesome, thank you
06:31 < buZz> sam___: you only see your node on there once you have fully funded (and public) channels running
06:32 < buZz> pubkey can be found with 'getinfo'
06:33 < sam___> Thanks buZz. I think I have 2 funded channels (6 confirms on both txs)
06:33 < sam___> details at the bottom of the github issue
06:34 < buZz> check listchannels to see if your channels are in there with public: true
06:35 < sam___> lightning-cli listchannels | grep 02e40b82365cd2a3908a481b712ba09858a5dee4cac997351db6cbaa175129907b 		{ "source" : "02e40b82365cd2a3908a481b712ba09858a5dee4cac997351db6cbaa175129907b", "destination" : "0387e3780a4325eb38421fb83000a6f6c0ffa4a69ea0c81db3f00e8e5015c9e8a1", "short_channel_id" : "506052:1274:0", "flags" : 0, "active" : true, "public" : true, "last_update" : 1516889294, "base_fee_millisatoshi" : 1000, "fee_per_million
06:36 < buZz> alright, and you see 2 of em right? for that hash?
06:36 < buZz> yep, i see them, 2x 2 channels
06:36 < sam___> I see 4 actually. 2 are source, 2 dest
06:40 < buZz> looks just fine
06:43 < sam___> hmm, any ideas as to what I should do?
06:44 < buZz> not sure what WIRE_PERMANENT_NODE_FAILURE means
06:44 < buZz> i'd really love some table of errormsgs by c-lightning :D
06:44 < buZz> with small explanation a piece
06:45 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has joined #c-lightning     
06:46 < p3tr> buZz: same, sometimes i have no idea whats wrong
06:49 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning     
06:51 < buZz> cdecker: does such a table exist? (one that explains all the states/errors/messages) 
07:00 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 260 seconds]     
07:07 -!- justus [4db37f01@gateway/web/freenode/ip.77.179.127.1] has joined #c-lightning     
07:08 < justus> when I try to make a payment I get "cannot find myself" error message. any ideas on how to fix this?
07:10 < justus> this one: "find_route: cannot find myself (...)"
07:15 < buZz> did you open a channel?
07:15 < justus> yes     
07:15 < buZz> ('connect' doesnt open one)
07:15 < buZz> is the 'fundchannel' tx already 6x confirmed?
07:17 < justus> yes     
07:18 < justus> this is the funding tx: https://btc-bitcore4.trezor.io/tx/4d09291882f65feec08f2433ec31dd176edbf932f77df8e8c3c32d99f72e73eb
07:19 < buZz> whats your node's id?
07:19 < justus> 0235c6758f6f6409d3df4bf756baa2d896c438b50d51c81097387959d66fabf4a3
07:20 < buZz> yeah i dont see any channel open with that
07:20 < sam___> logs for getRoute to SLEEPYARK:
07:20 < sam___> lightning_gossipd(13): TRACE: Failed connected out for 039a8f88dca257f4f67a2c65bfcc6ab1d398488334d3b3a78d514c8e3f6638a903, will try again lightningd(1): Connected json input lightning_gossipd(13): TRACE: req: type WIRE_GOSSIP_GETROUTE_REQUEST len 78 lightning_gossipd(13): TRACE: Trying to find a route from 02e40b82365cd2a3908a481b712ba09858a5dee4cac997351db6cbaa175129907b to 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d696
07:20 < sam___> https://pastebin.com/ifChBKH3
07:22 < buZz> justus: i dont see any channel you opened
07:23 < buZz> sam___: weird, i'm getting routes to all the nodes in there
07:23 < buZz> even yours
07:23 < justus> buZz: what do you think happened? :) what do I do now?
07:24 < sam___> justus: is it possible you just funded your LN node and not a channel?
07:24 < buZz> justus: whats the txid from the 'fundchannel ' you did? 
07:24 < buZz> so , not the initial funding, but the -channel- opening?
07:25 < buZz> that txid you linked wasnt for opening a channel, just initial LN wallet funding, right?
07:25 < buZz> https://blockchain.info/tx/4d09291882f65feec08f2433ec31dd176edbf932f77df8e8c3c32d99f72e73eb 
07:25 < buZz> oh, nope, its the channel opening .. weird
07:25 < sam___> I'm getting a ton of lightning_gossipd(13): TRACE: Failed connected out for 039a8f88dca257f4f67a2c65bfcc6ab1d398488334d3b3a78d514c8e3f6638a903, will try again
07:25 < buZz> justus: try 'getlog' ?
07:25 < buZz> sam___: maybe that node just shut down?
07:26 < sam___> maybe, but it's still up on recksplorer
07:27 < justus> here is my getlog output: https://pastebin.com/1vCYwS9b
07:28 < buZz> thats not getlog output?
07:28 < buZz> oh wait, it is
07:28 < buZz> Owning subdaemon lightning_channeld died (33792) 
07:28 < buZz> weird
07:29 < buZz> did your OS kill it?
07:29 -!- shesek [~shesek@5.102.207.185] has joined #c-lightning     
07:29 -!- shesek [~shesek@5.102.207.185] has quit [Changing host]     
07:29 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
07:30 < justus> I don't know. does a restart of lightningd help with this?
07:31 < buZz> wish i knew :P 
07:32 < justus> maybe I just try to close the channel and stick to on chain transactions ;)
07:34 < p3tr> on chain is boring ;)
07:35 < buZz> cant buy blockstream stickers with onchain
07:36 < buZz> that was 100% my motivation ^_^
07:36 -!- justus_ [~justus@x4db37f01.dyn.telefonica.de] has joined #c-lightning     
07:37 -!- justus [4db37f01@gateway/web/freenode/ip.77.179.127.1] has left #c-lightning []     
07:37 -!- justus_ is now known as justus     
07:39 -!- moctost [~moctost@88.202.178.100] has joined #c-lightning     
07:39 < justus> yes, i also need some stickers :(
07:44 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 248 seconds]     
07:46 -!- justus is now known as justusk     
07:47 -!- Saevar [2e166296@gateway/web/freenode/ip.46.22.98.150] has quit [Ping timeout: 260 seconds]     
07:53 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 240 seconds]     
08:00 -!- c-tester [20616e3b@gateway/web/freenode/ip.32.97.110.59] has joined #c-lightning     
08:01 -!- shesek [~shesek@5.102.207.185] has joined #c-lightning     
08:01 -!- shesek [~shesek@5.102.207.185] has quit [Changing host]     
08:01 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
08:02 < c-tester> to replenish funds in a channel.. do I simply send btc to the original address or create a new one?
08:07 < hkjn0> hey, I'm currently rebuilding from latest HEAD to see if anything changes, but with a commit a few days old I'm hitting this assert on startup: https://github.com/ElementsProject/lightning/blob/master/lightningd/peer_control.c#L2750
08:07 < hkjn0> any idea how we could get into that state? I shut down lightningd and then bitcoind gracefully as far as I could tell and noticed no issues before starting up lightningd again
08:15 -!- alexann [~Alex@79.125.252.208] has quit [Ping timeout: 248 seconds]     
08:16 -!- alexann [~Alex@77.29.86.81] has joined #c-lightning     
08:19 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has joined #c-lightning     
08:37 -!- mark__ [b94187ac@gateway/web/freenode/ip.185.65.135.172] has quit [Ping timeout: 260 seconds]     
08:41 < lugg_> the peer what happens if you close a channel, but your peer is disconnected when you hit the 144 block waiting period?
08:41 < lugg_> or rather, what happens if your peer never reconnects? :P
08:57 -!- justusk [~justus@x4db37f01.dyn.telefonica.de] has quit [Remote host closed the connection]     
09:04 -!- redstorm [cb56cc58@gateway/web/freenode/ip.203.86.204.88] has joined #c-lightning     
09:06 -!- jb55 [~jb55@d108-172-210-7.bchsia.telus.net] has joined #c-lightning     
09:13 < mlz> i'm running c-lightning but keep getting this rpc error:  $ lightning-cli getinfo
09:13 < mlz> [lncli] rpc error: code = Unavailable desc = grpc: the connection is unavailable
09:13 < mlz> what am i missing?
09:14 < jb55> err, that's output from lnd
09:14 < jb55> did you alias lightning-cli to lncli?
09:24 < mlz> yes jb
09:24 < mlz> that's clightning
09:25 < mlz> do i need to put rpcuser and rpcpassword in bitcoin.conf?
09:26 < pigeons> no i dont have rpcuser and rpcpassword in the conf and it uses the cookie from the datadir
09:27 < mlz> yea i think it should use the .cookie file but sometimes bitcoind can get flakey
09:27 < jb55> mlz: grpc is an lnd thing, the output you posted is from lnd
09:27 < mlz> jb55, but i'm not running lnd on this environment
09:27 < jb55> what does `which lightning-cli` say
09:28 < mlz>   /usr/local/bin/lightning-cli
09:30 < jb55> mlz: what does `file /usr/local/bin/lightning-cli`, if it says posix shell script, can you `cat /usr/local/bin/lightning-cli` and post it?
09:30 < jb55> something fishy going on
09:32 < mlz> it doesn't say "posix shell script"
09:33 < jb55> oh right
09:33 < jb55> nm     
09:34 < jb55> what does `ldd /usr/local/bin/lightning-cli` return?
09:34 < jb55> that should solve it
09:36 < mlz>         linux-vdso.so.1 =>  (0x00007fffe5fb5000)
09:36 < mlz>         libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ffde7360000)
09:36 < mlz>         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ffde6f90000)
09:36 < mlz>         /lib64/ld-linux-x86-64.so.2 (0x00007ffde7800000)
09:37 -!- redstorm [cb56cc58@gateway/web/freenode/ip.203.86.204.88] has quit [Quit: Page closed]     
09:37 < jb55> and lightning-cli --help ?
09:38 < jb55> sorry
09:38 < jb55> this was an obvious one I should have just asked
09:38 < jb55> initially
09:38 < mlz> i restarted both bitcoind and lightningd.. now i've noticed lightningd can't finish to the latest block maybe this is why?
09:39 < jb55> the output of that command is definitely lnd, I'm just trying to figure out why. might be some env issue. lncli = lnd
09:40 < ianthius> arghh not only is my node not keeping up with the blockheight but it's just losing funds from 'listfunds' i should have 3 addresses with balances but now i only have 1 :(
09:41 < jb55> ianthius: you see cdecker's comment to your issue 1h ago?
09:41 < mlz> jb55, i did run lnd on this bash ubuntu before and i still have the files but that should not be a problem 
09:42 < ianthius> no haven't checked the latest. but this listfunds thing is wierd since they are way older blocks than my nodes current block height. i will check github
09:42 < jb55> mlz: what does lightning-cli --help say?
09:42 < mlz> ok so i restarted lightningd, it caught up to the current block but still got the same error
09:42 < mlz> hold on
09:42 < mlz> lightning-cli --help shows everything in help
09:44 < mlz> $ lightning-cli --help | pastebinit
09:44 < mlz> http://paste.ubuntu.com/26459648/
09:44 < jb55> that's not clightning
09:44 < jb55> look: control plane for your Lightning Network Daemon (lnd)
09:44 < mlz> omg     
09:44 < mlz> lol how can this happen? lmao
09:44 < jb55> what about which -a lightning-cli
09:45 < buZz> lol mlz 
09:45 < jb55> you may have aliased lightning-cli to lncli somehow
09:45 < mlz> ah     
09:45 < mlz> how do you reverse this?
09:46 < mlz> or i just have to wipe everything?
09:46 -!- sam___ [484f79d5@gateway/web/freenode/ip.72.79.121.213] has quit [Quit: Page closed]     
09:46 < mlz> buZz, isn't this fun.. lunix is fun :P 
09:46 < jb55> does which -a lightning-cli return multiple lines?
09:46 < buZz> which `lightning-cli`
09:46 < mlz> jb55, nope
09:46 < jb55> oh     
09:46 < buZz> ls -l `which lightning-cli`
09:46 < buZz> is it a symlink? :)
09:47 < jb55> I know why :]
09:47 < jb55> just cd to the clightning dir and then do ./cli/lightning-cli instead.
09:47 < jb55> it's probably not in your path
09:47 < jb55> since there is no install yet
09:49 < jb55> I just have something like this in my user bin path: https://jb55.com/s/4d6eea220da281d8.txt
09:49 < jb55> you could also make an alias
09:49 < jb55> or you could add it directly to your path. many options :]
09:51 -!- justusk [~justus@x4db37f01.dyn.telefonica.de] has joined #c-lightning     
09:55 < ianthius> can someone paste a command line command that will output all your lightningd wallet addresses from the DB?
09:55 < ianthius> at home i have the sql gui :|
09:55 < mlz> jb55, no need to do all that extra complicated stuff, i got it fixed
09:55 < mlz> alias lncli=lightning-cli
10:00 -!- peterm [54c4bb2e@gateway/web/freenode/ip.84.196.187.46] has joined #c-lightning     
10:00 < peterm> Hallo c-tester
10:05 < jb55> mlz: I wouldn't alias lncli to lightning-cli unless you want to confuse yourself in the future when you want to use lnd again... :p
10:06 < mlz> lol     
10:06 < mlz> im going to delete lnd :D
10:07 -githubby:#c-lightning- [lightning] jb55 opened pull request #773: doc: some sqlite db info for HACKING (master...db-hacking) https://git.io/vNipQ
10:10 < peterm> Q: Any link to decent docs on the cli ?
10:12 < c-tester> Hi Peter....
10:20 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has quit []     
10:23 < c-tester> cli/lightning-cli help  will list all commands... not aware of any good docs
10:24 < mlz> jb55, i got lncli to work :D
10:26 < mlz> will this be changed in the future:  $ lncli connect 02c8ebb98a0f133b19fb7bc982ec233d2db32b59d1f1ec178c9bb091a4e2c8d72c@45.76.235.75:9735
10:26 < mlz> "id 02c8ebb98a0f133b19fb7bc982ec233d2db32b59d1f1ec178c9bb091a4e2c8d72c@45.76.235.75:9735 not valid"
10:27 < jb55> peterm: there are some initial manpages, nothing comprehensive yet though: man ./doc/lightning-pay.7
10:27 -!- justusk [~justus@x4db37f01.dyn.telefonica.de] has quit [Remote host closed the connection]     
10:27 < jb55> mlz: https://github.com/ElementsProject/lightning/issues/636
10:28 < mlz> oh cool.. thank you! 
10:29 < peterm> hi c-tester wanted to send you some satochi, but it didnot work out :-/
10:30 < peterm> ll try again
10:32 < peterm> I see a route
10:32 < peterm> 	[  		{ "id" : "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432", "channel" : "505949:2337:0", "msatoshi" : 11000, "delay" : 23 },  		{ "id" : "0201c0a1c3fdbefdd72fba461df6500f7ed773f3d9d63f794634c973c70dbc096b", "channel" : "505934:1295:1", "msatoshi" : 10000, "delay" : 9 } ] }
10:35 < peterm> But if I pay the invoice, it says "could not find to route"
10:38 < c-tester> im rebooting my server at the moment...
10:43 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 264 seconds]     
10:49 -!- jb55 [~jb55@d108-172-210-7.bchsia.telus.net] has quit [Read error: Connection reset by peer]     
10:50 -!- jb55 [~jb55@d108-172-210-7.bchsia.telus.net] has joined #c-lightning     
10:56 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wootrppggosyxjbb] has joined #c-lightning     
11:04 < mlz> what's the max amount to fundchannel for clightning?
11:07 < peterm> 21M BTC
11:07 < jb55> less than 2^24 satoshis
11:07 < jb55> for now
11:08 < jb55> https://jb55.com/s/3f337ffad6629fed.txt
11:11 < peterm> only 0.1677 btc?
11:13 < jb55> for now
11:14 < peterm> lol     
11:14 < jb55> that's 167000 dollars when btc is worth one million (think long term ;)
11:14 < peterm> I try to pay something to someone, any volunteer?
11:15 < jb55> testnet?
11:15 < peterm> :-)     
11:16 < peterm> I got a route
11:16 < peterm> but when i try to pay it says: "could not find to route"
11:16 < peterm> then i am stuck
11:28 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has joined #c-lightning     
11:36 -!- DarkKnight_ [a29b40e2@gateway/web/freenode/ip.162.155.64.226] has joined #c-lightning     
11:37 -!- jb55 [~jb55@d108-172-210-7.bchsia.telus.net] has quit [Ping timeout: 260 seconds]     
11:37 -!- DarkKnight_ [a29b40e2@gateway/web/freenode/ip.162.155.64.226] has quit [Client Quit]     
11:42 -!- duke_Atriedes [a29b40e2@gateway/web/freenode/ip.162.155.64.226] has joined #c-lightning     
11:43 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wootrppggosyxjbb] has quit []     
11:44 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-nfzhuhxsqsrwhdmy] has joined #c-lightning     
11:46 < duke_Atriedes> How long it take for your channel to lock in?
11:46 -!- jb55 [~jb55@184.68.162.218] has joined #c-lightning     
11:53 -!- shesek [~shesek@bzq-84-110-60-135.red.bezeqint.net] has joined #c-lightning     
11:53 -!- shesek [~shesek@bzq-84-110-60-135.red.bezeqint.net] has quit [Changing host]     
11:53 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
11:54 < peterm> duke: 1 confirm
11:55 < DrOlmer> isn't it 1 confirm to be visible and 6 to be usable?
11:58 < c-tester> correct 6 to be usable
12:16 < duke_Atriedes> Hmmm I must have screwed up mine is stuck at "CHANNELD_AWAITING_LOCKIN" for 12 confirmations
12:19 < c-tester> for how long now duke?
12:22 < duke_Atriedes> going on 12 blocks about an 1 1/2 hours c-tester
12:24 -githubby:#c-lightning- [lightning] RvMp opened pull request #775: clarified --lightning-dir syntax on help (master...master) https://git.io/vNP3d
12:24 < c-tester> never seen that, is your bitcoind at the latest block?
12:26 < duke_Atriedes> c-tester yeah I've been running a full node months its always synced. Think I'm just gonna kill it and try again. Thanks for your help though
12:27 < c-tester> yeah wont hurt to reboot everything
12:33 < peterm> did you recover from the reboot ?
12:35 < duke_Atriedes> peter-m: yes I rebooted and now I have "CHANNELD_NORMAL" so looking good
12:37 < peterm> good
12:54 -!- redstorm [cb56cc58@gateway/web/freenode/ip.203.86.204.88] has joined #c-lightning     
12:54 < c-tester> AWESOME duke
12:59 < truk_> does anyone know if your lightning node ip is the same as your bitcoin node ip? 
13:00 < redstorm> Q: I have a funded channel open. I decode the starblocks invoice to get the destination ID, then getroute to test their is a route from my node to starblocks, 4 hops, but the payment fails on the 0th node unknown next peer.
13:07 < jb55> yes I had this exact issue. on my testing integration branch I do not have this issue. I believe https://github.com/ElementsProject/lightning/pull/638 is the pr that fixes it
13:10 < c-tester> Yes Truk
13:12 < mn3monic> hi     
13:13 < mn3monic> what when I lost a channel funding transaction without broadcast it?
13:13 < redstorm> Thanks @jb55, any idea when it will be merged?
13:13 -!- peterm [54c4bb2e@gateway/web/freenode/ip.84.196.187.46] has quit [Quit: Page closed]     
13:18 -!- ebx [~ebx@12.226.6.52] has quit [Ping timeout: 240 seconds]     
13:19 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
13:19 < duke_Atriedes> Did anyone else get a "Peer not connected" error when trying to fund the blockstream store channel?
13:20 < jb55> redstorm: ¯\_(ツ)_/¯
13:21 < truk_> Thanks c-tester. 
13:22 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #c-lightning     
13:27 -githubby:#c-lightning- [lightning] practicalswift opened pull request #776: Onboarding: Make "lightning-cli" (without arguments) output the equivalent of "lightning-cli --help; lightning-cli help" (master...lightning-cli-usability) https://git.io/vNPl0
13:28 -!- ebx [~ebx@12.226.6.52] has quit [Remote host closed the connection]     
13:29 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
13:30 < truk_> Ok, when I reboot my lightning node it's giving me a peer with 'activate_peer(OPENINGD) with no funding txid?'
13:31 < truk_> I tired to close that peer out but it keeps showing up after Hello World
13:31 < redstorm> @truk same i managed to open but never funded a channel 6 times, i close them but every time i stop and start lightningd they come back.
13:36 -!- ebx [~ebx@12.226.6.52] has quit [Remote host closed the connection]     
13:36 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
13:37 < truk_> Ok, also I figured out how to get the ip and port listed on start up just include --ipaddr=<IP> --port=9735
13:38 -!- newbold [~adam@cpe-74-139-234-152.kya.res.rr.com] has joined #c-lightning     
13:43 < newbold> Anyone know if https://lnmainnet.gaben.win only shows live/connected nodes? Or does it show stuff that's not currently connected (but maybe once was)?
13:44 < newbold> Related question: given a node ID or IP address, is there a definitive way to know if it's online (beyond trying to ping it)
13:45 < newbold> Reason I ask is that lightning-cli is telling me that my peer isn't connected, but I see it on the recksplorer, so I'm not sure what to believe
13:45 < c-tester> newbold.. try lightning-cli getinfo to get your node id..  then
13:46 < c-tester> use lightning-cli listchannels |grep  yournode id,  or first 10 or so characters
13:46 < c-tester> your channel and its status will be listed... 
13:46 -!- CubicEarths [~cubiceart@201.206.163.235] has joined #c-lightning     
13:46 < c-tester> should read active true, public true
13:47 < newbold> is it bad if it returns nothing? :P
13:47 < newbold> oh wow, listchannels alone returns nothing too
13:49 < newbold> although maybe it makes sense, since I closed the channel
13:49 < newbold> but I never got my funds back, and I'm wonderinfg it it's because my channel peer has been offline
13:49 < c-tester> maybe restart your bitcoind and lightning instance...
13:49 < newbold> good idea
13:50 < CubicEarths>  I've got a question about fees. Every node should have an ideal state regarding the distributions of funds in its channels. Is there currently logic that adjusts the fees higher the future the node gets away from its ideal distribution?
13:52 < newbold> c-tester: it's adding a _ton_ of blocks
13:52 < newbold> is that a sign that it needed to be restarted?
13:53 < truk_> it's syncing with your btc node
13:54 < newbold> ok, it finished, and the log ends with this: https://gist.githubusercontent.com/newbold/0eb54e12d3abc8a41b8b11dee1b75567/raw/f49aa4006b22c07bda61d01280af1ade60a2c83f/gistfile1.txt
13:55 < c-tester> yes, guess it was behind a bit
13:55 < newbold> and I think that's a clue about my problem. I closed this channel a while ago but never got the funds back
13:55 < c-tester> good luck. gotta run but back later on tonight..
13:55 -!- c-tester [20616e3b@gateway/web/freenode/ip.32.97.110.59] has left #c-lightning []     
13:56 -!- CubicEarths [~cubiceart@201.206.163.235] has quit [Read error: Connection reset by peer]     
13:56 < newbold> the peer that I had the channel with shows the 'ONCHAIND_OUR_UNILATERAL' state
13:56 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has quit [Quit: Leaving]     
13:56 -!- CubicEarths [~cubiceart@201.206.163.235] has joined #c-lightning     
14:03 < newbold> interesting, if I try to re-connect to the peer, it says "channel ALL: Funding transaction spent"
14:18 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has quit []     
14:25 < alexann> sam___> hi, i have similar problem with those ports so i hope you can help me out
14:25 < alexann> i've deployed bitcoind, and when it runs although it gives this error: {some ip}:8333 failed: Cannot assign requested address (99),  {some ip}:8333 failed after select(): Connection refused (111)
14:26 < alexann> when I run "bitcoin-cli getinfo" it shows everything's good; However, when I try the next step: [ docker run --rm --name lightning --network container:bitcoind_mainnet -v /scratch/bitcoin/mainnet/bitcoind:/root/.bitcoin -v /scratch/bitcoin/mainnet/clightning:/root/.lightning --entrypoint /usr/bin/lightningd cdecker/lightningd:master --network=bitcoin --log-level=debug ]
14:26 < newbold> alexann: you're seeing that from bitcoind, right?
14:26 < alexann> yes, from bitcoind 
14:27 < alexann> when i execute that command in order to deploy lightning i get : 
14:27 < alexann> i'm getting : [ lightningd(1): Trying to guess public addresses... lightningd(1): Address 172.17.0.2:9735 is not routable lightningd(1): Failed to connect 10 socket: Cannot assign requested address lightningd(1): testing /usr/bin/lightning_channeld lightningd(1): testing /usr/bin/lightning_closingd lightningd(1): testing /usr/bin/lightning_gossipd lightningd(1): testing /usr/bin/lightning_hsmd lightningd(1): testing /usr/bin/lightning_onchaind 
14:27 < alexann> lightningd(1): testing /usr/bin/lightning_openingd lightningd(1): HSM TRACE: Client: Received message 11 from client lightningd(1): Loaded 0 invoices from DB lightningd(1): HSM TRACE: Client: Received message 9 from client lightning_gossipd(13): pid 13, msgfd 12 lightningd(1): Loaded 0 channels from DB lightningd(1): bitcoin-cli estimatesmartfee 2 CONSERVATIVE exited with status 1 lightning_gossipd(13): TRACE: req: type WIRE_GOSSIPCTL_INIT len 119 
14:27 < alexann> lightning_gossipd(13): TRACE: Creating IPv6 listener on port 9735 lightning_gossipd(13): TRACE: Failed to bind on 2 socket: Address already in use ]
14:28 < newbold> hmm     
14:28 < alexann> I checked the ports with "netstat -pant" and shows that 8333 and 9735 are used by docker-proxy (LISTEN), but
14:28 < alexann> the output I receive by running that script shows that another app. is using that port; I have clean latest Kali linux installed with teamviewer (it uses ports 5938 and 5939) only and nothing else.
14:28 < newbold> first let's make sure bitcoind is running ok
14:28 < alexann> Is there anything particular that needs to be put into bitcoin.conf (allow ip;s, port numbers etc...) ??
14:28 < alexann> Please help me I think I'm going nuts with this. 
14:28 < newbold> try bitcoin-cli getinfo
14:29 < alexann> bitcoin-cli getinfo
14:29 < alexann> {     
14:29 < alexann>   "version": 140200,
14:29 < alexann>   "protocolversion": 70015,
14:29 < alexann>   "walletversion": 130000,
14:29 < alexann>   "balance": 0.00000000,
14:29 < alexann>   "blocks": 506109,
14:29 < alexann>   "timeoffset": -7,
14:29 < alexann>   "connections": 8,
14:29 < alexann>   "proxy": "",
14:29 < alexann>   "difficulty": 2603077300218.593,
14:29 < alexann>   "testnet": false,
14:29 < alexann>   "keypoololdest": 1516643702,
14:29 < alexann>   "keypoolsize": 100,
14:29 < alexann>   "paytxfee": 0.00000000,
14:29 < alexann>   "relayfee": 0.00001000,
14:29 < alexann>   "errors": ""
14:29 < alexann> }     
14:29 < newbold> excellent, your node is up to date
14:30 < newbold> don't worry about that one connection message, your node will have all kinds of weird connection glitches with other nodes, and it's generally no cause for concern
14:30 < newbold> now, as for c-lightning... hmm
14:30 < alexann> running this on Kali linux btw 
14:30 < newbold> have you had any other lightning clients insatlled or running on the same box? because it sounds like it can't bind to port 9735, based on that last trace message
14:30 < newbold> and that's the port it needs to use
14:31 < newbold> if you've been playing with lnd, eclair, etc. then maybe one of them is still in use?
14:31 < alexann> no, i've made a fresh installation and the first thing i installed is bitcoind
14:31 < newbold> ok, good
14:31 < newbold> is your node fully synced?
14:32 < alexann> it's weird it cannot bind, because it seems available (listening) 
14:32 < alexann> yes, it synced
14:32 < newbold> did you compile c-lightning yourself or get it through docker?
14:32 < alexann> through docker 
14:32 -!- CubicEarths [~cubiceart@201.206.163.235] has quit []     
14:33 < newbold> ok, hmm
14:33 < alexann> here's the command: 
14:33 < alexann> docker run --rm --name lightning --network container:bitcoind_mainnet -v /scratch/bitcoin/mainnet/bitcoind:/root/.bitcoin -v /scratch/bitcoin/mainnet/clightning:/root/.lightning --entrypoint /usr/bin/lightningd cdecker/lightningd:master --network=bitcoin --log-level=debug
14:33 < newbold> it's *possible* that it has something to do with the version in that container
14:33 < newbold> looks like you're following the guide on that one medium post, right? :)
14:34 < alexann> yes :))) 
14:34 < newbold> you have nothing to lose by blowing that docker version away and compiling locally. It's *super* easy
14:34 < alexann> i'm trying this for 3 days already :)) 
14:34 < newbold> I can walk you through it because I've done it successfully :)
14:34 < alexann> can you please help me out to do that ?? 
14:34 < alexann> I'll gladly do :) 
14:34 < newbold> sure
14:35 < newbold> actually I don't even think you need to remove the docker thing... it's separate
14:35 < newbold> so...
14:35 < newbold> start with this, which has all of your prerequisites: sudo apt-get install -y autoconf automake build-essential git libtool libgmp-dev libsqlite3-dev python python3 net-tools
14:36 < alexann> done 
14:37 < newbold> ok     
14:37 < newbold> then: git clone https://github.com/ElementsProject/lightning.git
14:37 < newbold> (if it says you don't have git, just do sudo apt-get install git)
14:37 < newbold> oh wait lol git was in the previous command, so it won't do that :P
14:37 < alexann> i know i have found even a guide on how to get it from github..but god, i just realized i have 47 open tabs trying to troubleshoot this :))) 
14:38 < newbold> heh yeah
14:38 < newbold> after it's fetched from git, just two commands: "cd lightning" and "make"
14:39 < newbold> when "make" is finished, you do: ./lightningd/lightningd --network=bitcoin --log-level=debug
14:39 < newbold> for mainnet, that is. if you want testnet, then it's network=testnet
14:41 < alexann> still working 
14:42 < alexann> what are next steps?
14:45 < redstorm> use testnet
14:45 < alexann> root@node:~/lightning# ./lightningd/lightningd --network=bitcoin --log-level=debug
14:45 < alexann> lightningd(12126): Creating lightningd dir /root/.lightning
14:45 < alexann> lightningd(12126): Trying to guess public addresses...
14:45 < alexann> lightningd(12126): Address 192.168.1.20:9735 is not routable
14:45 < alexann> lightningd(12126): Failed to connect 10 socket: Network is unreachable
14:45 < alexann> lightningd(12126): testing /root/lightning/lightningd/lightning_channeld
14:45 < alexann> lightningd(12126): testing /root/lightning/lightningd/lightning_closingd
14:45 < alexann> lightningd(12126): testing /root/lightning/lightningd/lightning_gossipd
14:45 < alexann> lightningd(12126): testing /root/lightning/lightningd/lightning_hsmd
14:45 < alexann> lightningd(12126): testing /root/lightning/lightningd/lightning_onchaind
14:45 < alexann> lightningd(12126): testing /root/lightning/lightningd/lightning_openingd
14:45 < alexann> lightningd(12126): Creating database
14:46 < alexann> lightningd(12126): HSM TRACE: Client: Received message 11 from client
14:46 < alexann> lightningd(12126): Loaded 0 invoices from DB
14:46 < alexann> lightningd(12126): HSM TRACE: Client: Received message 9 from client
14:46 < alexann> lightning_gossipd(12134): pid 12134, msgfd 12
14:46 < alexann> lightningd(12126): Loaded 0 channels from DB
14:46 < alexann> lightning_gossipd(12134): TRACE: req: type WIRE_GOSSIPCTL_INIT len 119
14:46 < alexann> lightning_gossipd(12134): TRACE: Failed to bind on 10 socket: Address already in use
14:46 < alexann> lightning_gossipd(12134): TRACE: Failed to bind on 2 socket: Address already in use
14:46 < alexann> lightning_gossipd(12134): STATUS_FAIL_INTERNAL_ERROR: Could not bind to a network address on port 9735
14:46 < alexann> lightningd: lightning_gossipd failed (exit status 131), exiting.
14:46 < alexann> :(     
14:48 < newbold> hmm     
14:48 < alexann> is there something particular that should be in bitcoin.conf ?? 
14:48 < alexann> or maybe i should exclude those ports when i run the bitcoind throough docker??
14:48 < newbold> oh maybe that's it, if bitcoind is running through docker, hmmm
14:49 < newbold> honestly not sure about docker, I've never used it :(
14:49 -!- jb55 [~jb55@184.68.162.218] has quit [Ping timeout: 240 seconds]     
14:49 < alexann> hm, can i just skip it somehow ?? 
14:50 < alexann> i mean just install the daemon from git and use the folders that already downloaded 
14:51 < alexann> blocks, chainstate, all that .... 
14:52 < newbold> I think you should be able to, yeah
14:53 < newbold> if you know where the .bitcoin directory is for docker, then you should be able to mv that over to the local .bitcoin dir in your home directory once you have it installed
14:55 < alexann> yeah the blocks are in some "scratch" folder ... but whatever, I'll try to move them once i get bitcoind and launch it for a moment just to create those folders in a new location...
14:57 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
15:01 < redstorm> @alex netstat -an | grep 9735
15:04 < redstorm> Alexann change the port you launch lightningd on as you have a docker proxy on port 9735, --port=9736
15:08 < alexann> i launched the dockered bitcoind with 9736
15:08 < alexann> and lightning returns this again: 
15:08 < alexann> ightningd(14428): Trying to guess public addresses...
15:08 < alexann> lightningd(14428): Address 192.168.1.20:9735 is not routable
15:08 < alexann> lightningd(14428): Failed to connect 10 socket: Network is unreachable
15:08 < alexann> lightningd(14428): testing /root/lightning/lightningd/lightning_channeld
15:08 < alexann> lightningd(14428): testing /root/lightning/lightningd/lightning_closingd
15:08 < alexann> lightningd(14428): testing /root/lightning/lightningd/lightning_gossipd
15:08 < alexann> lightningd(14428): testing /root/lightning/lightningd/lightning_hsmd
15:08 < alexann> lightningd(14428): testing /root/lightning/lightningd/lightning_onchaind
15:09 < alexann> lightningd(14428): testing /root/lightning/lightningd/lightning_openingd
15:09 < alexann> lightningd(14428): HSM TRACE: Client: Received message 11 from client
15:09 < alexann> lightningd(14428): Loaded 0 invoices from DB
15:09 < alexann> lightningd(14428): HSM TRACE: Client: Received message 9 from client
15:09 < alexann> lightning_gossipd(14436): pid 14436, msgfd 12
15:09 < alexann> lightningd(14428): Loaded 0 channels from DB
15:09 < alexann> lightning_gossipd(14436): TRACE: req: type WIRE_GOSSIPCTL_INIT len 119
15:09 < alexann> lightning_gossipd(14436): TRACE: Creating IPv6 listener on port 9735
15:09 < alexann> lightning_gossipd(14436): TRACE: Failed to bind on 2 socket: Address already in use
15:09 < alexann> lightningd(14428): bitcoin-cli estimatesmartfee 2 CONSERVATIVE exited with status 1
15:09 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds]     
15:22 < mlz> does c-lightning have "autopilot" like LND?
15:28 <@cdecker> mlz, not yet, but eventually we're planning to add it
15:28 <@cdecker> alexann, please use pastebin to share logs
15:28 < mlz> cdecker, oh why, it won't make nodes automatically open channels without owners' consent, right?
15:29 <@cdecker> It could, if users want to have channels maintained automatically
15:29 < mlz> it would be great if it only "connects" nodes
15:29 < mlz> ugh i wouldn't 
15:30 <@cdecker> It would be opt-in of course
15:38 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
15:40 < alexann> newbold, thank you very much for trying to help me out 
15:40 < alexann> redstorm, also thanks for your time & effort
15:49 -!- blyat [~blyat@cpe-71-71-200-3.carolina.res.rr.com] has joined #c-lightning     
15:49 -!- blyat [~blyat@cpe-71-71-200-3.carolina.res.rr.com] has quit [Remote host closed the connection]     
15:51 -!- blyat [~blyat@cpe-71-71-200-3.carolina.res.rr.com] has joined #c-lightning     
15:51 -!- blyat [~blyat@cpe-71-71-200-3.carolina.res.rr.com] has quit [Remote host closed the connection]     
16:08 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds]     
16:10 -githubby:#c-lightning- [lightning] alaniz3 opened pull request #781: Onboarding: tweak grammar conventions for RPC responses (master...improve-cli-error-responses) https://git.io/vNP65
16:23 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning     
16:35 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vNPXe
16:35 -githubby:#c-lightning- lightning/master 2c17546 practicalswift: Onboarding: Make "lightning-cli" (without arguments) output the equivalent of "lightning-cli --help; lightning-cli help"...
16:59 -githubby:#c-lightning- [lightning] alaniz3 closed pull request #781: Onboarding: tweak grammar conventions for RPC responses (master...improve-cli-error-responses) https://git.io/vNP65
17:02 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #712: Fix "lightning" typos.  Add "lightning" typo checker :-) (master...lightning-spell) https://git.io/vN2hf
17:03 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vNPMR
17:03 -githubby:#c-lightning- lightning/master 8aee381 William Casarin: doc: Nix{,OS} build instructions...
17:05 -githubby:#c-lightning- [lightning] alaniz3 opened pull request #782: Onboarding: tweak grammar conventions for RPC responses (master...fix-grammar-conventions) https://git.io/vNPMK
17:09 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #756: Disable channel when losing the underlying connection (master...disable-on-shutdown) https://git.io/vNKOt
17:20 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #773: doc: some sqlite db info for HACKING (master...db-hacking) https://git.io/vNipQ
17:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 268 seconds]     
17:26 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-nfzhuhxsqsrwhdmy] has quit [Quit: Connection closed for inactivity]     
17:30 -githubby:#c-lightning- [lightning] jb55 closed pull request #764: tests: bech32 p2wpkh funding tests (master...bech32-tests) https://git.io/vN6vY
17:44 -!- redstorm [cb56cc58@gateway/web/freenode/ip.203.86.204.88] has quit [Quit: Page closed]     
17:45 -!- lio17 [~lio17@ns350827.ip-37-187-174.eu] has quit [Quit: lio17]     
17:46 -!- lio17 [~lio17@ns350827.ip-37-187-174.eu] has joined #c-lightning     
17:48 < ebx> anyone around that could pay a testnet invoice for me? (perhaps a couple depending on how my tests go)
17:49 < mlz> ebx, can you post your invoice here?
17:49 < ebx> lntb45m1pdx4zxapp55wlxwfanz4grxxzwua2ka95e48f7ej6ksawhemmfzfvyavm6m6dqdp2w3jhxapqvehhygrnw3hhyefqd9h8get8wfshg6t0dcxqrp8vcqpxa4g2jq6dtjvww69ytx22srs6e5hn5vvrynw8uw6zlxx5ls5txcar4fl3wlrlgr4yx9684d8sgc3c37glw5c8gc24uwks94ayc8s452qqvg72ms
17:50 < mlz> i'm using LND
17:50 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection]     
17:50 < mlz>  "payment_error": "payment of 4500000000 mSAT is too large, max payment allowed is 4294967295 mSAT",
17:50 < mlz>         "payment_preimage": "",
17:50 < mlz>         "payment_route": null
17:50 < ebx> oh right, I forgot about that
17:51 < mlz> ah i think it's the same for LND too
17:51 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
17:51 < mlz> yea the max for payment is 4294967 sat
17:53 < ebx> I think one could make that payment if they had multiple channels open, right?
17:53 < ebx> in any case give me one sec I'm generating another one if you wouldn't mind trying again
18:01 < ebx> mlz, lntb1u1pdx4zmppp59y3f58rw84eh6ke57kehsekyddddn68g6s8tvx7wjyhgqttta8mqdp2w3jhxapqvehhygrnw3hhyefqd9h8get8wfshg6t0dcxqrp8vcqpxzqjvc0302qfvge5cjgl4v7he6kayeg29ue7dwdyyla8vtmt4jwvxrh2sje09pxsvr9y7ngsg62clqumqclagg03v2fe5mt9h22luh7qqvwaaaf
18:06 < mlz> woohoo
18:06 < mlz> paid thru 3 hops
18:07 < mlz> are you using clightning?
18:07 < ebx> awesome, saw it instantly and appears to have worked for me :D
18:07 < ebx> yep, c-lightning
18:07 < ebx> and thanks for the payment too
18:08 < mlz> https://paste.ee/p/Kimg9#bOoaWS90Ta6IuuSP63zglb97UXGzmZOK
18:09 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 246 seconds]     
18:09 < mlz> i'm running LND testing autopilot
18:10 < mlz> ebx, i'm curious, who do you have channels with?
18:10 < ianthius> oh man my node is so busted.
18:11 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving]     
18:11 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has joined #c-lightning     
18:12 < ianthius> does git clone https://github.com/ElementsProject/lightning.git pull from master?
18:12 < mlz> yes     
18:13 < ianthius> that's what i thouhg
18:13 < ebx> mlz, nice pic :) -- and only 3 channels open on testnet atm: https://paste.ee/p/QpUGd
18:13 < ianthius> :( looks like cdecker fix didn't fix me
18:13 < ianthius> anyone know how to get the txid of txns TO the wallet?
18:14 < ianthius> i though I saw them in the sqlite database but they don't resolve on blockchain.info...
18:17 < mlz> ebx, ah..i guess you have a channel with Birefill?
18:17 < mlz> Bitrefill *
18:18 < mlz> or one of the node you're having a channel with has a channel with Bitrefill
18:19 < ebx> yeah I'm not terrible sure tbh, I opened a single channel a while ago with a random node and the rest popped up
18:19 < ebx> could pay one more for me please: lntb1u1pdx4rmapp5k8mgf89jzel8qznkwj8q7dj404ehm9a8cpqult7l9lhr7re9968qdp2w3jhxapqvehhygrnw3hhyefqd9h8get8wfshg6t0dcxqrp8vcqpx5g5njj6na4zrcaqg26fg506gzxvz07ys3kul0hlngf94r97dgedxup24t82l2g0sa0hpueww3yupgr32slpnhn5679n6j7e8q6xknmspvglctw
18:30 -!- jojeyh [~delphi@2602:306:b8b6:b970:54f6:f913:b30f:722e] has quit [Ping timeout: 252 seconds]     
18:31 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has quit []     
18:46 -!- ccc [95a9f545@gateway/web/freenode/ip.149.169.245.69] has joined #c-lightning     
18:49 -!- ccc [95a9f545@gateway/web/freenode/ip.149.169.245.69] has quit [Client Quit]     
18:57 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
19:00 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #775: clarified --lightning-dir syntax on help (master...master) https://git.io/vNP3d
19:02 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #784: channeld: don't spam with all our attempts to commit. (master...reduce-log-spam) https://git.io/vNPQN
19:16 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 240 seconds]     
19:26 -!- Linrono [6c1f9344@gateway/web/freenode/ip.108.31.147.68] has joined #c-lightning     
19:27 < Linrono> hello there
19:27 < Linrono> i am having trouble funding a channel with clightning and i was wondering if i could get some help
19:29 -!- vitaminc [~vitaminc@pool-71-114-78-15.washdc.fios.verizon.net] has joined #c-lightning     
19:30 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Ping timeout: 252 seconds]     
19:30 -!- vitaminc_ [~vitaminc@192.5.151.254] has joined #c-lightning     
19:34 -!- vitaminc [~vitaminc@pool-71-114-78-15.washdc.fios.verizon.net] has quit [Ping timeout: 240 seconds]     
19:34 < windsok> Linrono: what's the problem
19:34 -!- vitaminc [~vitaminc@192.5.151.254] has joined #c-lightning     
19:36 < Linrono> windsok: when i am trying the fundchannel function, it errors out and i get to_self_delay 2015 larger than 432. im on the testnet and i looked at a couple of other channels they seem to only have a delay of 144. i cant seem to find how to change this variable
19:40 < windsok> hmm I'm not sure on that one sorry. Have you tried opening a channel to a different node?
19:40 -!- jojeyh [~delphi@2602:306:b8b6:b970:80:2a10:c5f5:c650] has joined #c-lightning     
19:41 < Linrono> windsok: ive tried a couple, i have been having trouble finding channels to connect to i got this one off yalls.org
19:42 < windsok> take a look at https://explorer.acinq.co/#/ it shows all the testnet nodes
19:42 < Linrono> i actually have that up already. ill just pick another one and try. the first one i tried wasnt online anymore i think
19:42 < Linrono> thanks
19:43 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning     
19:44 < Linrono> lol i tried another random node and it worked
19:44 < Linrono> thanks
19:56 < Linrono> now when trying to pay an invoice im getting an error wire_permanent_node_failure, does that sound familiar to anyone?
20:12 -!- Alex_ [~Alex@46.217.110.88] has joined #c-lightning     
20:15 -!- alexann [~Alex@77.29.86.81] has quit [Ping timeout: 240 seconds]     
20:39 -!- Linrono [6c1f9344@gateway/web/freenode/ip.108.31.147.68] has quit [Quit: Page closed]     
20:42 < newbold> ok, I've gotta figure this out
20:42 < newbold> if a channel is in the ONCHAIND_OUR_UNILATERAL state, what can I do to get my coins out of it?
20:51 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds]     
21:40 -!- bajohns [bajohns@gateway/vpn/privateinternetaccess/bajohns] has quit [Remote host closed the connection]     
22:09 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 240 seconds]     
22:25 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-mqidncykihhitkxp] has joined #c-lightning     
22:47 < newbold> is there a way to view internal c-lightning wallet data? other than listfunds?
22:53 -!- gaxl [aed30df4@gateway/web/freenode/ip.174.211.13.244] has joined #c-lightning