--- Log opened Fri Nov 16 00:00:23 2018
00:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
00:54 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:14 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
01:14 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
01:19 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
01:33 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
01:50 -!- ctrlbreak_MAD [~ctrlbreak@142.162.20.53] has joined #c-lightning
01:50 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Read error: Connection reset by peer]
01:50 -!- booyah_ [~bb@193.25.1.157] has joined #c-lightning
01:52 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]
01:53 -!- ctrlbreak [~ctrlbreak@142.162.20.53] has quit [Ping timeout: 268 seconds]
01:56 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning
02:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
02:48 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:49 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
02:58 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:12 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:28 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
03:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
03:46 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:48 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
04:27 -!- ken2812221 [~ken281222@110.50.135.219] has joined #c-lightning
04:37 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
04:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds]
05:40 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
05:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
05:42 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
05:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
06:23 -!- cltrbreak_MAD2 [~ctrlbreak@142.162.20.53] has joined #c-lightning
06:27 -!- ctrlbreak_MAD [~ctrlbreak@142.162.20.53] has quit [Ping timeout: 272 seconds]
06:30 -!- cltrbreak_MAD2 is now known as ctrlbreak
06:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
06:44 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
07:02 -!- kexkey [~kexkey@87.101.92.68] has joined #c-lightning
07:24 < ctrlbreak> Question; I have a few million SATS no longer tied up in channels on my CL node.  Is there an 'AutoPilot' like function in CL yet, so I could put it to use?  If not, any recommendations on resources I could leverage to identify a good node I could open a channel with?
07:25 < ctrlbreak> ... sorry if there is such a function and I'm just ignorant of it at the moment.  I haven't been paying as much attention as I have previously. lol.
07:26 < molz> ctrlbreak, afaik c-lightning doesn't have autopilot yet
07:27 < ctrlbreak> Ho ho!  Just noticed 0.6.2 is avail and def. recommended... I'll ensure I'm at least running something that current.
07:27 < molz> oh..
07:27 < ctrlbreak> wow... I can see why. 
07:28 < ctrlbreak> I'll pull current master and recompile now.
07:28 < ctrlbreak> back in a jiff.
07:28 < molz> i guess i should update too
07:28 < molz> v0.6.1-233-g4863e11
07:32 < ctrlbreak> lol.... at least my Dell VM server is getting a little workout this morning.
07:32 < ctrlbreak> make -j 32
07:37 < ctrlbreak> I also just noticed I have debug logging on... and have nearly 3GB of gzipped logs X-P
07:39 < ctrlbreak> Looks like I've actually been running 0.6.2 for a while....Ha!
07:39 < ctrlbreak> stats... not good :-(
07:39 < ctrlbreak> ./lightning-cli listforwards -J | jq -C . | grep failed | wc -l
07:39 < ctrlbreak> 26
07:39 < ctrlbreak> offered : 2
07:39 < ctrlbreak> settled : 7
07:41 < ctrlbreak> and I have apparently collected 7.5sats in fees X-P
07:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
07:42 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
07:43 < ctrlbreak> I have made 55/1000ths of a Canadian Peso! fascinating. lol
08:00 <@cdecker> Congrats ctrlbreak that's the most forwardings I've seen so far :-)
08:00 <@cdecker> Re autopilot: Rene is working on one and it should be included as soon as the plugin interface is done
08:10 < molz> ah... i didn't know c-lightning now has "listforwards"
08:20 -!- ken2812221 [~ken281222@110.50.135.219] has quit [Ping timeout: 244 seconds]
08:41 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
08:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
08:42 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
08:45 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
09:00 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds]
09:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
09:36 < blockstream_bot> [Tim Ho, Blockstream] I'm having an issue with someone who has a channel open with my node, and they are trying to make a payment to y'alls (mainnet) through my node.
09:37 < blockstream_bot> [Alex Bosworth, Blockstream] can you pay yalls through your node?
09:37 < blockstream_bot> [Tim Ho, Blockstream] Yes, I can
09:37 < blockstream_bot> [Alex Bosworth, Blockstream] So in theory they should be able to
09:37 < blockstream_bot> [Tim Ho, Blockstream] https://files.sameroom.io/-gR4j7-10QF05Za0YXekusxDVol-L5q23hdiHtmuk_0/image.png
09:38 < blockstream_bot> [Alex Bosworth, Blockstream] Oh well if the balance is on the correct side
09:38 < blockstream_bot> [Tim Ho, Blockstream] https://files.sameroom.io/tnfV6pH5THJJ5gcgQLd5PhWlIhHQCA5T31O1XrNmGns/image.png
09:39 < blockstream_bot> [Alex Bosworth, Blockstream] Plenty of balance on your side
09:39 < blockstream_bot> [Tim Ho, Blockstream] https://files.sameroom.io/qGl9wjFFIZIVJs7D4_it6KUP1b6f0mFsSvrMmYSaQco/-.txt
09:40 < blockstream_bot> [Alex Bosworth, Blockstream] And I’ve been forwarding payments from you in the past 24 hours
09:40 < blockstream_bot> [Alex Bosworth, Blockstream] You’ve sent me 3 forwarded payments and I’ve sent you 1 forwarded payment
09:40 < blockstream_bot> [Tim Ho, Blockstream] I'm not sure what it means that my node's "channel updates" might be not working
09:40 < blockstream_bot> [Alex Bosworth, Blockstream] I guess the person is using BLW?
09:40 < blockstream_bot> [Tim Ho, Blockstream] Yeah
09:41 < blockstream_bot> [Alex Bosworth, Blockstream] There’s an issue I know about where if the user closes their app while the channel is confirming that the channel won’t work for the user
09:41 < blockstream_bot> [Alex Bosworth, Blockstream] But afaik that only applies to LND <> BLW
09:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
09:42 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
09:43 < blockstream_bot> [Tim Ho, Blockstream] Hmm not sure
09:44 < blockstream_bot> [Alex Bosworth, Blockstream] BLW may be missing the graph information so they don’t know how to forward the payment
09:46 < blockstream_bot> [Alex Bosworth, Blockstream] Plenty of liquidity to and from ACINQ on yalls - 10 million sat on both sides
09:47 < notmike> [notmike, Blockstream] wat
09:47 < blockstream_bot> [Tim Ho, Blockstream] Let me try to get in touch with Anton
10:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
10:43 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
11:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
11:43 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
12:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
12:43 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
13:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
13:42 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
14:07 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:21 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
14:44 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
14:59 -!- charltonh [~charltonh@189.160.71.57] has joined #c-lightning
15:01 < charltonh> Hey guys.  I run the c-lightning node at https://1ml.com/node/026fe566f268b8e88512cfb8ffda1426416dde5f8bbf0badf43007165be0f2bf76
15:02 < charltonh> For some reason it is registering the IPv6 address and not the static IPv4 address it's supposed to be running on.
15:02 < charltonh> IPv6 address can no longer be found, so no one can ever connect.  I've restarted c-lightning since so I'm not sure why it hasn't at least updated the IPv6 address, but I need it to register as IPv4 anyway.
15:03 < charltonh> Couldn't find any docs on the subject regarding IPv4/IPv6 options.
15:05 < molz> charltonh, what do you put in your config?
15:05 < molz> charltonh, there's info for config here:  https://github.com/rustyrussell/lightning/blob/f496eff9c2d1b7720c59257e7b502f77351cfb78/doc/lightningd-config.5.txt#L199
15:13 < charltonh> thx molz, nothing but the basic four options are in my config file listed here https://github.com/ElementsProject/lightning
15:14 < charltonh> just my alias, rgb, port, and network=mainnet basically
15:14 < molz> charltonh, is your node uptodate?
15:14 < molz> we don't use 'port' anymore
15:19 < charltonh> Up to date as of today.  Thing is, most ISPs no longer provide static IPs.  I have my static IP because I have a VPS with Digital Ocean where I forward the ports to my machine using openvpn.
15:19 < charltonh> So I get this when I give it the address it's supposed to announce on:  STATUS_FAIL_INTERNAL_ERROR: Failed to bind on 2 socket: Cannot assign requested address
15:20 < charltonh> Gonna try 'announce-addr' 
15:22 < molz> charltonh, try 'bind-addr' too
15:23 < molz> bind-addr=xx.xxx.xx.xx:9735  #YOUR IPV4
15:23 < charltonh> Ok...
15:24 < charltonh> bind-addr doesn't work:  2018-11-16T23:24:04.304Z lightning_connectd(4347): STATUS_FAIL_INTERNAL_ERROR: Failed to bind on 2 socket: Cannot assign requested address
15:24 < charltonh> but announce-addr works!
15:25 < molz> hm bind-addr works for me
15:25 < charltonh> awesome, it worked.  1ML now is correct
15:25 < molz> nice :D
15:25 < gwillen> molz: bind-addr would not work in a port-forward situation
15:26 < molz> oh really
15:26 < gwillen> I mean, assuming it does what it sounds like
15:26 < gwillen> you have to bind an address from your local machine
15:26 < gwillen> which wouldn't work for an address being forwarded from elsewhere
15:26 < molz> gwillen, my nodes are on a VPS which have static ips, is that why bind-addr works?
15:26 < charltonh> yeah, it would not be able to BIND to that actual IP address since it's on a different machine
15:26 < gwillen> but announce-addr sounds like the right thing for this situation
15:27 < gwillen> molz: correct, bind-addr is fine if your local machine owns the IP you're using
15:27 < gwillen> the port-forward case is sort of a weird corner case
15:27 < molz> gwillen, ok, thanks, i've learned something :)
15:27 < gwillen> np!
15:27 < charltonh> Interesting.  molz on my VPS I have:
15:27 < charltonh> iptables -t nat -A PREROUTING -p tcp --dport 9735 -j DNAT --to 10.8.0.6:9735
15:27 < gwillen> I don't know much about lightning yet but I know a bunch of stuff about networks
15:27 < charltonh> iptables -t nat -A POSTROUTING -j MASQUERADE
15:28 < molz> charltonh, i have no idea you have to ask gwillen :)
15:28 < charltonh> ah ok, your node is actually running on your VPS
15:29 < charltonh> I decided to run mine on my own machine (dynamic IP) because its hella more expensive renting a VPS with any capability whatsoever
15:29 < molz> yep
15:30 < charltonh> One other question:  everytime I restart lightningd I have to chown and chmod the lightning-rpc file
15:30 < charltonh> I am running mex.dynet.com 
15:30 < molz> i'm not sure why you have to do this
15:30 < charltonh> This *MAY BE* the first realtime lightning->fiat gateway
15:31 < molz> oh really..
15:31 < charltonh> because apache cannot use lightningd since it's another user
15:31 < charltonh> well certainly the first in Mexico or Latin America, dunno about the world
15:31 < charltonh> seems someone has done it before, but if not, here it is, and it's working!
15:33 < charltonh> Anyway, sorry for the gloating.  But yeah, I have to manually chgrp and chmod the rpc file everytime I restart lightning
15:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
15:42 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
15:54 -!- booyah_ is now known as booyah
15:55 -!- sgeisler [~quassel@x8d1ee20a.agdsn.tu-dresden.de] has joined #c-lightning
15:56 < charltonh> Man... I don't get how the lightning protocol cannot do DNS lookups.  If the IP address of an LN node ever changes, ALL channels will drop and have to be re-opened?
16:08 < gwillen> I don't know how this is done in practice, but in principle channels are separate from network connections, there's no reason a channel couldn't survive a disconnect/reconnect on a different IP
16:14 < charltonh> In practice it seems you have to open all new channels
16:14 < gwillen> it seems likely to me that that will be fixed, channels are supposed to be long-lived
16:15 < gwillen> I have been able to reuse a channel from my phone to acinq over multiple days, and I assume my phone's IP changed over that time
16:15 < gwillen> so I suspect it's already the case that the "client" end of the channel can change IP and have it still reconnect?
16:17 < molz> charltonh, no, test this out with your nodes, if a node goes offline then the connection is "false" but once it goes back online the node should say "connected: true", and you don't have to close/reopen channel
16:19 < charltonh> Ok, well I noticed that when I use announce-addr=165.227.222.8 in my config, lightningd no longer seems to run properly:
16:19 < charltonh> curl 165.227.222.8:9735
16:19 < charltonh> curl: (7) Failed to connect to 165.227.222.8 port 9735: Connection refused
16:19 < charltonh> curl 127.0.0.1:9735
16:19 < charltonh> curl: (7) Failed to connect to 127.0.0.1 port 9735: Connection refused
16:20 < charltonh> So it's acting like it's running.  1ML gets the announce:  https://1ml.com/node/026fe566f268b8e88512cfb8ffda1426416dde5f8bbf0badf43007165be0f2bf76
16:20 < charltonh> But it doesn't seem to be running.
16:20 < charltonh> Maybe it's running on IPv6 or something...
16:20 < molz> hm maybe bind to the localip?
16:20 < charltonh> ah, ok thx molz lemme try that
16:23 < molz> charltonh, try '--bind-addr=0.0.0.0'
16:23 < molz> i just look in the log, rusty was discussing this a few months ago and he told someone to do that
16:23 < charltonh> Ok... yeah 127.0.0.1 didn't work
16:24 < charltonh> Seems to work!
16:25 < charltonh> Yes!  finally...
16:27 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
16:31 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Ping timeout: 260 seconds]
16:38 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
16:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
16:43 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
16:46 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:58 < molz> hm.. i guess 'bind-addr=0.0.0.0' is safe for the node? rusty? cdecker ?
17:16 < charltonh> safe?  as in not opening up security holes?
17:57 < grubles> i mean, it's listening on every interface in that case
17:58 < grubles> dunno if that's what you intend
18:47 < molz> grubles, but that's what rusty suggested to someone a few months ago
18:49 < charltonh> it's working for me for right now.
18:54 < molz> charltonh, yea it should be ok but we'll see what the devs say
18:54 < molz> here's the log :  http://gnusha.org/c-lightning/2018-05-09.log
18:55 < molz> 21:45 < rusty> CubicEarths: I think you want '--bind-addr=0.0.0.0' '--announce-addr=66.30.214.90' (assuming you're happy with default ports)
19:08 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
19:09 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:09 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
19:10 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
19:42 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
20:22 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
20:26 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Ping timeout: 240 seconds]
20:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
20:45 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
20:50 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds]
20:55 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
21:36 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-rellmfrflzdhuffb] has left #c-lightning []
21:36 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-rellmfrflzdhuffb] has joined #c-lightning
21:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
21:43 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
22:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
22:42 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
23:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
23:44 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
23:54 < gwillen> molz: assuming that what you are binding is an interface designed to be exposed to the world -- which I believe it is, right? This is the interface that outside nodes are meant to connect to? Then binding to 0.0.0.0 is safe.
23:55 < gwillen> (This is in contrast to people wanting to bind the Bitcoin RPC interface, which is designed for private internal use and is very dangerous to expose to the internet, to 0.0.0.0, which is very unsafe.)
--- Log closed Sat Nov 17 00:00:23 2018