--- Log opened Mon Jul 20 00:00:25 2020
00:05 -!- t-bast [~t-bast@2a01:e34:efde:97d0:7c36:b8fe:1026:6cd9] has joined #lightning-dev
00:12 -!- marcoagner [~user@2001:8a0:6a45:1900:2fd7:e0f0:d356:dd70] has joined #lightning-dev
00:25 -!- laptop [~laptop@212.203.87.198] has joined #lightning-dev
00:32 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Ping timeout: 265 seconds]
00:38 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
00:46 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Read error: Connection reset by peer]
00:46 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #lightning-dev
00:54 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 240 seconds]
01:00 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
01:07 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
01:11 -!- slivera [~slivera@103.231.88.27] has joined #lightning-dev
01:18 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has joined #lightning-dev
01:27 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #lightning-dev
02:01 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 240 seconds]
02:09 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 246 seconds]
02:11 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:f56e:fb68:b894:e88d] has joined #lightning-dev
02:16 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
02:26 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has quit [Quit: Pavlenex]
02:29 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
02:38 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
02:39 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has quit [Ping timeout: 240 seconds]
02:44 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
02:45 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has joined #lightning-dev
02:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
03:04 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 264 seconds]
03:05 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
03:08 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 265 seconds]
03:09 -!- Netsplit *.net <-> *.split quits: wumpus, luke-jr, belcher_, yzernik
03:09 -!- Netsplit over, joins: belcher_, luke-jr, yzernik, wumpus
03:10 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Max SendQ exceeded]
03:11 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
03:14 -!- lukedashjr is now known as luke-jr
03:25 -!- t-bast [~t-bast@2a01:e34:efde:97d0:7c36:b8fe:1026:6cd9] has quit [Ping timeout: 272 seconds]
03:28 -!- t-bast [~t-bast@2a01:e34:efde:97d0:7c36:b8fe:1026:6cd9] has joined #lightning-dev
03:28 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has quit [Quit: Pavlenex]
03:31 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has joined #lightning-dev
03:53 -!- reallll [~belcher@unaffiliated/belcher] has joined #lightning-dev
03:55 -!- reallll is now known as belcher
03:55 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:f56e:fb68:b894:e88d] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:56 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]
03:59 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 258 seconds]
04:02 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
04:31 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 246 seconds]
04:38 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
04:42 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
04:47 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 246 seconds]
04:50 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
04:54 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
05:05 -!- sr_gi [~sr_gi@static-144-88-225-77.ipcom.comunitel.net] has joined #lightning-dev
05:05 -!- sr_gi [~sr_gi@static-144-88-225-77.ipcom.comunitel.net] has left #lightning-dev []
05:10 -!- sr_gi [~sr_gi@static-144-88-225-77.ipcom.comunitel.net] has joined #lightning-dev
05:15 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lightning-dev
05:18 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
05:18 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
05:24 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:40e9:2682:c291:8cb6] has joined #lightning-dev
05:36 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:40e9:2682:c291:8cb6] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
05:48 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #lightning-dev
06:06 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
06:06 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #lightning-dev
06:07 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Remote host closed the connection]
06:08 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
06:09 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
06:09 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
06:13 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
06:14 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
06:17 -!- nicolasburtey [~nicolasbu@24-116-195-80.cpe.sparklight.net] has joined #lightning-dev
06:18 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 256 seconds]
06:18 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 240 seconds]
06:21 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
06:27 -!- slivera [~slivera@103.231.88.27] has quit [Remote host closed the connection]
06:27 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
07:00 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lightning-dev
07:28 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
07:28 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
07:34 -!- Bugz [~pi@035-134-226-003.res.spectrum.com] has quit [Quit: WeeChat 2.3]
07:37 -!- Bugz [~pi@2600-6c67-8880-0168-c71d-66c8-53c5-9584.res6.spectrum.com] has joined #lightning-dev
07:38 -!- yzernik [~yzernik@75-25-138-252.lightspeed.plalca.sbcglobal.net] has quit [Ping timeout: 240 seconds]
07:46 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
07:49 -!- laptop [~laptop@212.203.87.198] has quit [Ping timeout: 265 seconds]
07:56 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:a9ba:e7d1:8403:5903] has joined #lightning-dev
08:02 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
08:02 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
08:08 -!- t-bast [~t-bast@2a01:e34:efde:97d0:7c36:b8fe:1026:6cd9] has quit [Ping timeout: 272 seconds]
08:11 -!- t-bast [~t-bast@2a01:e34:efde:97d0:7c36:b8fe:1026:6cd9] has joined #lightning-dev
08:11 -!- t-bast [~t-bast@2a01:e34:efde:97d0:7c36:b8fe:1026:6cd9] has quit [Client Quit]
08:14 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:a9ba:e7d1:8403:5903] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:25 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has joined #lightning-dev
08:31 -!- mdunnio_ [~mdunnio@208.59.170.5] has joined #lightning-dev
08:34 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 256 seconds]
08:37 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 258 seconds]
08:42 -!- mol [~mol@unaffiliated/molly] has joined #lightning-dev
09:04 -!- th0th1 [~th0th@gateway/tor-sasl/th0th] has quit [Remote host closed the connection]
09:04 -!- th0th1 [~th0th@gateway/tor-sasl/th0th] has joined #lightning-dev
09:09 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
09:18 -!- nirved [~nirved@gateway/tor-sasl/nirved] has quit [Remote host closed the connection]
09:19 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
09:19 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #lightning-dev
09:23 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
09:23 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
09:31 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:188a:4539:27a:a21e] has joined #lightning-dev
09:33 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Remote host closed the connection]
09:34 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
09:38 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Ping timeout: 260 seconds]
09:40 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 246 seconds]
09:43 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
09:44 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
09:44 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Remote host closed the connection]
09:45 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
09:45 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Remote host closed the connection]
09:45 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
09:56 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
10:16 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has joined #lightning-dev
10:17 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has quit [Read error: Connection reset by peer]
10:17 -!- tryphe__ [~tryphe@unaffiliated/tryphe] has joined #lightning-dev
10:17 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Ping timeout: 258 seconds]
11:04 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:188a:4539:27a:a21e] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:15 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:188a:4539:27a:a21e] has joined #lightning-dev
11:28 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has quit [Quit: Pavlenex]
11:33 -!- Sajesajama [Salsa@gateway/vpn/protonvpn/sajesajama] has quit [Remote host closed the connection]
11:34 -!- Sajesajama [Salsa@gateway/vpn/protonvpn/sajesajama] has joined #lightning-dev
11:44 -!- th0th1 is now known as th0th
11:47 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has joined #lightning-dev
11:51 -!- Sajesajama [Salsa@gateway/vpn/protonvpn/sajesajama] has quit [Remote host closed the connection]
11:52 -!- Sajesajama [Salsa@gateway/vpn/protonvpn/sajesajama] has joined #lightning-dev
11:59 -!- Sajesajama [Salsa@gateway/vpn/protonvpn/sajesajama] has quit [Max SendQ exceeded]
12:00 -!- Sajesajama [Salsa@gateway/vpn/protonvpn/sajesajama] has joined #lightning-dev
12:12 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
12:13 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:188a:4539:27a:a21e] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
12:16 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Remote host closed the connection]
12:16 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
12:21 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Ping timeout: 258 seconds]
12:33 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 264 seconds]
12:37 -!- t-bast [~t-bast@2a01:e34:efde:97d0:7c36:b8fe:1026:6cd9] has joined #lightning-dev
12:56 -!- renepick1 [6dcb0e15@109.203.14.21] has joined #lightning-dev
12:58 -!- sstone [~sstone@112.ip-51-68-199.eu] has joined #lightning-dev
12:59 < t-bast> Good evening folks!
12:59 < cdecker> Good evening t-bast 
12:59 < niftynei> hello
12:59 < renepick1> hei hei (: 
13:00 < lndbot> <johanth> hei :slightly_smiling_face:
13:00 < sstone> Hi everyone!
13:02 < t-bast> what have you been up to these past two weeks?
13:02 < niftynei> c-lightning's been getting our 0.9 release out the door
13:02 <+roasbeef> same tryna get 0.11 out the door 
13:03 < t-bast> what's notable in these new releases?
13:03 <+roasbeef> also finally wrote up the dynamic commitments thing ;) will poast after this 
13:03 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
13:03 < niftynei> we're very excited about MPP support and having experimental anchors!
13:03 <+roasbeef> ooo nice y'all get anchors in niftynei ? 
13:03  * niftynei goes to double check the PR got merged
13:03 < t-bast> niftynei: experimental anchors, already? With interop tests completed?
13:04 < niftynei> oh no it's still unmerged :/
13:04 < t-bast> roasbeef: nice, eager to see that proposal
13:04 < cdecker> It's not in just yet, but it'd be experimental and not publicized in the release notes
13:04 < t-bast> ok, I have one pending question regarding anchors on the PR where I tagged rusty/ariard, still waiting for confirmation
13:04 < cdecker> Plan is to merge it as soon as 0.9.0 is out and get it interop tested, before making it the default
13:05 < t-bast> I started doing interop testing on anchors between eclair and lnd
13:05 <+roasbeef> t-bast: experimental support for a repliacted db (etcd), fixes for some force close de-sync issues (also might've found a spec issue in the state machine), 
13:05 <+roasbeef> the force close de-sync bugs took foreeevver to track down, but we're confident in the fixes we're gonna roll out 
13:05 < t-bast> interesting, I'm curious about that spec issue, worht digging into
13:06 <+roasbeef> they were triggered during chan reest, so if peers for w/e reason were very flappy it could trigger the closes more 
13:06 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev
13:06 < t-bast> that's great, less force-close makes it much easier to identify malicious actors :D
13:06 < rusty> Sorry I'm late.
13:06 <+roasbeef> yeh it's this re-orering thing, need to confirm it still, but it's possilbe (at least we did) send a sig/revoke on chan reest in a diff order than was actually sent in 
13:06 < t-bast> good morning rusty
13:07 < t-bast> roasbeef: interesting, that's something we've been chasing for a long while, if we can finally get to the bottom of this it would be great
13:07 <+roasbeef> we were workign on AMP, and some other psbt stuff, but that got pushed out a bit 
13:07 <+roasbeef> t-bast: ok nice to confirm there might actualy be something there
13:07 < rusty> niftynei: anchors didn't make the cut.... but can still test them.
13:08 < t-bast> nice, rusty I've tagged you in a last comment on the anchors PR regarding anchor cost when only one anchor materializes, just need to confirm/agree on the behavior
13:08 <+roasbeef> oh we're adding wumbo support too, better late than never, kek 
13:08 < t-bast> shall we start recording? who wants to chair?
13:09 < BlueMatt> roasbeef: ugh, yea, we had the same issue a while back, was a huge pain until I sucked it up and wrote a fuzzer for the state machine...eventually found a state machine design that fixed the whole mess all at once
13:10 < lndbot> <johanth> oh, yeah fuzz all the things
13:10 < rusty> t-bast: yes, and niftynei can chair? (Too early for me to volunteer)
13:11 < t-bast> my wifi is a bit spotty so I'd rather not chair in case I drop out for a few minutes, I drafted a small agenda here: https://github.com/lightningnetwork/lightning-rfc/issues/790
13:11  * t-bast votes for niftynei!
13:11 < niftynei> sure, i can chair!
13:11 < niftynei> #startmeeting
13:11 < lightningbot> Meeting started Mon Jul 20 20:11:28 2020 UTC.  The chair is niftynei. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:11 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:11 < niftynei> #info agenda at https://github.com/lightningnetwork/lightning-rfc/issues/790
13:12 < niftynei> according to this agenda i've got, it looks like 'CLTV expiry delta recommendations' is the first discussion topic
13:12 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Ping timeout: 246 seconds]
13:13 < niftynei> #topic CLTV delta recommendations
13:13 < niftynei> #link https://github.com/lightningnetwork/lightning-rfc/pull/785
13:13 < t-bast> since last meeting, conner raised a point about updating the default min-final-expiry-delta in Bolt 11 as well, which I did in the last commit
13:14 < t-bast> it requires a phased change from implementations: when an invoice doesn't specify min-final-expiry-delta, we should now use 18 instead of 9
13:14 < t-bast> however when receiving, we should either now write our min-final-expiry-delta in the invoice (instead of relying on a spec hard-coded default value)
13:15 < t-bast> or we'll need to keep accepting payments using min-final-expiry-delta=9 for backwards-compat with non-upgraded wallets/nodes that will send 9 by default
13:15 <+roasbeef> yeh the implicit thing wasn't the best idea
13:15 < rusty> t-bast: with the idea we can eventually rely on the default?... one day?
13:15 < t-bast> In eclair, I started explicitly setting min-final-expiry-delta in invoices
13:15 <+roasbeef> we should remove the implicit value and _always_ set
13:15 < t-bast> agreed, that's more future-proof
13:16 < t-bast> and just in case it's not specified in the invoice (because backwards-compat) we should now send 18 instead of 9
13:16 < rusty> Yeah, ack that.  Make it "Reader MUST >= 18 if not specified" and "Writer MUST specify".
13:17 < t-bast> rusty: SGTM, I was going to suggest something like that
13:17 < t-bast> I'll update the PR to reflect that
13:17 < t-bast> #action t-bast to update PR: bolt 11 writers MUST specify min-final-expiry-delta
13:18 < niftynei> does anyone have further commment on this topic item?
13:18 < niftynei> moving on then
13:19 < niftynei> #topic PR #787 add missing MAC check in Act Three
13:19 < niftynei> #link https://github.com/lightningnetwork/lightning-rfc/pull/787
13:19 <+roasbeef> seems sane, just approved on the PR, coudl argue that applies everywhere and not just on that step 
13:20 < renepick1> I already commented that one on git. seems logical
13:20 <+roasbeef> ah below there it has the same message also 
13:20 < t-bast> agreed, renepick1 pointed that this is mentioned at the beginning of the bolt, so maybe not necessary to say again
13:21 < t-bast> we do explicitly mention it in most places though...
13:21 < niftynei> it seems like this change mostly just makes the two decryptWithAD result sections identical
13:21 <+roasbeef> niftynei: yeh that's how I'm viewing it now 
13:21 < rusty> Being explicit is nice, coders can usually figure out checklists, and are bad with implied contexts.
13:21 < t-bast> for consistency, it's probably worth applying
13:22 < niftynei> the symmetry seems reasonable
13:22 < renepick1> agree with rusty. we have it at other spots and it makes it easier for coders than cross refs. For motivation I would still keep the sentence at the beginning though
13:22 <+roasbeef> lgmt'd on the pr 
13:22 < t-bast> same, ACKed
13:22 < niftynei> ok looks like we've got two acks and no issues. i'll merge
13:23 < niftynei> #action niftynei to merge PR #787
13:23 < niftynei> next up is our Long Term Updates discussion
13:24 < niftynei> anchor outputs is listed up first but since renepick1 is here today let's start with the FoaF and rebalancing topic 
13:24 <+roasbeef> anchor seems to be moving along on teh PR, so maybe skip it to let other stuff be discussed since it's kinda dominated the convo the past few meetings? 
13:25 < niftynei> sg! 
13:25 < niftynei> #topic FoaF and rebalancing
13:25 < t-bast> I think the PR is in good shape, it was easy to implement from scratch. The only place where I hesitated and did it differently from lnd is the case where only one anchor materializes. In that case I used to refund the 330 to the funder's output, whereas lnd doesn't. For simplicity's sake, I think the lnd way of always deducing 660 sats makes sense.
13:25 < t-bast> (was my only feedback for anchor that I'd like to see cleared out soon)
13:25 < renepick1> did anyone have the chance to look at the FOAF balance sharing proposal? 
13:25 < rusty> t-bast: yeah, I assumed 660 basically gets added to the fee.
13:26 <+roasbeef> t-bast: yeh less things moving around kinda, can see it as an extension of the reserve 
13:26 < renepick1> I guess the main question is if we want to start thinking about sharing balances with neighbors and if the query and reply should look in the way how I proposed them
13:26 < niftynei> #link https://github.com/lightningnetwork/lightning-rfc/pull/780
13:27 <+roasbeef> renepick1: sharing balances to give more path finding context, or like down stream forwarding context? 
13:27 < rusty> I'm confused by the FoaF proposal.  It's unclear what to do with this information, and why is there a query and a reply, not just a "broadcast"?
13:28 < rusty> It seems like it could let a node find rebalancing triangles, but not broader topologies.  And all it allows us more "friendly" rebalancing, but there's no mechanism for giving a discount?
13:28 < renepick1> the information could be used to a) make path finding decisions b) if utilized properly help with JIT-rebalancing (e.g. to prevent channel probing attacks)
13:28 < renepick1> circles of length 4 are also included and the ones of length 5 could be guessed pretty reliably
13:28 < t-bast> renepick1: at first glance, it feels like we hope the shared balance information doesn't move too quickly, right? Because it could be quickly outdated if many transactions are happening
13:28 < renepick1> as a node could ask all its friends
13:29 < renepick1> I decided against broadcasting as a node wants the information at a certain point in time
13:29 < renepick1> goes in the same direction as t-bast says about outdating (if I understand this correctly)
13:30 < niftynei> i think the stated goals of this proposal are good, but it seems like it's got a lot of WIP markers on it still
13:30 < rusty> renepick1: I think it leaks information if I only ask for it when a payment is going through though.  Maybe better as "broadcast no more than every 1 minute": like anything, it's a "good enough" gossip attempt.
13:31 < rusty> (Plus, adding a new optional message is trivial)
13:31 < niftynei> renepick1 it seems like having an implementation done might help fill in a lot of the gaps here
13:31 < renepick1> rusty: I could pose the query also at random times
13:32 < rusty> renepick1: which is the same only marginally less efficient and more complex?
13:32 < renepick1> @niftynei there is an implementation as a c-lightning plugin. but just to send the query and the reply. not to utilize the results yet
13:32 < renepick1> @rusty it allows the node to also include the moments when it "needs" the information to know it doesn't have outdated information 
13:32 < rusty> renepick1: I would suggest simply sending a set of "flow_dir/amt/scid" tuples (i.e. a new subtype).
13:32 < renepick1> but I will think about this
13:33 < rusty> renepick1: that's not possible, since it can change?
13:33 <+roasbeef> if it's path finding, then is it polling based? to avoid having to have even more flooded information 
13:33 < renepick1> @roasbeef what do you mean with flooded information? 
13:33 < cdecker> Well, supposedly the FOAF network is rather small already, so flooding shouldn't be too much of an issue
13:34 <+roasbeef> also fwiw, a few published papers have sown how easy it is to map thing based on probing, but ofc there're other mitigations like setting a lower max_htlc, etc 
13:34 <+roasbeef> every thing*
13:34 < renepick1> polling in general would probably be less traffic than broadcasting though. but I will tinker about the broadcast question
13:35 < renepick1> @roasbeef that is part of the rational. probing FOAF seems trivial in most cases anyway so why not just asking nicely
13:35  * roasbeef zooms out to mention that there's been a TON of published research on LN this year which is great
13:35 < cdecker> Problem with probing is that it gets destroyed by JIT-rebalancing, which changes the balances as a reaction to probes
13:35 <+roasbeef> cdecker: does it tho? as rebalancing can fail, and I can still craft other routes to occupy channels and probe what I really wana
13:35  * cdecker agrees that it's nice to see all the good research, though a lot to read it all :-)
13:36 < rusty> Yes, I was surprised that this doesn't include JIT routing.  I kind of expected it to give a token which you ca put in your onion to get a "free" HTLC...
13:36 <+roasbeef> heh yeh i've read maybe 20% of it all
13:36 < renepick1> @rusty: I thought I would seperate it from free HTLC stuff and rebalancing onions because I thought the information sharing would be useful for many other settings
13:36 < cdecker> I assumed that the information can be used for a JIT rebalancing / routing, which I also assumed was the reason for active queries rather than regular broadcasts
13:37 <+roasbeef> also re jit rebalancing: why would a node try to optimisticlaly rebalance (which costs them fees), for an HTLC that might not actually be resolved? 
13:37 < renepick1> can I summerize that we are open to balance sharing within the friend of a friend network and that the question is if it should be broadcast or a query / reply? 
13:38 < rusty> renepick1: yes, but I'd also like to see a free rebalancing protocol sketched out on top (maybe that's just me).
13:38 < renepick1> @roasbeef: I think the main argument for jit rebalancing is to have circular paths with costfree htlcs if every node along the circle decreses their imbalance. it is actually a recommendation for the reply to only include channels along wich a node would want to rebalance
13:39 <+roasbeef> but then how do you ensure the cohort does the rebalancing in an atomic way?
13:39 <+roasbeef> like you could doa buncha work, then the htlc gets canceleld back in the next hop due to some policy violation 
13:39 < renepick1> @rusty: you have my support for that! though it might be tricky to have the free fee rebalancing in a way that it won't be abused to deliver regular payments
13:39 < rusty> renepick1: yes :)
13:39 <+roasbeef> not convined that it makes sense to generate even _more_ forwarding traffic in an attempt to forward a single origin HTLC 
13:40 < niftynei> it seems like this proposal might greatly benefit from a higher level design and use document?
13:40 < rusty> roasbeef: agreed, unless there's some clever free rebalancing protocol, then you can use that to mess up probes.
13:40 < renepick1> use document as in product requirement document describing use cases? 
13:40 < t-bast> agreed with niftynei, maybe instead of a spec PR start with something in the "proposals" format (like I did for blinded paths/trampoline) that's a bit higher level so that we discuss the concept first
13:41 < rusty> (Though I thought I had a proposal to include an "amount hint" in channel_temporarily_unavailable replies now we have MPP...)
13:41 <+roasbeef> in terms of negotaiting the rebalancing up front and making in atomic, there's this: https://dl.acm.org/doi/10.1145/3133956.3134033, not sure if they evern deployed it tho 
13:41 < t-bast> have a look at the trampoline PR for example, I changed it to include a higher-level design doc with diagrams in the "proposals" folder, I hope it will be helpful
13:41 < cdecker> t-bast: well it being a completely separate bolt sort of makes the proposal redundant imho, it's already a well-contained document
13:42 < t-bast> cdecker: yes, but I meant something less in "spec format" and more diagram-y / higher level at first :D
13:42 < cdecker> Right
13:42 < renepick1> @roasbeef I think revive is not quite what we want
13:42 < niftynei> renepick1, you can find t-bast's route blinding proposal here https://github.com/lightningnetwork/lightning-rfc/pull/765/files
13:43 < renepick1> @t-bast I can try to add a high level proposal / use case document so that we can have a more focused discussion. but the feedback today is very helpful so that I can move this forward
13:43 <+roasbeef> not saying it's what we want renepick1 , but just some existing related research
13:43 < niftynei> ok in the sake of time, let's move onto a quick anchor outputs discussion then
13:44 < renepick1> @roasbeef : just saying that I looked at revive because I hoped they would solve the problem for us. but how I understood I think they didn't but it is certainly a point in the right direction
13:44 < niftynei> #action renepick1 to consider feedback and update proposal/PR etc
13:44 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #lightning-dev
13:44 < niftynei> #topic anchor outputs
13:44 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has quit [Ping timeout: 256 seconds]
13:45 < cdecker> Awesome, that was a great discussion renepick1 and everybody ^^
13:45 < niftynei> #link https://github.com/lightningnetwork/lightning-rfc/pull/688
13:46 <+roasbeef> so joost is on vacation, so johan is taking over the PR 
13:46 <+roasbeef> w.r.t fixing it up n stuff
13:46 < t-bast> I've been able to create anchor outputs channels between eclair and lnd
13:46 < lndbot> <johanth> woop
13:46 < t-bast> and exchange HTLCs/update commitments
13:46 < lndbot> <johanth> cool, yeah mostly waiting from feedback from other impls
13:47 < niftynei> i think t-bast had a comment about the 660 vs 330 (trimming etc?)
13:47 < lndbot> <johanth> to sort out the latest quirks/questions on the current PR
13:47 < t-bast> but I'm having issues during mutual close, signatures don't match...and unfortunately even at debug level lnd doesn't log the tx it signs, so I'm currently combing through your code to add it for my tests :D
13:47 <+roasbeef> t-bast: interesting, could give you a patch to add more logging there 
13:47 < t-bast> niftynei: I think rusty said earlier that he also thinks we should always deduce 660 sats even if one anchor doesn't materialize for simplicity's sake
13:48 < niftynei> t-bast: ah i missed that :thumbsup:
13:48 < t-bast> roasbeef: don't worry, I think I've got it, I'm in `CreateCloseProposal` in channel.go, I should be able to add that log line and figure it out by tomorrow
13:48 < rusty> t-bast: and now I've commented the same on-issue.
13:48 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
13:48 < t-bast> great, so that clears out the un-materialized anchor refund, apart from that the state of the PR looks mostly good to me 
13:49 < rusty> Yeah, close tx should *not* have anchors.  Nor should the 660 count towards the "maximum allowable fee" for close tx.
13:49 < t-bast> test vectors work, just need to finish interop tests and then do a ton of work on figuring out good ways of doing automatic fee bumping
13:49 < lndbot> <johanth> status on the lnd implementaiont is that we have been running it in the wild for a while, no major issues
13:49 < rusty> i.e. "base fee" definition is unchanged.
13:49 < lndbot> <johanth> no automatic fee bumping yet tho
13:50 < rusty> johanth: any particular node I should test against?  Mainnet OK...
13:50 < lndbot> <johanth> hehe, I can send you a node URI for sure…
13:50 < lndbot> <johanth> still using the 1337 bit
13:50 < lndbot> <johanth> so that has to be flipped before going non-experimental
13:51 < t-bast> rusty: where are you on the implementation on the c-lightning side?
13:52 < rusty> t-bast: it's implemented, pending interop testing (didn't make the coming release).  Doesn't do *anything* with the anchors yet, but ignore them....
13:52 < rusty> johanth: ah, OK, I'll hack that feature in...
13:53 < t-bast> good, eclair is around the same state as well
13:53 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Ping timeout: 240 seconds]
13:53 < niftynei> do we have any outstanding action items for the anchors PR?
13:53 < t-bast> I think we should be able to finalize interop testing before the next meeting
13:53 < t-bast> niftynei: nope, good to go!
13:54 < niftynei> #action t-bast + rusty to work on interop testing with lnd's anchor outputs impl; will update at next spec meeting
13:54 < niftynei> ok we've got 5min
13:54 < niftynei> let's talk about protocol tests!
13:54 < niftynei> #topic protocol test suite
13:54 < niftynei> rusty do you have a link for this?
13:55 < rusty> So, cdecker is working on finishing the Sphinx implementation in python, so I can actually test *successful* HTLCs..
13:55 < rusty> https://github.com/rustyrussell/lnprototest
13:55 < niftynei> #link https://github.com/rustyrussell/lnprototest
13:55 < rusty> (Though you can get an awful long way without actually forwarding an HTLC, turns out).
13:55 <+roasbeef> niiice, have been taking a look at what we need to do in lnd to be able to run as a tester 
13:55 < cdecker> Aaaaaalmost there, I promise ^^
13:56 < rusty> roasbeef: hopefully it's getting less, the test framework is smart enough to adapt, though youj need to be able to reach into your node and extract the secrets.
13:56 <+roasbeef> yeh seems the main thing is first being able to start an instance w/ a set of canned private keys, and dump other secrets that we may derive off that, so like a special build dev tag 
13:56 < rusty> Technically this means I've implemented anchor outputs *twice*, but damn it was easier in lnprototest.
13:57 < t-bast> damn, I'll need to learn some python :(
13:57  * niftynei (sympathizes with t-bast)
13:57 < cdecker> Well there is jython xD
13:57 < rusty> roasbeef: doesn't need that any more (though c-lightning still does it taht way), but can query node keys at runtime.
13:57 <+roasbeef> it's like fancy python 
13:57 <+roasbeef> type hints n stuff 
13:57 <+roasbeef> idk what version of python we're even on anymore lol 
13:57 < rusty> (Don't get me started on type hints in Python....)
13:58 <+roasbeef> 3.8....woah, and somehow python 2.7 isn't dead yet lol
13:58 < rusty> We actually contracted a Python person to look at my code.... TL;DR: it got better.
13:58 < t-bast> rusty: xD
13:58 < cdecker> roasbeef: 2.X has officially reached End of Life last new year
13:59 < t-bast> rusty: so the tl;dr on what we need to do, is plug some hooks in implementations to extract secrets somehow, then write some python to connect with lnprototest?
13:59 < rusty> Yeah, I'm aiming for 3.6+, but I know it works with 3.8 because that's here.
13:59 < niftynei> rusty is there anything you want people to know when trying to write tests / runners for lnprototest?
13:59 <+roasbeef> cdecker: only took like a decade or something? kek
13:59 < rusty> t-bast: yeah, since the only runner currently is clightning, copy that.  We should probably share some stuff (.e.g a heap of it us just to drive bitcoind for example)
14:00 < rusty> And looking fwd to niftynei writing the dual fund tests and providing feedback on what it's like.,
14:00 < niftynei> soon! TM
14:01 < niftynei> i actually need to head out here shortly
14:01 < niftynei> are there any action items for the lnprototests?
14:01 < rusty> There'll be some flux as we will no doubt add more requirements for backends so we can test more stuff, but we can do a *lot* with what's there.
14:01 < rusty> niftynei: not really, just get people to try to attach it to their implementations.
14:02 < niftynei> #action niftynei to write dual funding prototests to dogfood the lnprototest docs
14:02 < cdecker> Always remember: the official lightning motto is "duo septimanas" (two weeks) :-)
14:02 < niftynei> ehehehe
14:02 < t-bast> great, not sure we'll have time to do it in the next 2-weeks period for eclair but if there's a bit of time available I'll take a look at it!
14:03 < niftynei> #action lnd + eclair to investigate the runner implementation requirements (time permitting) ;)
14:03 < niftynei> ok i think that's all we have time for today
14:03 < t-bast> thanks for chairing niftynei!
14:03 < niftynei> thanks everyone for your input and participation and we'll meet again soon!
14:03 < cdecker> Great meeting everyone ^^
14:03 < niftynei> #endmeeting
14:03 < lightningbot> Meeting ended Mon Jul 20 21:03:59 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
14:03 < lightningbot> Minutes:        http://www.erisian.com.au/meetbot/lightning-dev/2020/lightning-dev.2020-07-20-20.11.html
14:03 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/lightning-dev/2020/lightning-dev.2020-07-20-20.11.txt
14:03 < lightningbot> Log:            http://www.erisian.com.au/meetbot/lightning-dev/2020/lightning-dev.2020-07-20-20.11.log.html
14:04 < t-bast> thanks everyone!
14:04 < cdecker> Thanks for chairing niftynei ^^
14:04 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
14:04 -!- t-bast [~t-bast@2a01:e34:efde:97d0:7c36:b8fe:1026:6cd9] has quit [Quit: Leaving]
14:04 < rusty> See you all in duo septimanas!
14:07 -!- renepick1 [6dcb0e15@109.203.14.21] has quit [Remote host closed the connection]
14:09 < lndbot> <johanth> Bye all :)
14:09 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Ping timeout: 260 seconds]
14:20 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
14:23 -!- sstone [~sstone@112.ip-51-68-199.eu] has quit [Quit: Leaving]
14:25 -!- yzernik [~yzernik@2600:1700:dc40:3dd0:184b:2098:63a0:2478] has joined #lightning-dev
14:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds]
14:42 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has joined #lightning-dev
14:48 -!- slivera [~slivera@103.231.88.10] has joined #lightning-dev
15:00 -!- marcoagner [~user@2001:8a0:6a45:1900:2fd7:e0f0:d356:dd70] has quit [Ping timeout: 272 seconds]
15:08 -!- slivera [~slivera@103.231.88.10] has quit [Remote host closed the connection]
15:45 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Remote host closed the connection]
15:45 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has joined #lightning-dev
15:50 -!- proofofkeags [~proofofke@c-65-50-169-164.hs.gigamonster.net] has quit [Ping timeout: 264 seconds]
15:52 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has quit [Remote host closed the connection]
15:53 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has joined #lightning-dev
15:56 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 258 seconds]
15:58 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
16:01 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
16:01 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has quit [Quit: Pavlenex]
16:03 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
16:40 -!- mdunnio_ [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
16:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev
17:12 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lightning-dev
17:15 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
17:17 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds]
17:21 -!- slivera [~slivera@103.231.88.10] has joined #lightning-dev
17:37 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 240 seconds]
17:44 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
17:46 -!- riclas [riclas@77.7.37.188.rev.vodafone.pt] has quit [Ping timeout: 260 seconds]
17:50 -!- inara` [~inara@static.38.6.217.95.clients.your-server.de] has quit [Quit: Leaving]
17:54 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
17:56 -!- proofofkeags [~proofofke@174-29-8-246.hlrn.qwest.net] has joined #lightning-dev
17:59 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 258 seconds]
18:01 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lightning-dev
18:26 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
18:26 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
18:48 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 256 seconds]
18:49 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #lightning-dev
19:00 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
19:01 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
19:15 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Ping timeout: 256 seconds]
19:19 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
19:24 -!- proofofkeags [~proofofke@174-29-8-246.hlrn.qwest.net] has quit [Remote host closed the connection]
19:25 -!- proofofkeags [~proofofke@174-29-8-246.hlrn.qwest.net] has joined #lightning-dev
19:28 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
19:29 -!- proofofkeags [~proofofke@174-29-8-246.hlrn.qwest.net] has quit [Ping timeout: 264 seconds]
19:29 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev
19:58 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
20:04 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #lightning-dev
20:48 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Ping timeout: 256 seconds]
20:50 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
20:52 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
20:57 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
21:04 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
21:22 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
21:23 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 246 seconds]
21:26 -!- lukedashjr is now known as luke-jr
21:29 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
21:37 -!- rdymac [uid31665@gateway/web/irccloud.com/x-fasvjyjtbkoqaehj] has quit [Quit: Connection closed for inactivity]
22:06 -!- vtnerd [~vtnerd@173-17-206-92.client.mchsi.com] has quit [Ping timeout: 264 seconds]
22:41 -!- vtnerd [~vtnerd@173-17-206-92.client.mchsi.com] has joined #lightning-dev
23:07 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 256 seconds]
23:09 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
23:11 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
23:13 -!- arowser [~arowser1@67.230.166.11] has joined #lightning-dev
23:16 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
23:16 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev
23:27 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
23:33 -!- arowser [~arowser1@67.230.166.11] has quit [Ping timeout: 264 seconds]
23:37 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #lightning-dev
23:38 -!- inara [~inara@static.38.6.217.95.clients.your-server.de] has joined #lightning-dev
23:47 -!- Pavlenex [~Thunderbi@195.181.160.173.adsl.inet-telecom.org] has joined #lightning-dev
23:48 -!- marcoagner [~user@bl11-17-219.dsl.telepac.pt] has joined #lightning-dev
--- Log closed Tue Jul 21 00:00:19 2020