--- Day changed Sun May 13 2018 00:10 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 00:10 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 00:14 -!- vogelito [~Adium@189.134.38.218] has quit [Quit: Leaving.] 01:13 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 01:13 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 01:17 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 01:18 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 01:40 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 01:41 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 01:42 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 01:43 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 01:44 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 01:45 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 01:47 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 01:49 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 01:50 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 01:51 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 01:54 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 01:54 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 01:55 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 01:56 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 01:56 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 01:58 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 01:59 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:00 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:00 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:02 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:03 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:06 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:08 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:09 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:11 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:12 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:13 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:15 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:15 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:18 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:18 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:20 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:21 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:23 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:24 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:36 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:38 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:40 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:41 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:44 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:44 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:45 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:46 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:49 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:50 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:54 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:54 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:57 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 02:57 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 02:59 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:00 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:01 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:03 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:05 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:06 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:08 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:08 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:10 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:11 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:15 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:15 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 03:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 03:20 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:21 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:23 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:24 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:26 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:26 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:29 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:29 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:33 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:34 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:35 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:36 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:39 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:40 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:45 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:45 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:47 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:48 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:53 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:55 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 03:56 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 03:58 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 04:01 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 04:05 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 04:46 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 05:10 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 268 seconds] 05:14 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:33 -!- simlay1 [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds] 05:44 -!- simlay1 [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 05:54 -!- tiagotrs [~user@p5DC47C29.dip0.t-ipconnect.de] has joined #c-lightning 05:54 -!- tiagotrs [~user@p5DC47C29.dip0.t-ipconnect.de] has quit [Changing host] 05:54 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 06:00 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 268 seconds] 06:07 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-sqqojfnxqstyjuts] has joined #c-lightning 06:16 -!- deusexbeer [~deusexbee@080-250-075-194-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 256 seconds] 06:17 -!- deusexbeer [~deusexbee@093-092-176-087-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 06:30 < ctrlbreak> vogelito: Thanks for sharing what you found. We need more people actively discussing troubleshooting, that's for sure. 07:15 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 07:15 -!- arowser_ [~arowser@45.32.248.113] has joined #c-lightning 07:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 07:20 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 08:17 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-sqqojfnxqstyjuts] has quit [Quit: Connection closed for inactivity] 10:14 -!- tiagotrs [~user@p5DC47271.dip0.t-ipconnect.de] has joined #c-lightning 10:14 -!- tiagotrs [~user@p5DC47271.dip0.t-ipconnect.de] has quit [Changing host] 10:14 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 10:14 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 10:16 < StopAndDecrypt> question about backups 10:16 < StopAndDecrypt> i know the node can end up posting old states, but you still need to backup the wallet to recover to begin with 10:17 < StopAndDecrypt> so just the /wallet/ folder is sufficient for that? 11:01 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 11:07 < molz> StopAndDecrypt, did you see the link vogelito posted? a dev explains if you should use a backup 11:26 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1498: Do not use potentially uninitialized value needed_dns (master...needed_dns) https://git.io/vp9BG 11:41 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1499: wireaddr: Make sure addrstr fits the largest possible addrlen (master...addrlen-size) https://git.io/vp9RT 11:41 < molz> StopAndDecrypt, https://github.com/ElementsProject/lightning/issues/1156#issuecomment-370131797 11:49 -githubby:#c-lightning- [lightning] practicalswift closed pull request #1499: wireaddr: Make sure addrstr fits the largest possible addrlen (master...addrlen-size) https://git.io/vp9RT 12:06 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1500: wireaddr: Avoid buffer overflow in fmt_wireaddr_without_port() (master...fmt_wireaddr_without_port) https://git.io/vp903 12:09 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 12:17 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 12:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 13:10 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 256 seconds] 13:44 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 13:48 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 13:50 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 13:51 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 14:04 -!- tiagotrs [~user@p5DC47528.dip0.t-ipconnect.de] has joined #c-lightning 14:04 -!- tiagotrs [~user@p5DC47528.dip0.t-ipconnect.de] has quit [Changing host] 14:04 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 14:43 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 14:44 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 14:44 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 14:46 -!- amp__ [~amp@24.136.5.183] has quit [Ping timeout: 240 seconds] 15:22 < StopAndDecrypt> molz, thanks, just hsm_secret, but do i need to back that up after every channel opening or does that use some sort of HD system where i only need to back that up once? 15:26 < molz> StopAndDecrypt, i'm not sure, but afaik a backup is not recommended for lightning 15:26 < StopAndDecrypt> yes im aware, i just care about not losing my money... 15:26 < StopAndDecrypt> so, if my pc fails, i need to save the keys 15:27 < molz> i think it's explained how to recover the keys in that thread but i haven't tried this with c-lightning 15:27 < StopAndDecrypt> it does, my question is does it use an HD system for opening new channels or do i have to back up that file every time i open a new channel 16:02 < molz> hm i'm not sure if that can work with c-lightning without the danger that if you happen to run a backup you can lose all your money 16:03 < molz> because the backup is an old state 16:07 -!- arowser_ [~arowser@45.32.248.113] has quit [Remote host closed the connection] 16:28 < tigermousr> i am trying to test using the coinpanic community coinjar. I can make deposits, but when I try to withdraw, it says there is no route. I have two funded channels open but my ip address is not shown on 1ml. Is that required to receive payments? 16:29 < roasbeef> tigermousr: explorers are useless 16:31 < tigermousr> fair enough. but if i can make a payment to coinpanic, but they can't make one back - does that sound like an issue with me broadcasting my ip address? is there another way to test if i can receive payments? 16:34 < tigermousr> Payment Error: unable to route payment to destination: TemporaryChannelFailure(update=(*lnwire.ChannelUpdate) 16:35 < molz> tigermousr, is your node running c-lightning? 16:36 < tigermousr> yes, built from master yesterday 16:37 < tigermousr> had some trouble with a unilateral channel close and I have just been able to make a first test payment today 16:46 < roasbeef> nah not related to an ip address, they just might have some issues on their end tigermousr 17:10 < tigermousr> ok, thanks 17:28 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 265 seconds] 17:53 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 17:58 < tigermousr> so, in follow up. is there anything i can do to make the route work? I can see that another user was able to make a withdrawal after I made a deposit... so it appears to be purely routing issue. 18:00 < roasbeef> tigermousr: the other day i couldn't even get it to give an invoice, so it might have intermitent issues? dunno 18:01 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 240 seconds] 18:33 < molz> tigermousr, do you have a channel with another node? 18:34 < tigermousr> yeah, I have two funded channels open with state 'CHANNELD_NORMAL' 18:43 < molz> tigermousr, from the same node or you have two nodes? 18:43 < molz> afaik c-lightning doesn't allow multiple channels on a node 18:45 < tigermousr> two nodes 18:48 < molz> tigermousr, there might be an interop issue or something between his node and your node, i'm just wondering if you open a channel with another node that has a channel and liquidity with coinpanic, you might be able to get paid by coinpanic 18:49 < molz> i don't have a channel with coinpanic but i'm able to send and receive from coinpanic because i have a bunch of channels with other nodes 18:49 < molz> and actually only about 3 of those channels provide the routes for me 19:03 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1501: wire: remove --check-alignment arg from spec parsing tool. (master...remove-spec-alignment-checks) https://git.io/vp9Xc 19:05 < molz> tigermousr, or you could try to open a channel between your two nodes and see if it can work 19:08 -!- simlay1 [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 19:08 -!- simlay1 [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 19:22 < tigermousr> i went back and reread you question molz, and my incorrect response... I have two funded channels from my one node. i will close one and try again. seems odd that lightning-c only allow one channel per node - what if that one node i'm connected to goes down? 19:25 < molz> i think the devs have plan to change this, but idk for sure 19:25 < molz> tigermousr, i don't think you have two channels on the same node, probably one channel is stale/closed 19:26 < molz> or maybe you have two channels with two different nodes 19:26 < tigermousr> two channels with two different nodes, is what i mean 19:35 < molz> ah ok 19:35 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 19:52 -!- antanst [~antanst@62.169.219.213] has quit [Ping timeout: 250 seconds] 19:53 -!- antanst [~antanst@62.169.219.213] has joined #c-lightning 19:59 < molz> tigermousr, also, there's a rule for a reserve amount of 1% of the channel capacity, unless you have paid coinpanic more than this amount, you can't get paid back 20:00 < molz> for example, if you open a channel with 1200000 satoshis, your reserve is 12000 satoshis, and you've sent coinpanic only 5000 satoshi, you can't ask to be paid back yet, you only get back amount over 12000 satoshis 20:06 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 20:07 < tigermousr> in my case i opened a channel with coinpanic for 100000sat. i made an initial payment of 100 sat. then another of 1000 sat. so this seems to cover the reserve element. the response on coinpanic remains 'unable to route payment to destination' 20:12 < molz> then it must be some other issue 20:15 < molz> tigermousr, and your invoice was for 100 sat or 150 sat? 20:15 < tigermousr> 150sat 20:15 < molz> ah, that explains it 20:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 20:16 < molz> you can only ask back 100 sat minus a fee maybe 1 sat 20:22 < tigermousr> just tried an invoice for 100sat and 10sat. same network issue. 20:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:53 -!- CubicEarths [~cubiceart@ool-44c11be6.dyn.optonline.net] has joined #c-lightning 21:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 21:33 < molz> tigermousr, i said hi to you here: https://www.coinpanic.com/Lightning/CommunityJar :) 21:52 < tigermousr> thanks. 23:30 -!- ctrlbreak [~ctrlbreak@fctnnbsc38w-47-55-95-227.dhcp-dynamic.fibreop.nb.bellaliant.net] has quit [Ping timeout: 255 seconds] 23:31 -!- ctrlbreak [~ctrlbreak@fctnnbsc38w-47-55-95-227.dhcp-dynamic.fibreop.nb.bellaliant.net] has joined #c-lightning