--- Log opened Thu Oct 24 00:00:43 2019 00:02 -!- laptop_ [~laptop@194.33.98.165] has joined #lightning-dev 00:09 -!- marcoagner [~user@2001:8a0:6a5f:5700:7bb3:6296:d274:7295] has joined #lightning-dev 00:22 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lightning-dev 00:26 -!- laptop_ [~laptop@194.33.98.165] has quit [Ping timeout: 245 seconds] 00:41 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev 00:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev 00:44 -!- achow101 [~achow101@unaffiliated/achow101] has joined #lightning-dev 00:48 -!- arshbo3000 [~arshbot@99-23-136-47.lightspeed.tukrga.sbcglobal.net] has joined #lightning-dev 00:48 -!- arshbot [~arshbot@99-23-136-47.lightspeed.tukrga.sbcglobal.net] has quit [Ping timeout: 268 seconds] 00:55 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 265 seconds] 00:57 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 276 seconds] 01:01 -!- achow101 [~achow101@unaffiliated/achow101] has joined #lightning-dev 01:09 -!- kabaum [~kabaum@2001:9b1:efd:9b00::281] has joined #lightning-dev 01:11 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:c0cf:92fb:ed09:3579] has joined #lightning-dev 01:27 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:c0cf:92fb:ed09:3579] has quit [Quit: Sleep mode] 01:27 -!- laptop_ [~laptop@194.33.98.165] has joined #lightning-dev 01:40 -!- nobody123 [~nobody123@152.89.163.116] has quit [Remote host closed the connection] 01:41 -!- nobody123 [~nobody123@152.89.163.116] has joined #lightning-dev 01:41 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:c0cf:92fb:ed09:3579] has joined #lightning-dev 01:46 -!- nobody123 [~nobody123@152.89.163.116] has quit [Ping timeout: 276 seconds] 01:52 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:c0cf:92fb:ed09:3579] has quit [Quit: Sleep mode] 02:04 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lightning-dev 02:34 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:c0cf:92fb:ed09:3579] has joined #lightning-dev 02:35 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev 02:38 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds] 02:54 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Ping timeout: 252 seconds] 03:07 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has joined #lightning-dev 03:37 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lightning-dev 03:41 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:c0cf:92fb:ed09:3579] has quit [Quit: Sleep mode] 03:41 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:c0cf:92fb:ed09:3579] has joined #lightning-dev 03:42 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has joined #lightning-dev 03:48 -!- Honthe [~Honthe@s91904421.blix.com] has quit [Read error: Connection reset by peer] 04:10 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 268 seconds] 04:14 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 245 seconds] 04:15 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has quit [Quit: jonatack] 04:16 -!- jonatack_ [~jon@213.152.161.249] has joined #lightning-dev 04:16 -!- jonatack_ [~jon@213.152.161.249] has quit [Client Quit] 04:16 -!- jonatack_ [~jon@213.152.161.249] has joined #lightning-dev 04:18 -!- jonatack_ [~jon@213.152.161.249] has quit [Client Quit] 04:18 -!- jonatack_ [~jon@213.152.161.249] has joined #lightning-dev 04:21 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:c0cf:92fb:ed09:3579] has quit [Quit: Sleep mode] 04:22 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:c0cf:92fb:ed09:3579] has joined #lightning-dev 04:22 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:c0cf:92fb:ed09:3579] has quit [Client Quit] 04:42 -!- Bitcoinera [d9d8574e@217.216.87.78.dyn.user.ono.com] has joined #lightning-dev 04:47 -!- Bitcoinera [d9d8574e@217.216.87.78.dyn.user.ono.com] has quit [Remote host closed the connection] 04:51 < sword_smith> I just read this story about ZipoTm losing 4 BTC because he closed with the wrong transaction. Does anyone know why he closed with an old balance? 04:56 < sword_smith> I am referring to this article: https://news.bitcoin.com/mishap-sees-user-lose-30000-btc-on-lightning-network/ 04:59 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds] 05:03 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev 05:07 -!- Bitcoinera [d9d8574e@217.216.87.78.dyn.user.ono.com] has joined #lightning-dev 05:11 < riclas> there's a reddit thread from yesterday too. i believe he discussed the issue on slack also 05:13 < sword_smith> riclas: Thanks. Will have a look. 05:30 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lightning-dev 05:45 < lndbot> sword_smith I've seen him on the slack and discord for a while now, probably since last year. I don't know why he didn't know it's dangerous to run an older channel invalid state, but that's what he did. 05:50 < lndbot> many people would ignore the warning "don't run a backup of older state".. And since version 6 LND has SCB for recovery if you need to, now we're at version 8.. and the instructions how to do this have been available, plus no-paid volunteers are available on the slack... Why would someone still willfully run and older channel invalid state? The only answer is it's his choice and his own fault. 05:54 < lndbot> so the main problem was that he force closed all channels while being out of sync? 06:00 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds] 06:01 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds] 06:04 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev 06:13 < darosior> haluzan.rok: yes, he broadcasted outated commitments transactions, for which the remote side had private keys.. 06:17 < lndbot> oh boy, people are fuding because of all the wrong reasons. again. Is lost of funds this was necessary (as a penalization to prevent fraud) or could those outdated transactions just be rejected as invalid instead? 06:18 < lndbot> the software is agnostic of why you would run an older channel state 06:19 < sword_smith> So his lightning node was not up to date? Perhaps someone had paid him when he was away? 06:19 < darosior> haluzan.rok: If the older state was in favor of A, if B doesn't penalize A then A would have effectively stolen funds. The only workaround is B penalizing the cheater 06:20 < darosior> sword_smith: Yeah the most plausible scenario is restoring for not up-to-date backup, software force-closing with an already-reverted state, other side software taking it all 06:21 < lndbot> sword_smith his node was running lnd v0.7.1 which was up to date , that's not the issue. the issue was he had a power outage which probably corrupt his data, so his node couldn't start, he then decided to run that backup of his data which was a few days old, if you read the story on his thread 06:22 < lndbot> what he should have done if his node could not start is do a recovery which is SCB and he had the file for that, which he ran it after he already closed all his channels with the older state 06:23 < sword_smith> So he restored a state from somewhere and then decided to close the channel? I am a bit confused as to how you can end up in a situation where the other party has newer channel transactions than you have since, AFAIK, channel updates requires participation from both parties. 06:24 < lndbot> his story was a bit confusing, i think the SCB did recover the channels that didn't close but he mass closed most of his channels with the older invalid state already so SCB could not recover all his money 06:24 < sword_smith> moli: Very interesting. Thanks. I guess in these early days some gentleman-like behavior on the LN is probably, that the other party will pay him back 90 % of what he lost? I like to think that I would do that. 06:24 < sword_smith> s/probably/probable/ 06:25 < lndbot> sword_smith when he said he closed his channel with a "backup" he meant the backup he created by saving his data files in directory .lnd. With SCB, LND now creates a .backup file for you which is totally different and that's what he should have used first 06:27 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 06:28 < lndbot> makes sense. Ty for replying darosior and moli, good info. :slightly_smiling_face: 06:28 -!- rh0nj [~rh0nj@88.99.167.175] has joined #lightning-dev 06:29 < sword_smith> The issue does create a little bit of fud but the other new blockchain technologies (BTC, ETH (DAO)) have also experienced that. Haters gonna hate. 06:31 -!- jonatack_ [~jon@213.152.161.249] has quit [Ping timeout: 246 seconds] 06:31 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #lightning-dev 06:31 < sword_smith> Let's assume that he really did have corrupted data and wanted to close all channels. What would have been the correct actions to take? 06:33 < lndbot> yep, we've seen these fudsters the last few years, gotta grow thick skin by now, he posted my convo from trying to help him, so now my name is everywhere and even archive.. i'm in lightning history now.. woohoo! what else can surprise me.. lol 06:43 < darosior> sword_smith> "Let's assume that he really did have corrupted data and wanted to close all channels. What would have been the correct actions to take?" That's the big question FWIW I had this case and contacted all node owner I could identify (also tried to send bad messages but...) 06:43 < darosior> That would not happen with eltoo 06:43 < darosior> https://blockstream.com/eltoo.pdf 06:54 < lndbot> but with eltoo we still need a way to protect us from cheaters 07:00 -!- laptop_ [~laptop@194.33.98.165] has quit [Quit: Leaving] 07:15 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 07:17 -!- jonatack_ [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has joined #lightning-dev 07:20 -!- unixb0y [~unixb0y@dslb-188-098-157-136.188.098.pools.vodafone-ip.de] has quit [Quit: ZNC 1.6.5+deb1+deb9u2 - http://znc.in] 07:22 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 07:26 -!- jonatack_ [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Quit: jonatack_] 07:27 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has joined #lightning-dev 07:41 -!- thomasanderson [~thomasand@108-91-143-73.lightspeed.rlghnc.sbcglobal.net] has joined #lightning-dev 07:41 < harding> Is halseth here (via the relay)? In your email to the list, I'm confused by the need for 1 CSV. Is the design you're thinking about documented somewhere so I can look at it? I tried searching both the bolts and lnd repos, but the closest I found was https://github.com/lightningnetwork/lnd/issues/3587 , which doesn't seem to have or point to anything about needing to use CSV. 07:43 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev 07:45 -!- thomasanderson [~thomasand@108-91-143-73.lightspeed.rlghnc.sbcglobal.net] has quit [Ping timeout: 245 seconds] 08:03 < lndbot> harding: not sure what the best source would be, but I think it is first mentioned by bluematt here: https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-November/001644.html 08:03 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 08:04 < harding> johanth: that answers my question perfectly, thanks! 08:06 -!- captjakk [~captjakk@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev 08:06 -!- captjakk [~captjakk@c-65-50-169-164.hs.gigamonster.net] has quit [Read error: Connection reset by peer] 08:07 -!- captjakk [~captjakk@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev 08:14 -!- thomasanderson [~thomasand@108-91-143-73.lightspeed.rlghnc.sbcglobal.net] has joined #lightning-dev 08:16 < lndbot> sword_smith I just saw your other question "Let's assume that he really did have corrupted data and wanted to close all channels. What would have been the correct actions to take?" ==> The answer with LND now is you run the recovery by using SCB, here's the docs: https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md 08:21 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 265 seconds] 08:26 -!- thomasanderson [~thomasand@108-91-143-73.lightspeed.rlghnc.sbcglobal.net] has quit [Ping timeout: 240 seconds] 08:38 -!- llou [~textual@cm-83-97-182-195.telecable.es] has quit [Read error: Connection reset by peer] 08:41 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev 09:00 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 264 seconds] 09:07 -!- lndbot [~lndbot@138.197.213.35] has quit [Remote host closed the connection] 09:07 -!- lndbot [~lndbot@138.197.213.35] has joined #lightning-dev 09:39 -!- captjakk [~captjakk@c-65-50-169-164.hs.gigamonster.net] has quit [Remote host closed the connection] 09:45 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has joined #lightning-dev 09:46 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 09:57 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 09:59 -!- jtimon [~quassel@22.133.134.37.dynamic.jazztel.es] has joined #lightning-dev 10:13 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 10:13 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has quit [Ping timeout: 276 seconds] 10:14 -!- afk11` is now known as afk11 10:23 < sword_smith> Does the Bolt protocol specify if you can pay your own invoices? I mean: Can a lightning node pay invoices that it generated itself? 10:23 < sword_smith> I am using c-lightning FYI :) 10:24 < lndbot> Sure you can pay your own invoices 10:24 < lndbot> Why do you want to do that? 10:25 < sword_smith> alexbosworth: But paying them requires that there is a cycle in my graph of connections, right? :) 10:26 < lndbot> Well you can pay out and in with the same peer if you really want 10:27 < sword_smith> alexbosworth: Currently I get: '{ "code":205, "message": "Could not find a route" }' when I try to pay my own invoice. 10:27 < lndbot> I think that speaks more to the implementation than the protocol limitations 10:28 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has joined #lightning-dev 10:29 < sword_smith> alexbosworth: I see. I have three open outgoing channels (where I have a positive balance). Any idea on how I can get others to open testnet channels to me? 10:31 < lndbot> Why do you want them to open channels to you? 10:32 < sword_smith> alexbosworth: I am testing payments from htlc.me -- that I register ingoing payments correctly. I currently I cannot receive from htlc.me 10:32 < lndbot> Ah I can make a channel to you from htlc.me, what is your node details? 10:34 < sword_smith> alexbosworth: I am on 03ac388eaf01314c302d9469b1c291b95702276ad5d6c32ab40fc59677dff4329d 10:41 < lndbot> I don't have your ip and you aren't peered with me 10:41 < sword_smith> alexbosworth: PM? 10:42 < lndbot> You could try Lightning Loop, make a channel to htlc.me and then do Loop Out to get inbound liquidity from htlc.me 10:42 < lndbot> I'm not on IRC, I'm using a bridge 10:42 < sword_smith> alexbosworth: I know :) How do I send you a PM, is that possible? 10:44 < sword_smith> alexbosworth: https://pastebin.com/y0JxAtTE 10:45 < lndbot> oh we have a channel and in clightning I cannot make a channel to you 10:45 < lndbot> if you close the channel I can make one 10:45 < sword_smith> alexbosworth: Then why cannot HTLC send payments to me? 10:46 < lndbot> because the balance is on your side since you made the channel 10:46 < sword_smith> alexbosworth: Sure, I can close the channel to 03c856d2dbec7454c48f311031f06bb99e3ca1ab15a9b9b35de14e139aa663b463 10:46 < sword_smith> alexbosworth: Done. The channel is closed. 10:47 < lndbot> I get an error when I try to connect to you 10:47 < sword_smith> alexbosworth: Did you notice the alternative port? 10:47 < lndbot> ah ok 10:48 < lndbot> ok opening 10:49 < sword_smith> alexbosworth: Thanks a lot! Which protocol are you chatting on, Slack? 10:49 < lndbot> Yeah LND developer slack 10:49 < sword_smith> I see the channel being opened. Much appreciated. 10:49 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev 10:51 < sword_smith> alexbosworth: Just to be sure we are on the same page: Once this channel is opened, I should be able to pay invoices generated by me through the htlc.me web site, right? Even with this alternative port? 10:51 < lndbot> sure 11:25 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection] 11:26 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #lightning-dev 11:35 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 11:35 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #lightning-dev 11:48 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 11:57 -!- reallll [~belcher@unaffiliated/belcher] has joined #lightning-dev 11:59 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 11:59 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #lightning-dev 12:01 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 12:01 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 268 seconds] 12:10 -!- reallll is now known as belcher 12:11 -!- noxx [~noxx@p200300E617215E00649BA022975A0EC8.dip0.t-ipconnect.de] has joined #lightning-dev 12:11 -!- noxx [~noxx@p200300E617215E00649BA022975A0EC8.dip0.t-ipconnect.de] has quit [Client Quit] 12:21 -!- kabaum [~kabaum@2001:9b1:efd:9b00::281] has quit [Ping timeout: 245 seconds] 12:46 -!- Bitcoinera [d9d8574e@217.216.87.78.dyn.user.ono.com] has quit [Ping timeout: 260 seconds] 12:50 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 12:51 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 13:08 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has quit [Remote host closed the connection] 13:12 -!- captjakk_ [~captjakk@c-24-72-155-6.ni.gigamonster.net] has joined #lightning-dev 13:29 -!- captjakk_ [~captjakk@c-24-72-155-6.ni.gigamonster.net] has quit [Remote host closed the connection] 13:29 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has joined #lightning-dev 13:34 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has quit [Ping timeout: 245 seconds] 13:34 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has joined #lightning-dev 13:35 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has quit [Remote host closed the connection] 14:02 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has joined #lightning-dev 14:03 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has quit [Remote host closed the connection] 14:05 -!- captjakk_ [~captjakk@c-24-72-155-6.ni.gigamonster.net] has joined #lightning-dev 14:05 -!- captjakk_ [~captjakk@c-24-72-155-6.ni.gigamonster.net] has quit [Client Quit] 14:06 -!- nobody123 [~nobody123@152.89.163.116] has joined #lightning-dev 14:21 < BlueMatt> johanth: how does your proposal change anything? 14:21 < BlueMatt> also, this bridge is super duper obnoxious, breaks all tab completion 14:22 < BlueMatt> changing the size limitation wouldnt change it (and would make reasoning about it much more complex on the bitcoin core mempool size, I think) 14:26 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has joined #lightning-dev 14:33 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e54a:392d:cc0a:581e] has joined #lightning-dev 14:33 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 14:36 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 15:05 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds] 15:10 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e54a:392d:cc0a:581e] has quit [Quit: Sleep mode] 15:27 -!- nsh [~lol@wikipedia/nsh] has quit [Quit: ZNC - http://znc.in] 15:44 -!- nsh [~lol@wikipedia/nsh] has joined #lightning-dev 15:45 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 15:52 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #lightning-dev 15:53 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection] 15:53 -!- marcoagner [~user@2001:8a0:6a5f:5700:7bb3:6296:d274:7295] has quit [Ping timeout: 250 seconds] 16:11 -!- Bitcoinera [4f9bd400@0.red-79-155-212.dynamicip.rima-tde.net] has joined #lightning-dev 16:11 -!- Bitcoinera [4f9bd400@0.red-79-155-212.dynamicip.rima-tde.net] has quit [Remote host closed the connection] 16:43 -!- farmerwampum [~farmerwam@195.206.105.7] has quit [Ping timeout: 276 seconds] 16:47 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev 16:55 -!- captjakk [~captjakk@c-24-72-155-6.ni.gigamonster.net] has quit [Remote host closed the connection] 16:56 -!- farmerwampum [~farmerwam@195.206.105.52] has joined #lightning-dev 17:13 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 17:37 -!- jtimon [~quassel@22.133.134.37.dynamic.jazztel.es] has quit [Quit: gone] 17:42 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev 17:58 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 265 seconds] 18:07 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has quit [Ping timeout: 265 seconds] 18:39 -!- thomasanderson [~thomasand@108-91-143-73.lightspeed.rlghnc.sbcglobal.net] has joined #lightning-dev 18:43 -!- thomasanderson [~thomasand@108-91-143-73.lightspeed.rlghnc.sbcglobal.net] has quit [Ping timeout: 245 seconds] 19:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 276 seconds] 19:49 -!- captjakk [~captjakk@174-16-221-137.hlrn.qwest.net] has joined #lightning-dev 20:06 -!- thomasanderson [~thomasand@108-91-143-73.lightspeed.rlghnc.sbcglobal.net] has joined #lightning-dev 20:11 -!- thomasanderson [~thomasand@108-91-143-73.lightspeed.rlghnc.sbcglobal.net] has quit [Ping timeout: 268 seconds] 20:30 -!- captjakk [~captjakk@174-16-221-137.hlrn.qwest.net] has quit [Remote host closed the connection] 20:32 -!- captjakk [~captjakk@174-16-221-137.hlrn.qwest.net] has joined #lightning-dev 21:02 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Read error: Connection reset by peer] 21:03 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #lightning-dev 21:39 -!- captjakk [~captjakk@174-16-221-137.hlrn.qwest.net] has quit [Remote host closed the connection] 23:03 -!- kabaum [~kabaum@2001:9b1:efd:9b00::281] has joined #lightning-dev 23:54 -!- Stadicus [~stadicus@8.182.132.164.rdns.lunanode.com] has joined #lightning-dev 23:56 -!- Stadicus [~stadicus@8.182.132.164.rdns.lunanode.com] has left #lightning-dev [] --- Log closed Fri Oct 25 00:00:44 2019