--- Log opened Mon Aug 17 00:00:51 2020
00:05 -!- jonatack [~jon@213.152.162.170] has quit [Ping timeout: 264 seconds]
00:07 -!- marcoagner [~user@bl11-17-219.dsl.telepac.pt] has joined #lightning-dev
00:08 -!- opsec_x12 [~opsec_x12@c-67-183-29-123.hsd1.wa.comcast.net] has joined #lightning-dev
00:16 -!- jonatack [~jon@37.173.134.26] has joined #lightning-dev
00:16 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
00:21 -!- laptop [~laptop@85-195-244-64.fiber7.init7.net] has joined #lightning-dev
00:25 -!- laptop [~laptop@85-195-244-64.fiber7.init7.net] has quit [Remote host closed the connection]
00:36 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #lightning-dev
00:44 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
00:46 -!- _flow_ [~none@salem.informatik.uni-erlangen.de] has quit [Quit: WeeChat 2.8]
00:52 -!- _flow_ [~none@salem.informatik.uni-erlangen.de] has joined #lightning-dev
01:00 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has joined #lightning-dev
01:14 -!- Pavlenex [~Thunderbi@141.98.103.251] has joined #lightning-dev
01:14 -!- Pavlenex [~Thunderbi@141.98.103.251] has quit [Client Quit]
01:27 -!- yzernik [~yzernik@2600:1700:dc40:3dd0:7959:4abc:66d0:df15] has quit [Ping timeout: 244 seconds]
01:28 -!- yzernik [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has joined #lightning-dev
01:42 -!- yzernik [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has quit [Ping timeout: 240 seconds]
01:43 -!- yzernik [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has joined #lightning-dev
01:56 -!- rdymac [uid31665@gateway/web/irccloud.com/x-gmtmuztgkritnlyh] has joined #lightning-dev
02:03 -!- laptop [~laptop@212.203.87.198] has joined #lightning-dev
02:05 -!- jonatack [~jon@37.173.134.26] has quit [Ping timeout: 256 seconds]
02:10 -!- zmanian_ [sid113594@gateway/web/irccloud.com/x-icvlgcsmdljbedob] has quit [Read error: Connection reset by peer]
02:10 -!- CodeShark___ [sid126576@gateway/web/irccloud.com/x-sbibwyjkowqluexo] has quit [Read error: Connection reset by peer]
02:10 -!- digi_james [sid281632@gateway/web/irccloud.com/x-mlrabtrlgtkxmnzl] has quit [Read error: Connection reset by peer]
02:12 -!- fjahr [sid374480@gateway/web/irccloud.com/x-uivuzkqvxqkxtfmn] has quit [Ping timeout: 260 seconds]
02:13 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #lightning-dev
02:14 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
02:17 -!- fjahr [sid374480@gateway/web/irccloud.com/x-oiefvwkqhrcxgrux] has joined #lightning-dev
02:17 -!- digi_james [sid281632@gateway/web/irccloud.com/x-nbhbgbttjkqeljzc] has joined #lightning-dev
02:18 -!- Pavlenex [~Thunderbi@141.98.103.251] has joined #lightning-dev
02:23 -!- Pavlenex [~Thunderbi@141.98.103.251] has quit [Quit: Pavlenex]
02:23 -!- zmanian_ [sid113594@gateway/web/irccloud.com/x-owgovjfyzsyioxij] has joined #lightning-dev
02:23 -!- CodeShark___ [sid126576@gateway/web/irccloud.com/x-llqxtmpeasxaoiaz] has joined #lightning-dev
02:38 -!- ddustin_ [~ddustin@unaffiliated/ddustin] has joined #lightning-dev
02:39 -!- jonatack [~jon@37.173.134.26] has joined #lightning-dev
02:40 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 260 seconds]
02:44 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
02:51 -!- Pavlenex [~Thunderbi@141.98.103.251] has joined #lightning-dev
02:51 -!- Pavlenex [~Thunderbi@141.98.103.251] has quit [Client Quit]
02:54 -!- Pavlenex [~Thunderbi@141.98.103.251] has joined #lightning-dev
02:55 -!- Pavlenex [~Thunderbi@141.98.103.251] has quit [Client Quit]
02:58 -!- cloudflare [~cloudflar@unaffiliated/cloudflare] has joined #lightning-dev
03:03 -!- norisg [~nobody123@dslb-092-075-080-136.092.075.pools.vodafone-ip.de] has joined #lightning-dev
03:07 -!- norisg [~nobody123@dslb-092-075-080-136.092.075.pools.vodafone-ip.de] has quit [Ping timeout: 256 seconds]
03:13 -!- Pavlenex [~Thunderbi@141.98.103.251] has joined #lightning-dev
03:31 -!- jonatack [~jon@37.173.134.26] has quit [Read error: Connection reset by peer]
03:33 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev
03:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
03:40 -!- Pavlenex [~Thunderbi@141.98.103.251] has quit [Quit: Pavlenex]
03:55 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
03:56 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev
03:58 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
03:58 -!- vasild_ is now known as vasild
04:30 -!- Pavlenex [~Thunderbi@141.98.103.251] has joined #lightning-dev
04:33 -!- Pavlenex [~Thunderbi@141.98.103.251] has quit [Client Quit]
04:51 -!- lmatteis_ [uid3300@gateway/web/irccloud.com/x-qjubqqbdcbnnchkl] has joined #lightning-dev
04:52 -!- lmatteis_ [uid3300@gateway/web/irccloud.com/x-qjubqqbdcbnnchkl] has quit [Client Quit]
04:53 -!- lmatteis_ [uid3300@gateway/web/irccloud.com/x-qtjyiovnlrzqwsom] has joined #lightning-dev
04:53 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #lightning-dev
05:19 -!- jeremyrubin [~jr@2601:645:c200:f539:1d25:1a55:e644:5c4d] has quit [Ping timeout: 260 seconds]
05:45 -!- fox2p [~fox2p@ec2-52-87-89-213.compute-1.amazonaws.com] has quit [Quit: hash]
06:08 -!- arowser [~arowser1@192.69.88.248.16clouds.com] has quit [Remote host closed the connection]
06:09 -!- arowser [~arowser1@192.69.88.248] has joined #lightning-dev
06:09 -!- arowser [~arowser1@192.69.88.248] has quit [Remote host closed the connection]
06:10 -!- arowser [~arowser1@192.69.88.248] has joined #lightning-dev
06:12 -!- arowser [~arowser1@192.69.88.248] has quit [Read error: Connection reset by peer]
06:13 -!- arowser [~arowser1@192.69.88.248.16clouds.com] has joined #lightning-dev
06:13 -!- arowser [~arowser1@192.69.88.248.16clouds.com] has quit [Remote host closed the connection]
06:13 -!- arowser [~arowser1@192.69.88.248] has joined #lightning-dev
06:30 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:33 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #lightning-dev
06:36 -!- fearbeag [~seanicide@142.114.183.92] has joined #lightning-dev
06:45 -!- proofofkeags [~proofofke@174-29-11-169.hlrn.qwest.net] has joined #lightning-dev
06:50 -!- laptop [~laptop@212.203.87.198] has quit [Ping timeout: 256 seconds]
07:00 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has joined #lightning-dev
07:00 -!- lmatteis_ [uid3300@gateway/web/irccloud.com/x-qtjyiovnlrzqwsom] has quit [Quit: Connection closed for inactivity]
07:00 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lightning-dev
07:03 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Ping timeout: 240 seconds]
07:04 -!- norisg [~nobody123@dslb-092-075-080-136.092.075.pools.vodafone-ip.de] has joined #lightning-dev
07:09 -!- norisg [~nobody123@dslb-092-075-080-136.092.075.pools.vodafone-ip.de] has quit [Ping timeout: 256 seconds]
07:10 -!- laptop [~laptop@212.203.87.198] has joined #lightning-dev
07:12 -!- melande [~melande@gateway/tor-sasl/melande] has joined #lightning-dev
07:13 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
07:13 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lightning-dev
07:16 -!- arowser [~arowser1@192.69.88.248] has quit [Remote host closed the connection]
07:17 -!- arowser [~arowser1@192.69.88.248.16clouds.com] has joined #lightning-dev
07:19 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
07:20 -!- laptop [~laptop@212.203.87.198] has quit [Ping timeout: 256 seconds]
07:22 -!- rh0nj [~rh0nj@88.99.167.175] has joined #lightning-dev
07:48 -!- proofofkeags [~proofofke@174-29-11-169.hlrn.qwest.net] has quit [Ping timeout: 240 seconds]
07:49 -!- laptop [~laptop@85-195-244-64.fiber7.init7.net] has joined #lightning-dev
07:52 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Quit: jb55]
07:52 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #lightning-dev
07:54 -!- laptop [~laptop@85-195-244-64.fiber7.init7.net] has quit [Ping timeout: 264 seconds]
07:55 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
07:56 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #lightning-dev
08:04 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has quit [Read error: Connection reset by peer]
08:05 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has joined #lightning-dev
08:05 -!- Pavlenex [~Thunderbi@141.98.103.251] has joined #lightning-dev
08:38 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
08:50 -!- alko [~alko@cpe-85-10-28-138.static.amis.net] has quit [Quit: Konversation terminated!]
09:01 -!- weedcoder [~weedcoder@2a02:120b:2c08:21f0:c07e:e68e:d9f1:d32d] has joined #lightning-dev
09:07 -!- proofofkeags [~proofofke@174-29-11-169.hlrn.qwest.net] has joined #lightning-dev
09:11 -!- proofofkeags [~proofofke@174-29-11-169.hlrn.qwest.net] has quit [Ping timeout: 246 seconds]
09:14 -!- mol [~mol@unaffiliated/molly] has joined #lightning-dev
09:19 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
09:20 -!- jeremyrubin [~jr@2601:645:c200:f539:1d25:1a55:e644:5c4d] has joined #lightning-dev
09:23 -!- arowser [~arowser1@192.69.88.248.16clouds.com] has quit [Remote host closed the connection]
09:23 -!- proofofkeags [~proofofke@174-29-11-169.hlrn.qwest.net] has joined #lightning-dev
09:24 -!- arowser [~arowser1@192.69.88.248] has joined #lightning-dev
09:27 -!- belcher [~belcher@unaffiliated/belcher] has joined #lightning-dev
09:27 -!- proofofkeags [~proofofke@174-29-11-169.hlrn.qwest.net] has quit [Ping timeout: 260 seconds]
09:55 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
09:58 -!- lndbot2 [~lndbot@138.197.213.35] has quit [Remote host closed the connection]
09:58 -!- lndbot [~lndbot@138.197.213.35] has joined #lightning-dev
10:22 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Ping timeout: 256 seconds]
10:38 -!- norisg [~nobody123@dslb-092-075-080-136.092.075.pools.vodafone-ip.de] has joined #lightning-dev
10:39 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
10:40 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
10:48 -!- Pavlenex [~Thunderbi@141.98.103.251] has quit [Quit: Pavlenex]
10:55 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
10:56 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
11:10 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
11:11 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
11:13 -!- mol_ [~mol@unaffiliated/molly] has joined #lightning-dev
11:16 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 260 seconds]
11:26 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
11:27 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
11:41 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
11:42 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
11:58 -!- alko89 [~alko89@unaffiliated/alko89] has joined #lightning-dev
12:06 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
12:10 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev
12:10 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
12:12 -!- laptop [~laptop@85-195-244-64.fiber7.init7.net] has joined #lightning-dev
12:50 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #lightning-dev
12:53 -!- treehug88 [~textual@pool-74-108-51-127.nycmny.fios.verizon.net] has quit [Ping timeout: 256 seconds]
12:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev
12:56 -!- treehug88 [~textual@pool-74-108-51-127.nycmny.fios.verizon.net] has joined #lightning-dev
12:59 < niftynei> hello hello hello
12:59 < rusty> Hello everyone!
13:00 < niftynei> hello rusty!
13:00 < rusty> hello niftynei!  That's two of us :)
13:00 -!- sstone [~sstone@112.ip-51-68-199.eu] has joined #lightning-dev
13:01 < lndbot> <johanth> hi :slightly_smiling_face:
13:02 < sstone> hi everyone!
13:02 < niftynei> i half remember seeing that tbast is out on vacation this week?
13:02 < niftynei> hello sstone!
13:02 < sstone> yes he won't join us today
13:03 < rusty> niftynei: ah, maybe?  Christian is also out this week, hopefully vacationing!
13:05 < rusty> Hmm, who will chair then?
13:07 < rusty> OK, since we're already 5 minutes late, I guess I'll chair!
13:08 < rusty> #startmeeting
13:08 < lightningbot> Meeting started Mon Aug 17 20:08:11 2020 UTC.  The chair is rusty. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:08 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:08 < rusty> #topic https://github.com/lightningnetwork/lightning-rfc/pull/785
13:09 < rusty> I think we reached consensus last meeting on this, but let's just confirm?  The "must specify" + "assume 18 if not specified" combo seems to have made everyone "not unhappy"?
13:10 <+roasbeef> yeh I think so, everyone should specify and it's safe to assume 18 otherwise, as they should still accvept the payment w/ the larger value 
13:10 <+roasbeef> but _decreasing_ would require a more uniform update path 
13:10 < rusty> roasbeef: yep, I agree.  OK, anyone object to applying it?
13:11 < rusty> #action Apply https://github.com/lightningnetwork/lightning-rfc/pull/785
13:11 < rusty> #topic https://github.com/lightningnetwork/lightning-rfc/pull/767
13:12 <+roasbeef> overall change sgtm, but haven't reviwed the wording or anything yet 
13:12  * roasbeef glances at the PR.... 
13:12 < rusty> roasbeef: it's literally "if a channel's latest `channel_update`s `timestamp` is older than two weeks" -> "if a channel's oldest `channel_update`s `timestamp` is older than two weeks"
13:13 < niftynei> is it oldest or the newest?
13:13 <+roasbeef> rusty: diff context? 
13:13 <+roasbeef> ahh ok switched PRs
13:13 <+roasbeef> approved 785 
13:14 < niftynei> ah i see, that's the whole thing isn't it lol
13:14 < rusty> niftynei: oldest... basically if either end lets the channel go stale, it's dead.
13:14 <+roasbeef> yeh the actual diff is tiny 
13:14 < niftynei> yep, makes sense to me. 
13:14 <+roasbeef> I guess it's clarification in a sense, as "latest" can be kinda ambigious 
13:15 <+roasbeef> I think the end goal here is also more aggressive pruning, as nodes need to make sure they aren't caught slipping w.r.t how old thier updates are 
13:15 < rusty> aside: next lightning version I'm going to change routing to ignore channels which are disabled in *either* dir.  Turns out that (of course, but I'm slow) if one side goes offline, it doesn't send an update with disable.  This leads to loads of unidir channels which aren't actually usable.
13:15 < rusty> s/lightning/c-lightning/
13:16 < sstone> roasbeef: can you please clarify the "y'alls continues to send fresh channel_updates" bit ? 
13:16 <+roasbeef> yeh we've been looking at making some changes in that area ourselves too, lnd doesn't have an easy api to enable/disable, so we've seem some nodes start to advertise super high fees as a subsitute if they don't want the chan to be used for w/e reasn 
13:16 < rusty> (Could refine this to take the *latest* update, so if one side has just marked it enabled it'll be counted, but in practice that's rare).
13:17 <+roasbeef> sstone: I think he means that rn lnd nodes will continue to send the update even if the other person is never online 
13:17 <+roasbeef> which I think all other nodes do to? as in we always sign before the "deadline" regardless of if they other peer is active or not 
13:17 < rusty> sstone: currently nodes will refresh channel, even if they haven't seen the peer all that time.
13:17 < rusty> Yeah, us too.
13:18 < rusty> (We don't close without explicit instructions, but "been away for 2 weeks" would be a pretty good heuristic...(
13:18 < sstone> mmm... what is the rationale for publishing updates for a channel for which the remote peer is offline ?
13:18 < niftynei> right, this proposed PR would remove those channels from gossip propagation
13:19 < rusty> sstone: we simply didn't check.  We don't actually keep records on when we last saw peer (at least, not inside our gossip logic)
13:20 < rusty> So, meanwhile, are people happy for https://github.com/lightningnetwork/lightning-rfc/pull/767 ?  Seems harmless, and useful, though we could have an other PR to fix the refresh for dead peers logic.,
13:20 < niftynei> hmm wait maybe that's not true... this is just a recommendation eh
13:21 < rusty> niftynei: yeah, and one we should probably implement.
13:22 < rusty> No objections in 1 minute and I'll action to apply it?
13:22 < niftynei> well it sounds like we'll already be de-facto implementing it by ignoring these channels for routing :)
13:23 < rusty> (Next: https://github.com/lightningnetwork/lightning-rfc/pull/695 because why not)
13:23 < niftynei> does 'prune' here, in bolt 07, mean 'remove from gossip'?
13:23 <+roasbeef> sstone: in our case, the systems just don't communicate
13:23 < niftynei> or is this just 'fyi, you should probs do this to your internal representation'
13:24 < rusty> niftynei: yes, you no longer propagate it either.
13:24 < rusty> "This channel is dead to me"
13:24 < niftynei> gotcha :thumbs_up:
13:24 <+roasbeef> one is the "link" the other is the "gossiper"
13:24 < sstone> ok we have a different design but I guess this PR is harmless, so I won't object
13:25 < rusty> #action apply https://github.com/lightningnetwork/lightning-rfc/pull/767
13:25 <+roasbeef> ours is basically a cron job internall that runs and checks if it needs to send out another one, and sleeps if doesn't 
13:25 < rusty> #topic https://github.com/lightningnetwork/lightning-rfc/pull/695
13:26 < rusty> OK, this is really rough (should prob be a TLV).  But we find ourselves probing for capacities now with MPP, which seems silly.
13:26 <+roasbeef> hmmm, isn't this information already available if clients look at their path finding history? 
13:26 <+roasbeef> and nodes should be setting max_htlc properly to signal the largest htlc they're willing to accept 
13:26 <+roasbeef> it also effectively undoes the philosophy behind "temp channel failure" 
13:26 < rusty> roasbeef: you currently end up bouncing off the channel until you get low enough.  That's a pretty poor use of resources.
13:27 <+roasbeef> sure but you can also remember yoru past attempts, and discount any failures temporarily, so like decay the probability 
13:27 <+roasbeef> fwiw there've also been a buncha papers that show how mapping certain sections of the netowrk is super easy via probing 
13:27 <+roasbeef> tho there're a series of defenses gfainst that which require no protocol chagnes, but which aren't super widely implemented 
13:28 < rusty> roasbeef: this simply shortcuts the process, esp when you're going to fail anyway.
13:28 <+roasbeef> oh this is on the channel_update....somehow I read it as a new failure message 
13:28 <+roasbeef> err no it's a failur emessge kek 
13:28 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #lightning-dev
13:29 < rusty> Yeah, it's after the channel_update... trying to avoid the current inefficient probing, or at least reduce it.
13:30 <+roasbeef> is capacity_order meant to be like 3 bits? "ok, send more, send less?" 
13:30 <+roasbeef> or 2 
13:30 < rusty> roasbeef: naah, it's "you are out by this many orders of magnitude"...
13:30 <+roasbeef> ahhh
13:30 < niftynei> seems like it's you're within 2*2, you're within 2*16, etc?
13:31 < bitconner> hey y'all 👋  missed the discussion about 767 but happy to circle back later if people have more questions
13:31 < niftynei> hello bitconner !
13:31 < rusty> bitconner: we actioned it for merge, assume that's OK?
13:32 < bitconner> sgtm!
13:32 < niftynei> seems like the real question here is "are hints ok or should we keep you guessing?"
13:32 < rusty> Dunno if the capacity_order should be relative to their HTLC, or simply absolute...
13:33 < niftynei> absolute meaning 'hints for the total channel capacity' vs 'hints for capacity missing for this htlc'?
13:33 < rusty> niftynei: yeah.
13:33 <+roasbeef> relative to the htlc leaks more info I guess? 
13:33 < bitconner> main q i think is whether to just return the value explicitly or to actually fuzz. fuzzing only adds a logarithmic factor to the htlcs one needs to send to binary search a channel capacity no?
13:33 <+roasbeef> err less info* 
13:34 < niftynei> right, the htlc amount allows you to probe for a more exact amount
13:34 < rusty> roasbeef: I'm not sure... I feel it's true, but I can't really prove it either.
13:34 < rusty> bitconner: fuzzing avoids them *accidentally* probing, at least...
13:35 < rusty> Anyway, discuss on issue?  The whole idea makes me kinda nervous, but I do feel that not including it is just a fig leaf and not real privacy.
13:36 <+roasbeef> yeh I think discuss on issue, I can bring up some of the recent papers in this area, so we can examine some of their suggestions 
13:36 < rusty> #topic https://github.com/lightningnetwork/lightning-rfc/pull/688 (yay!)
13:36 < niftynei> sgtm. it does get into interesting questions about what the point of (semi)obscuring current capacity is
13:37 < rusty> OK, we have a successful interop test!  Any objections to applying this?
13:37 <+roasbeef> niftynei: mhmm, many of the papers argue that it sin't really effective, given ppl don't set max_htlc or limit the outstanding amt, and you can kinda paint parts of the sub-graph given probing is "free"
13:38 <+roasbeef> yay interop!
13:38 < rusty> #action apply https://github.com/lightningnetwork/lightning-rfc/pull/688 
13:39 <+roasbeef> seems the fee thing has been resolved which is nice 
13:39 < rusty> Nice!  I'm also running it on my testnet and mainnet nodes, but haven't actually interop tested yet because I'm slack :)
13:39 <+roasbeef> so we need to make a small change on our end re the fee thing, but we should be able to bundle it in our next major release (about to release 0.11, so would be 0.12) or a minor release possilby so we can make it more widespread on the network sooner 
13:39 < rusty> I think joost should do the honors of merging it, since he did all the hard work...
13:40 <+roasbeef> he's back from vacation just in time ;) 
13:40 <+roasbeef> also johan back too in time 
13:41 <+roasbeef> it's late-ish from them, so tomorrow my time they should be able to do the final sniff and hit the merge button 
13:41 < rusty> roasbeef: yeah, our implementation is config-experimental only.  It just forgets the anchor outputs on unilateral close.  But maybe that's OK, hmm...
13:41 < rusty> roasbeef: nice!
13:42 < rusty> OK, that's the substative part done I think.  Some minor things:
13:43 < rusty> #738 (ln.dev) I have found some people to try to wrangle the site.  The main thing I want is a matrix of major implementation versions and what features they support/require (e.g. payment secrets, MPP, anchor outputs).
13:43 < rusty> That would give implementors an idea of when they can deprecate...
13:44 <+roasbeef> cool, we have a checklist in our readme, but it's super outdated
13:44 < rusty> #topic https://github.com/lightningnetwork/lightning-rfc/pull/672
13:45 <+roasbeef> like the rest of our readme really lol 
13:45 < rusty> roasbeef we haven't even been tracking, I'll have to dig through changelogs at very least... :(
13:45 <+roasbeef> woah, this one is old, I'd forgotten about it lol 
13:45 < rusty> Seems like we  should assign a feature bit and move to interop testing?
13:45 <+roasbeef> wasn't there somtehing on the bitcoind side related to this? 
13:45 <+roasbeef> the anysegwit thing 
13:46 <+roasbeef> like something about modifying relay behavior...? I'm behind on irc lol 
13:46 < rusty> roasbeef: I think it was simply awaiting 0.19.0 being widely deplpoyed...
13:46 < bitconner> prior the mempool only allowed version 0, but that was relaxed iirc
13:46 <+roasbeef> this is like related to taproot if I'm vaguely remembering it properly 
13:47 < rusty> bitconner: yeah... so if they propagate, there's no reason to ban them.  However, current clients do, so we need a feature bit.
13:48 < jeremyrubin> hi
13:48 < jeremyrubin> roasbeef: are you asking about wtxid relay?
13:48 < rusty> I propose 22/23 as feature bits for this: that seems to be the next cab on the rank?
13:48 <+roasbeef> maybe jeremyrubin  knows? 
13:48 <+roasbeef> idk maybe, lol 
13:49  * bitconner waves
13:49 < rusty> jeremyrubin: my understanding is that, regardless, a tx with a segwit v(1-16) output will currently propagate?
13:49 <+roasbeef> fwiw, rn I think we just limit on size...of the addr, which is also diff for the next segwit version 
13:49 <+roasbeef> in terms of our validation of close addrs 
13:49 < jeremyrubin> Output maybe. 
13:49 < jeremyrubin> Input no
13:49 < jeremyrubin> Let me check
13:50 < rusty> roasbeef: yes, I suspect it was our discussion of how we have to handle this that lead to that bitcoind PR, but I might be wrong.
13:51 < rusty> (The idea was "upgrade once and your software will handle all future segwits too", but that proved fraught with subtle problems like this one...)
13:52 < bitconner> https://github.com/bitcoin/bitcoin/pull/15846
13:52 < jeremyrubin> TX_WITNESS_UNKNOWN seems to be a standard output
13:53 < bitconner> > This makes sending to future Segwit versions via native outputs (bech32) standard for relay, mempool acceptance, and mining. Note that spending such outputs (including P2SH-embedded ones) remains nonstandard, as that is actually required for softfork safety.
13:53 < jeremyrubin> I'm not sure where we reject the inputs though, will have to look
13:54 < jeremyrubin> ah
13:54 < jeremyrubin> discourage upgradeable witness 
13:54 < jeremyrubin> So we only reject witness type if the script is run for mempool
13:54  * jeremyrubin carry on
13:55 < rusty> jeremyrubin: thanks for confirm.  So, let's assign a feature bit?  Anyone object?
13:55 < jeremyrubin> There is one issue
13:55 < jeremyrubin> Which is that you can get weird cross version pinning stuff 
13:56 < jeremyrubin> E.g., v2 witness looks unspendable to and old client
13:56 < jeremyrubin> but then to a new client, v2 witness is spendable
13:56 < jeremyrubin> so new nodes could have another child tx causing pinning on new but not old
13:56 < jeremyrubin> Which might be confusing for LNDs to deal with
13:57 < rusty> jeremyrubin: in this case, it's a mutual close so pinning isn't really an issue AFAICT.
13:57 < jeremyrubin> cool
13:58 < bitconner> rusty: changes look good to me, i'd vote for proceeding with feature bit assignment
13:58 < rusty> OK, I'll assign 22/23 as features on the issue.  Interop testing on testnet should be pretty easy with some hacks...
13:59 < rusty> OK, let's sneak in one more: blast from the past: https://github.com/lightningnetwork/lightning-rfc/pull/641
14:00 < rusty> #action Assign features 22/23 for https://github.com/lightningnetwork/lightning-rfc/pull/672 for interop testing.
14:00 < rusty> #topic https://github.com/lightningnetwork/lightning-rfc/pull/641
14:00 < rusty> This is about not giving historical data when timestamp filtering.
14:00 < bitconner> hehe wow that is a blast 
14:00 -!- laptop [~laptop@85-195-244-64.fiber7.init7.net] has quit [Ping timeout: 240 seconds]
14:01 < bitconner> for those catching up, the idea is that just setting really old timestamps makes this initial dump equivalent to `initial_routing_sync`
14:01 < bitconner> we opted to ditch `initial_routing_sync` in favor of gossip queries because it proved to be inefficient
14:02 < rusty> Unf, c-lightning uses timestamp 0 for initial startup on the very first peer, precisely to get the firehose.
14:02 < rusty> I definitely think that after the initial gossip_timestamp_filter you shouldn't be able to ask for historicals.
14:03 < rusty> But the bootstrap case needs something.
14:03 < bitconner> why can't it just use the same set reconcilliation protocol?
14:03 < rusty> bitconner: it's more efficient to ask for everything if you know you know nothing?
14:04 < bitconner> in the past we observed cases on mobile where a mobile phone connected to CL would be asked to dump 40+MB every time the app was opened
14:04 < rusty> bitconner: yeah, that was quite a while ago,.
14:04 < bitconner> i think some of those bugs have been fixed, but i think the goal is to curb reliance on asking for dumps in general
14:05 < rusty> bitconner: I'm not sure asking for all possible scids is much better though.
14:05 < BlueMatt> why? dumps are...the expected thing on first startup
14:05 < bitconner> it ends up being < 10 control messages, which is still dwarfed by the thousands of messages for channels and ndoes
14:06 < BlueMatt> its not an effeciency question, though, its a "why make a common case deliberately inscruitable"?
14:07 < bitconner> so that people don't lean on it as a catch all, which has already happened
14:07 <+roasbeef> BlueMatt: it persisted on every connect, not just the first start up
14:07 < BlueMatt> right, and thats a bug that rusty indicated was fixed?
14:07 <+roasbeef> like it requested a dump even if it had everything, or just did a recent dump 
14:07 < rusty> BlueMatt: it was a year ago, but it still hurts to think about it.
14:08 < BlueMatt> ok, so...problem solved? no need to update the spec? I'm confused. are you *still* seeing this issue roasbeef/bitconner?
14:08 < bitconner> iirc RL doesn't hasn't fully implemented gossip queries? so i see why you wouldn't want to remove this
14:08 < rusty> Now, we ask the first peer for everything.  Once that's done (or stalled), we ask another peer for every scid (because, I guess, if the first peer is LND it didn't honor the timestamp?)
14:08 < BlueMatt> or just the pr was opened then and hasnt been reconsidered since?
14:09 < rusty> BlueMatt: it *is* easier not to implement the rewind behavior.
14:09 < rusty> roasbeef/bitconner: I assume this PR reflect current lnd behavior?
14:09 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
14:09 < bitconner> currently we have a config option tha allows you toggle whether you reply or not
14:10 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
14:11 < rusty> bitconner: well, we'll survive if it's disabled.  I can change the algo not to rely on it at all: in practice, practice beats theory, so if this is existing behavior we should document it.
14:11 < bitconner> if you want a dump from the first peer, why not set `initial-routing-sync` instead of doing so via historical timestamps?
14:12 < bitconner> why does that functionality need to exist twice
14:13 < rusty> bitconner: because you have to know that at connect time :(
14:14 < rusty> bitconner: And it doesn't work with gossip timestamps extension anyway:
14:14 < rusty> A node:
14:14 < rusty>   - if the `gossip_queries` feature is negotiated:
14:14 < rusty>     - MUST not send gossip it did not generate itself, until it receives `gossip_timestamp_filter`.
14:14 < rusty> (i.e. initial-routing-sync doesn't really exist anymore)
14:15 < bitconner> don't you know you know nothing before connecting?
14:15 < bitconner> (in the very fist sync example)
14:15 < bitconner> first*
14:16 < bitconner> this is true, lnd removed initial-routing-sync several versions ago
14:16 < bitconner> BlueMatt: i haven't noticed the issue recently, but probably because i run with `ignore-historical-gossip-filters` on
14:17 < bitconner> perhaps we should continue this discussion on the issue given we are over
14:17 < rusty> bitconner: agreed.
14:18 < rusty> #action discuss https://github.com/lightningnetwork/lightning-rfc/pull/641 on issue
14:18 < rusty> Any Other Business?
14:20 < rusty> BTW, I've been doing some research on tracability of payments by intermediate hops, will share soon.  Seems like it's bad (immediate neigbors can guess within a handful of potential src/dst), but not awful (other intermediates have possible set sizes about 1/3 of entire network).  Will post something soon.
14:20 < rusty> #closemeeting
14:20 < rusty> #endmeeting
14:20 < lightningbot> Meeting ended Mon Aug 17 21:20:48 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
14:20 < lightningbot> Minutes:        http://www.erisian.com.au/meetbot/lightning-dev/2020/lightning-dev.2020-08-17-20.08.html
14:20 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/lightning-dev/2020/lightning-dev.2020-08-17-20.08.txt
14:20 < lightningbot> Log:            http://www.erisian.com.au/meetbot/lightning-dev/2020/lightning-dev.2020-08-17-20.08.log.html
14:20 < rusty> OK, thanks everyone!
14:20 < bitconner> rusty: sounds cool, looking forward to it!
14:23 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev
14:25 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 246 seconds]
14:25 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
14:26 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
14:39 -!- ddustin_ [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
14:40 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lightning-dev
14:40 -!- sstone [~sstone@112.ip-51-68-199.eu] has quit [Quit: Leaving]
14:40 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
14:41 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
14:42 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
14:45 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 260 seconds]
14:48 -!- marcoagner [~user@bl11-17-219.dsl.telepac.pt] has quit [Ping timeout: 264 seconds]
14:50 -!- yzernik [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has quit [Ping timeout: 256 seconds]
14:50 -!- yzernik [~yzernik@2600:1700:dc40:3dd0:7959:4abc:66d0:df15] has joined #lightning-dev
14:55 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
14:56 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
15:02 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
15:02 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
15:07 -!- dome [~e-mod@c-73-46-0-211.hsd1.fl.comcast.net] has joined #lightning-dev
15:11 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
15:12 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
15:26 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
15:26 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
15:27 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
15:33 -!- yzernik_ [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has joined #lightning-dev
15:33 -!- yzernik [~yzernik@2600:1700:dc40:3dd0:7959:4abc:66d0:df15] has quit [Ping timeout: 244 seconds]
15:41 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
15:42 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
15:55 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
15:57 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
15:58 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
15:58 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
15:58 -!- vasild_ is now known as vasild
16:01 -!- yzernik_ [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has quit [Ping timeout: 246 seconds]
16:12 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
16:13 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
16:16 -!- weedcoder [~weedcoder@2a02:120b:2c08:21f0:c07e:e68e:d9f1:d32d] has quit [Ping timeout: 272 seconds]
16:27 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
16:28 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
16:42 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
16:43 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
16:55 -!- rdymac [uid31665@gateway/web/irccloud.com/x-gmtmuztgkritnlyh] has quit [Quit: Connection closed for inactivity]
16:58 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
16:59 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
17:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev
17:08 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
17:13 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
17:14 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
17:28 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
17:29 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
17:43 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
17:44 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
17:44 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
17:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
17:58 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
17:59 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
18:08 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has quit [Ping timeout: 256 seconds]
18:10 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has quit [Remote host closed the connection]
18:10 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #lightning-dev
18:15 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has quit [Ping timeout: 260 seconds]
18:16 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
18:17 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
18:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
18:31 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
18:32 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
18:38 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
18:40 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
18:46 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #lightning-dev
18:47 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
18:48 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
18:50 -!- yzernik [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has joined #lightning-dev
18:50 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has quit [Ping timeout: 256 seconds]
18:53 -!- arowser [~arowser1@192.69.88.248] has quit [Remote host closed the connection]
18:53 -!- arowser [~arowser1@192.69.88.248] has joined #lightning-dev
18:54 -!- yzernik_ [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has joined #lightning-dev
18:54 -!- yzernik [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has quit [Ping timeout: 256 seconds]
19:02 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
19:03 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
19:04 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 264 seconds]
19:18 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
19:19 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
19:26 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #lightning-dev
19:34 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
19:35 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
19:49 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
19:51 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
20:05 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
20:06 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
20:08 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
20:08 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
20:08 -!- vasild_ is now known as vasild
20:14 -!- tryphe_ is now known as tryphe
20:22 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
20:23 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
20:23 -!- arowser [~arowser1@192.69.88.248] has quit [Read error: Connection reset by peer]
20:24 -!- arowser [~arowser1@192.69.88.248] has joined #lightning-dev
20:26 -!- berndj [~berndj@ns1.linksynergy.co.za] has quit [Remote host closed the connection]
20:29 -!- berndj [~berndj@ns1.linksynergy.co.za] has joined #lightning-dev
20:29 -!- interfect[m] [interfectm@gateway/shell/matrix.org/x-dyokvkyepytrhkes] has quit [Read error: Connection reset by peer]
20:29 -!- zkao [zkaomatrix@gateway/shell/matrix.org/x-wlxxxygqxfvltard] has quit [Remote host closed the connection]
20:29 -!- TheFuzzStone[m] [thefuzzsto@gateway/shell/matrix.org/x-kfkxcubdaveiuvwm] has quit [Write error: Connection reset by peer]
20:36 -!- interfect[m] [interfectm@gateway/shell/matrix.org/x-uwxdjyvguzoriaeh] has joined #lightning-dev
20:37 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
20:38 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
20:38 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
20:39 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
20:40 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
20:41 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 240 seconds]
20:44 -!- lukedashjr is now known as luke-jr
20:47 -!- yzernik_ [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has quit [Ping timeout: 265 seconds]
20:50 -!- yzernik [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has joined #lightning-dev
20:53 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
20:54 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
20:56 -!- yzernik [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has quit [Ping timeout: 246 seconds]
20:57 -!- yzernik [~yzernik@2600:1700:dc40:3dd0:7959:4abc:66d0:df15] has joined #lightning-dev
21:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
21:03 -!- jeremyrubin [~jr@2601:645:c200:f539:1d25:1a55:e644:5c4d] has quit [Ping timeout: 260 seconds]
21:05 -!- zkao [zkaomatrix@gateway/shell/matrix.org/x-jdqwvnhupqiadjub] has joined #lightning-dev
21:05 -!- TheFuzzStone[m] [thefuzzsto@gateway/shell/matrix.org/x-dclcfywknvejsmkh] has joined #lightning-dev
21:08 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
21:09 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
21:24 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
21:25 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
21:29 -!- yzernik [~yzernik@2600:1700:dc40:3dd0:7959:4abc:66d0:df15] has quit [Quit: ZNC 1.7.5 - https://znc.in]
21:34 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
21:36 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #lightning-dev
21:38 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
21:38 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
21:40 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
21:41 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
21:48 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Read error: Connection reset by peer]
21:48 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Write error: Connection reset by peer]
21:48 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Write error: Connection reset by peer]
21:48 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Write error: Connection reset by peer]
21:48 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Write error: Connection reset by peer]
21:48 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Read error: Connection reset by peer]
21:48 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
21:48 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has quit [Write error: Connection reset by peer]
21:48 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Write error: Connection reset by peer]
21:50 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lightning-dev
21:50 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #lightning-dev
21:51 -!- melande [~melande@gateway/tor-sasl/melande] has joined #lightning-dev
21:52 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #lightning-dev
21:53 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has joined #lightning-dev
21:55 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
21:56 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
21:59 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #lightning-dev
22:02 -!- yzernik [~yzernik@12.203.56.101] has joined #lightning-dev
22:02 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
22:04 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
22:06 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
22:07 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
22:08 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
22:08 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
22:09 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
22:10 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
22:10 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
22:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
22:11 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
22:11 -!- melande [~melande@gateway/tor-sasl/melande] has joined #lightning-dev
22:12 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
22:13 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
22:19 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
22:20 -!- melande [~melande@gateway/tor-sasl/melande] has joined #lightning-dev
22:23 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Ping timeout: 264 seconds]
22:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]
22:39 -!- jeremyrubin [~jr@2601:645:c200:f539:d82f:3d65:91f6:9c31] has joined #lightning-dev
22:41 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
22:54 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
22:56 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
22:59 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Read error: Connection reset by peer]
22:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
22:59 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
22:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
22:59 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection]
22:59 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has quit [Remote host closed the connection]
22:59 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Write error: Connection reset by peer]
23:02 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #lightning-dev
23:03 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #lightning-dev
23:03 -!- yzernik [~yzernik@12.203.56.101] has quit [Quit: ZNC 1.7.5 - https://znc.in]
23:04 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has joined #lightning-dev
23:04 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Ping timeout: 240 seconds]
23:05 -!- yzernik [~yzernik@12.203.56.101] has joined #lightning-dev
23:15 -!- melande [~melande@gateway/tor-sasl/melande] has joined #lightning-dev
23:15 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lightning-dev
23:24 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
23:25 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
23:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
23:35 -!- weedcoder [~weedcoder@31.130.192.178.dynamic.wline.res.cust.swisscom.ch] has joined #lightning-dev
23:38 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
23:39 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #lightning-dev
23:39 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
23:53 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
23:54 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lightning-dev
--- Log closed Tue Aug 18 00:00:02 2020