--- Log opened Mon Mar 18 00:00:19 2019 00:13 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 00:31 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Remote host closed the connection] 00:34 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #lightning-dev 00:53 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev 01:15 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 268 seconds] 01:19 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev 01:35 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev 02:06 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev 02:14 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #lightning-dev 02:14 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 268 seconds] 02:23 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Remote host closed the connection] 02:24 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #lightning-dev 02:24 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 02:25 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev 02:27 -!- mode/#lightning-dev [+o rusty] by ChanServ 02:28 -!- rusty changed the topic of #lightning-dev to: Bitcoin Lightning Network Development: Be Excellent To Each Other! Logging at http://gnusha.org/lightning-dev/ Next Meeting: https://github.com/lightningnetwork/lightning-rfc/issues/588 02:28 -!- mode/#lightning-dev [-o rusty] by rusty 02:40 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 244 seconds] 02:54 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev 03:12 -!- shesek [~shesek@unaffiliated/shesek] has joined #lightning-dev 03:25 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 03:25 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev 03:26 -!- jungly [~quassel@host97-200-static.8-79-b.business.telecomitalia.it] has joined #lightning-dev 03:28 -!- melvin_ [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lightning-dev 03:44 -!- DavidMitchell[m] [davidfedii@gateway/shell/matrix.org/x-qjkshmqekinkvjbt] has joined #lightning-dev 04:09 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 04:54 -!- khs9ne_ [~guido@unaffiliated/mn3monic] has joined #lightning-dev 05:08 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 05:08 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev 05:45 -!- riclas [riclas@148.63.37.111] has joined #lightning-dev 06:03 -!- khs9ne_ [~guido@unaffiliated/mn3monic] has quit [Remote host closed the connection] 06:43 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 252 seconds] 07:01 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #lightning-dev 07:11 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Remote host closed the connection] 08:50 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Quit: Leaving] 08:57 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 246 seconds] 09:02 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 246 seconds] 09:02 -!- StopAndDecrypt_ [~StopAndDe@173.254.208.58] has joined #lightning-dev 09:07 -!- StopAndDecrypt [~StopAndDe@94.242.238.73] has joined #lightning-dev 09:07 -!- StopAndDecrypt [~StopAndDe@94.242.238.73] has quit [Changing host] 09:07 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #lightning-dev 09:07 -!- StopAndDecrypt_ [~StopAndDe@173.254.208.58] has quit [Ping timeout: 246 seconds] 09:11 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 246 seconds] 09:12 -!- StopAndDecrypt [~StopAndDe@206.189.169.41] has joined #lightning-dev 09:12 -!- StopAndDecrypt [~StopAndDe@206.189.169.41] has quit [Changing host] 09:12 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #lightning-dev 09:29 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 09:49 -!- Prolac [~prolac@unaffiliated/prolac] has joined #lightning-dev 09:50 < Prolac> hi, one question, If I want to receive payment through LN, do I have to have equal amount of my own funds locked in the receiving channel? 09:57 < lndbot> No 09:58 < Prolac> how much incoming liquidity do I need to have then? 09:59 < lndbot> Just more than you want to receive, channels are designed for repeat usage not one-off sends and receives 10:00 < Prolac> so If I want to receive 1BTC I need to already have at least 1BTC? 10:01 < lndbot> duh 10:01 < lndbot> No 10:02 < lndbot> btc is free like free speech, right? 10:02 < kanzure> meeting time? 10:02 < lndbot> oh .. i'll be quiet :) 10:03 < Prolac> alex: I'm not sure I understand then, you said that I need to have more than I want to receive, what am I missing? 10:03 < kanzure> whoops, timezone problems 10:03 < lndbot> Incoming liquidity is not your money 10:05 < Prolac> oh I see, but it has to be in the channels I used? 10:06 < lndbot> Someone has to have it, but not you 10:07 < molz> Prolac, if you want to receive, have the sender to open a channel to your node, if routing is too complicated for you to comprehend 10:08 < molz> and in my opinion, that should be the basic explanation to newbies who aren't familiar with ln yet 10:08 < Prolac> hmm why was it problematic for Lightning torch to go through then and it was only around $150? 10:08 < molz> because most people don't have much money in their nodes 10:09 -!- jungly [~quassel@host97-200-static.8-79-b.business.telecomitalia.it] has quit [Remote host closed the connection] 10:09 < molz> i was offered by Koala to take the torch from him but I declined because i didn't have that much money on my node, and why? because im not stupid to risk my btc at this stage of lightning 10:09 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 10:10 < lndbot> There are some arbitrary safety limits designed larger value sends impractical at the moment 10:10 < Prolac> what do you mean, you said that receiver doesn't have to have the same amount of money he is receiving, the whoe capacity of channels is 1000 BTC or so, why was the problem to receive $150 then? 10:10 < Prolac> It seems I'm not understanding the concept properly 10:11 < lndbot> Even if you don’t have the funds someone else has to have them 10:13 < Prolac> so noone on the whole LN had $150 at the time? 10:13 < molz> you have the limit of your channel capacity 10:13 < lndbot> The person you are peered with has to have the money not anyone on the network 10:13 < molz> if your channel capacity has 1650000 satoshis, you can't receive more than that 10:14 < molz> and the torch at the time was about 3000000 sat or something 10:14 < Prolac> and the channel can be consisted of only two people right? 10:17 < lndbot> At the moment yes 10:17 < lndbot> More people has other trade offs and is more complicated to implement 10:21 < Prolac> ok, so why was molz unable to receive the LN torch then? 10:36 < Prolac> why was sender unable to open direct channel with molz and send the torch? 10:38 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev 10:38 < molz> Prolac, because Koala and I didn't have a channel with each other, I guess he could've sent to me and I could've forwarded the torch but I didn't want him to have to do this and wait for the channel to open 10:39 < molz> in order for him to send to me he would've had to open a channel to me or i would've had to open a channel to him with a push_amt as the liquidity for him to send the torch to me 10:40 < molz> we're talking about cryptographic transactions here, not cash app or paypal 10:41 < Prolac> and why was it a problem for him to open a channel with you? Isn't that how its supposed to work, you open a channel with a person you want to transact with, lock the btc and send it over to him? 10:42 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev 10:42 < molz> because i didn't want him to have to open a channel with me when there were other people waiting who would take the torch right then 10:45 < Prolac> lol, I don't see why was that such a big deal then, so the receiver can receive any amount (without owning any money previously) if the sender opens direct channel with him? 10:47 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #lightning-dev 10:48 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 246 seconds] 10:50 < lndbot> It’s not a big deal, maybe people are surprised to learn that channels are designed for lower value more frequent sends not higher value less frequent sends 10:52 < molz> Prolac, no it's not a big deal but to answer your question hmm why was it problematic for Lightning torch to go through then and it was only around $150? 10:52 < molz> because LN has rules and limits 11:11 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 272 seconds] 11:15 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #lightning-dev 11:24 -!- belcher [~belcher@unaffiliated/belcher] has joined #lightning-dev 11:30 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Remote host closed the connection] 11:58 -!- hiroki [a331ce08@gateway/web/freenode/ip.163.49.206.8] has joined #lightning-dev 11:58 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev 12:01 < rusty> Meeting time! roasbeef aj bitconner BlueMatt cdecker niftynei pm7 rusty and anyone I missed... 12:02 < rusty> #startmeeting 12:02 < lightningbot> Meeting started Mon Mar 18 19:02:14 2019 UTC. The chair is rusty. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:02 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 12:02 < kanzure> hi 12:02 < rusty> #info https://github.com/lightningnetwork/lightning-rfc/issues/588 12:02 < Chris_Stewart_5> Might be sparsely attended for US folks since we had our daylight savings last week 12:03 < rusty> Agenda is suspiciously light... Ah, thanks Chris_Stewart_5, we're going to hit a second DST event soon when I move off DST, as well. 12:03 < Chris_Stewart_5> wall clock time is an hour later for us now 12:03 < rusty> Then errors should cause people to be bright and early, which is better than coming in at the end! 12:03 -!- sstone [~sstone_@185.186.24.109.rev.sfr.net] has joined #lightning-dev 12:04 < rusty> sstone: hi! 12:04 < sstone> hi! 12:04 < lndbot> hi :slightly_smiling_face: 12:04 -!- cARdkEf [1facece8@gateway/web/freenode/ip.31.172.236.232] has joined #lightning-dev 12:04 < niftynei> hello! 12:05 < rusty> roasbeef suggested we split up option_simplified_commitment, and I posted that to the ML. I think I actually have implemented it already (except I need to use the new feature bit). I have also started implementing the extended gossip queries. 12:05 < rusty> Since cdecker is at a fireside chat instead, seems a productive place to start. 12:06 < rusty> Anyone have any feedback on the concept of option_static_remotekey as I called it? 12:07 < rusty> https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-March/001911.html 12:08 < rusty> The only caveat is that we may end up renaming option_simplified_commitment into option_bring_your_own_fees, since that's what's left (and we may make it require or imply option_static_remotekey to avoid testing all options). 12:09 -!- nickler [~nickler@159.69.205.219] has joined #lightning-dev 12:09 < sstone> we like option_static_remotekey too. we've already started implementing "simplified commitment tx" and should be able to extract what is needed. 12:10 < rusty> sstone: great; yeah, it is kind of the easy part. I guess the debate was whether to include symmetric CSV delays under that feature, but it was easy to implement and related, so I chose to. 12:11 < sstone> Yes I think we need to 12:11 < rusty> sstone: sorry I have been remiss on implementing the gossip enhancements, but I finally started last night and it was *really easy*, so I expect quick progress from here. I'll test my node against yours today. 12:12 < sstone> we'll add test vectors (in JSON format :)) 12:12 < rusty> sstone: I need to get back to that, yes.... so much to do, so little time! 12:13 < rusty> Anyone else have things to bring up, otherwise a short meeting is a good meeting? Though I think roasbeef and bitconner are sleeping :) 12:14 < rusty> BTW: we have an intern Joe making progress generating the Million Channels Project, and it's caused me to have to actually implement some optimizations so it doesn't take forever to benchmark, let alone give decent results so that's been my 2 weeks... 12:15 < sstone> I've add a look at Christian's proposal for "framing" the onion and I think it's quite nice and simple but maybe pointless to discuss without him and roaseef ? 12:15 < rusty> sstone: yes, agreed. I like it too, but I want them to sort it out :) 12:17 < sstone> yes :) did you have time to check the test vectors for the CLTV-based sorting of HTLCs ? 12:17 < rusty> #action rusty to check CLTV-sorting HTLC vectors 12:19 < rusty> Three minor notes: 1. I've created a tag for "Next Meeting" for people to note stuff they want to raise; I'll clear it from all issues at the end of each meeting, rahter than a specific per-meeting tag. Please use. 2. DST is going to move 7 April, so the meeting will move +1 hr again then (that's *not* nxt meeting, but the following). 3. Mailing list is movign to groups.io, you don't need to do anything if you want to be subsc 12:19 < rusty> ribed to the new one. 12:19 <+roasbeef> static key FTW 12:19 <+roasbeef> reading mail for the first time now ;) 12:19 < rusty> roasbeef: cool :) 12:20 < rusty> roasbeef: gives us more breathing room with standardness rules etc for bitcoin propagation. 12:20 <+roasbeef> i also have a few things to add to the DLP section bsaed on some work we've done in lnd within that area, some recovery edge cases 12:20 <+roasbeef> def 12:21 <+roasbeef> what time zone do we base the meeting off rn? AU? 12:21 <+roasbeef> DST happened in teh us already 12:21 <+roasbeef> is the groups.io interface very diff than the old linux foundation one? 12:21 < rusty> roasbeef: great. Yes, it's in a link in the issue https://github.com/lightningnetwork/lightning-rfc/issues/588 and I always update it. 12:21 <+roasbeef> also what will happen to the existing archives? 12:22 < rusty> roasbeef: I believe the existing archives will be maintained, though I'll be seeking a mirror just in case. 12:22 < rusty> roasbeef: groups.io put an obnoxious tailer on messages with unsubscribe links etc, but that seems to be about it. 12:23 <+roasbeef> gotcha, was google groups out of the question? 12:23 <+roasbeef> jw 12:24 < rusty> roasbeef: LF are migrating all lists to groups.io; I have a real, active, listserver we could have moved to (lists.ozlabs.org) which hosts some non-trivial lists, but since they're doing this for us, I thought it the easiest path. 12:25 < rusty> OK, unless people have other issues to discussion, I'm going to end meeting? 12:27 < rusty> #endmeeting 12:27 < lightningbot> Meeting ended Mon Mar 18 19:27:02 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 12:27 < lightningbot> Minutes: http://www.erisian.com.au/meetbot/lightning-dev/2019/lightning-dev.2019-03-18-19.02.html 12:27 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/lightning-dev/2019/lightning-dev.2019-03-18-19.02.txt 12:27 < lightningbot> Log: http://www.erisian.com.au/meetbot/lightning-dev/2019/lightning-dev.2019-03-18-19.02.log.html 12:27 < rusty> That was easy :) 12:27 <+roasbeef> heh, i'm behind on stuff right now unfortunately, will try to catch up by the next meeting 12:28 <+roasbeef> there're some network level issues we're seeing on the lnd side partially due to the larger influx of channels, and instability of network connections to due large backlogs when gossip timestamps are applied to peers 12:29 < sstone> you mean peers setting a filter timestamp way back in the past ? 12:29 <+roasbeef> that, but just also in the past our or so 12:29 <+roasbeef> so it amplifies kinda 12:29 <+roasbeef> ends up sending 10s of thousands of backlogged messages, but we have write timeouts in place to not block writing for ever, the connection dies, and the whole thing restarts 12:30 <+roasbeef> the 1970 thing makes it worse, but it's still present 12:30 < rusty> roasbeef: I know the feeling, I keep saying "next week"... c-lightning *still* asks for all the gossip because it hasn't hit top of my todo. But fixing that would make everyone's life a bit nicer. 12:30 <+roasbeef> it's seen one a fresh restart, but then evens out after the node has been up for a while 12:30 <+roasbeef> on a* 12:30 <+roasbeef> we have a change coming to only start to sync updates from 3 (configurable) peers 12:31 <+roasbeef> so it lessens the load a bit as well, and doesn't hit the worst case of all peers asking since 1970 all at once 12:31 < sstone> we do sthg similar on the mobile app 12:31 <+roasbeef> then we'll rotate them after a bit, asking for a fresh sync to catch older channels (fresh and in query short chan) 12:32 <+roasbeef> there's also zombie chrun going on in mainnet rn, it happend on testnet a bit back 12:32 <+roasbeef> another cycle of peers broadcasting older chans we've deemed to be zombies, but we re-add, then broadcast and prune again, only to hear about again later 12:32 <+roasbeef> we have another fix to just start to mark them with tombstones so we'll never accept 12:32 <+roasbeef> i think eclair will cache until it knows they aren't zombies 12:33 < sstone> it seems that there was an issue with LNBig (?) lots of new channels that got closed pretty quickly, and lots of flapping channels 12:33 <+roasbeef> closed why? 12:33 <+roasbeef> i'm not quite sure what they're doing anymore at this point tbh 12:34 < sstone> don't know. apparently not by them but by their peers 12:34 <+roasbeef> our next release will fix much of the flappy channels and enable/disable spam 12:34 <+roasbeef> so things should be more placid afterwards ;) 12:34 < sstone> we check announcements against the blockchain, don't propagate zombie messages and just stop listening when a peers sends up too many zombie messages 12:35 <+roasbeef> but also personally has had me up the prio on our end to add more active DoS scoring/detection, and really start to de-prio gossip in the protocol all together 12:35 < sstone> having gossip messages on a separate connection would be nice 12:36 < sstone> it should be doable without adding a specific extra port 12:39 <+roasbeef> internally we de-prio gossip when writing out queues now 12:39 <+roasbeef> or just yank it out all together ;) 12:40 <+roasbeef> i'd say we prob reached this # of chans sooner than I anticiapted 12:40 <+roasbeef> from my findings, many of these new ones are also super tiny channels (like 20k) put up to maybe make their node look more attractive on "explorers"? (look i haz lots of connections) 12:41 <+roasbeef> we'll soon start to enforce various channel level agreements on the channels, so close out if they aren't forwaradding at all, peer doesn't have proper uptime, etc, etc 12:42 < sstone> yes. I think pretty soon people will start refusing tiny incoming channels, and be more aggressive with unreliable nodes 12:43 < sstone> we've also implemented probing of direct peers (I think c-lightning were the first to do that ?) 12:53 <+roasbeef> yeah they do a ping 12:53 <+roasbeef> before send to ensure the link is still acitve 12:53 <+roasbeef> active* 12:58 < rusty> Yeah, I had someone complain c-lgihtning didn't implement minimum channel amount for accepting channels. I'd never thought of it, TBH. 12:59 < sstone> I though c-lightning also use random payment hashes to probe their direct peers ? 12:59 < sstone> used 12:59 < lndbot> you should, I had so many small channels before I set the min amount with lnd would quickly get out of hand otherwise 13:00 < rusty> sstone: yeah, we ahve a couple of plugins, but we don't do it by default. 13:00 < rusty> cdecker and niftynei have both written ones, so I assume they're sweeping the network right now... 13:02 < sstone> ok 13:05 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 244 seconds] 13:06 -!- shesek [~shesek@unaffiliated/shesek] has joined #lightning-dev 13:07 -!- cARdkEf [1facece8@gateway/web/freenode/ip.31.172.236.232] has quit [Quit: Page closed] 13:08 <+roasbeef> rusty: yeh our min is 20k, a while back we ran itno an issue where the chan size was too small and ppl close out on chain due to fees, so we upped it 13:12 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 255 seconds] 13:15 -!- hiroki [a331ce08@gateway/web/freenode/ip.163.49.206.8] has quit [Quit: Page closed] 13:29 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 13:33 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 13:34 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #lightning-dev 13:34 -!- sstone [~sstone_@185.186.24.109.rev.sfr.net] has quit [Ping timeout: 250 seconds] 13:36 -!- darosior [~darosior@2a01:e35:2ff9:8200:9d71:5b1f:da8f:3768] has joined #lightning-dev 13:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 14:17 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #lightning-dev 15:23 -!- Prolac [~prolac@unaffiliated/prolac] has quit [Read error: Connection reset by peer] 15:24 -!- Prolac [~prolac@unaffiliated/prolac] has joined #lightning-dev 15:26 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Remote host closed the connection] 15:33 -!- Prolac [~prolac@unaffiliated/prolac] has quit [Quit: Leaving] 16:03 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev 16:10 -!- darosior [~darosior@2a01:e35:2ff9:8200:9d71:5b1f:da8f:3768] has quit [Remote host closed the connection] 17:27 -!- DavidMitchell[m] [davidfedii@gateway/shell/matrix.org/x-qjkshmqekinkvjbt] has quit [Read error: Connection reset by peer] 17:27 -!- TheFuzzStone[m] [thefuzzsto@gateway/shell/matrix.org/x-fmqzyhplnzzogdcv] has quit [Remote host closed the connection] 17:28 -!- interfect[m] [interfectm@gateway/shell/matrix.org/x-rhkebwrpwsqivixa] has quit [Remote host closed the connection] 17:28 -!- devdig[m] [devdigmatr@gateway/shell/matrix.org/x-bbvmlrmnoyaambqm] has quit [Remote host closed the connection] 17:28 -!- JoKe[m] [jokesharek@gateway/shell/matrix.org/x-pbnqooiehyntcuvm] has quit [Read error: Connection reset by peer] 17:30 -!- kiltzman [~k1ltzman@185.62.188.244] has quit [Ping timeout: 246 seconds] 17:33 -!- kiltzman [~k1ltzman@185.62.188.244] has joined #lightning-dev 17:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev 17:39 -!- JoKe[m] [jokesharek@gateway/shell/matrix.org/x-pucfejvhividcoqo] has joined #lightning-dev 17:50 -!- melvin_ [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 272 seconds] 17:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 18:19 -!- interfect[m] [interfectm@gateway/shell/matrix.org/x-htumwwaofaasonmi] has joined #lightning-dev 18:19 -!- devdig[m] [devdigmatr@gateway/shell/matrix.org/x-suyieyaffrfhycyy] has joined #lightning-dev 18:19 -!- TheFuzzStone[m] [thefuzzsto@gateway/shell/matrix.org/x-cofeusuklpvcrfdg] has joined #lightning-dev 18:19 -!- DavidMitchell[m] [davidfedii@gateway/shell/matrix.org/x-mixgqrajxdbghcyw] has joined #lightning-dev 18:38 -!- vtnerd_ [~Lee@173-23-103-30.client.mchsi.com] has joined #lightning-dev 18:39 -!- vtnerd [~Lee@173-23-103-30.client.mchsi.com] has quit [Ping timeout: 245 seconds] 18:54 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 19:02 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev 19:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev 19:12 -!- riclas [riclas@148.63.37.111] has quit [Ping timeout: 268 seconds] 19:42 -!- shesek [~shesek@93-38-48-98.ip69.fastwebnet.it] has joined #lightning-dev 19:42 -!- shesek [~shesek@93-38-48-98.ip69.fastwebnet.it] has quit [Changing host] 19:42 -!- shesek [~shesek@unaffiliated/shesek] has joined #lightning-dev 20:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev 23:07 -!- kiltzman [~k1ltzman@185.62.188.244] has quit [Ping timeout: 264 seconds] 23:19 -!- melvin_ [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lightning-dev 23:22 -!- kiltzman [~k1ltzman@185.62.188.244] has joined #lightning-dev --- Log closed Tue Mar 19 00:00:20 2019