--- Log opened Thu Jun 23 00:00:00 2022
00:05 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 240 seconds]
00:10 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #lightning-dev
00:14 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Quit: Ping timeout (120 seconds)]
00:14 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Quit: Ping timeout (120 seconds)]
00:14 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #lightning-dev
00:19 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #lightning-dev
00:26 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Read error: Connection reset by peer]
00:26 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #lightning-dev
00:40 -!- esats [~bosats@2601:47:4285:c7f0:ebc1:1ac3:c332:363e] has quit [Ping timeout: 248 seconds]
00:40 -!- evbo [~bosats@2601:47:4285:c7f0:927:e45d:8260:af32] has joined #lightning-dev
01:00 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has joined #lightning-dev
01:02 -!- valwal0 [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #lightning-dev
01:04 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Ping timeout: 248 seconds]
01:04 -!- valwal0 is now known as valwal
01:09 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Quit: Ping timeout (120 seconds)]
01:09 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Quit: Ping timeout (120 seconds)]
01:09 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #lightning-dev
01:19 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #lightning-dev
01:30 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Ping timeout: 240 seconds]
01:30 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Ping timeout: 272 seconds]
02:04 -!- kexkey [~kexkey@178.249.214.18] has quit [Ping timeout: 248 seconds]
02:06 -!- kexkey [~kexkey@178.249.214.10] has joined #lightning-dev
02:09 < cdecker[m]> Trying to wrap my head around how everybody implemented zeroreserve: the spec states that "MUST set channel_reserve_satoshis greater than or equal to dust_limit_satoshis", and I was told some implementations actually set reserve=0 (for peers that are in an allowlist).
02:10 < cdecker[m]> I was under the impression that this requirement would be broken, because clearly we shouldn't allow dropping the dust limit below 546sats, but is it though? I expect dropping the dust level this low would actually have some serious consequences on commitment txs (HTLC elision etc), but does it?
02:11 < cdecker[m]> How are other implementations handling this?
02:21 < realtbast[m]> You're right, this is directly conflicting with the dust limit requirement. What we do for Phoenix is that we keep the dust limit unchanged, but just allow the reserve to go below that to zero. We simply skip the reserve checks anywhere we have them, but don't modify anything else in the protocol.
02:25 < cdecker[m]> Ok, that's good to know. Would it make sense for me to propose removal of those requirements, since LDK, CLN and Eclair seem to all allow dipping below the dust limit (when configured accordingly), weakening them to be a suggestion and adding warnings about the semi-trusted nature of these settings? I really don't like allowing stuff in CLN that knowingly is non-compliant.
02:30 < realtbast[m]> Yes, I think that would make sense. Or we could also standardize how we do zero-reserve (e.g. with a feature bit) and in that case explicitly bypass that requirement in the spec?
02:33 < cdecker[m]> Dunno, it seems like it's rather simple, and given the signalling confusion that zeroconf caused, I'm rather hesitant to add yet another item to the negotiation. Though it might make sense since CLN still fails fundings if the reserve >= dust on the incoming channel is not respected, making "just self-declare unsafe" a breaking change for us at least (a funding that a zeroreserve node would consider valid was not valid before the
02:33 < cdecker[m]> removal), so there is an argument for adding that explicit signalling
02:36 < realtbast[m]> If you want I can submit that PR since we already have running code for it ;) 
02:44 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #lightning-dev
02:45 < cdecker[m]> Same here, just removing the compilation guards that I had in place and replacing it with a command line flag, which caused me to wonder if spec changes are desired.
02:50 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #lightning-dev
03:09 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has joined #lightning-dev
03:48 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has quit [Ping timeout: 240 seconds]
04:17 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has joined #lightning-dev
04:33 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has quit [Ping timeout: 240 seconds]
05:01 -!- Common__ [~Common@096-033-221-075.res.spectrum.com] has quit [Quit: Leaving]
05:34 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has joined #lightning-dev
05:52 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has quit [Ping timeout: 246 seconds]
06:02 -!- flooded is now known as _flood
06:46 -!- jespada [~jespada@cpc121022-nmal24-2-0-cust171.19-2.cable.virginm.net] has quit [Ping timeout: 256 seconds]
06:50 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
06:51 -!- jespada [~jespada@cpc121022-nmal24-2-0-cust171.19-2.cable.virginm.net] has joined #lightning-dev
06:51 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Client Quit]
09:49 -!- lightningbot [lightningb@172.104.61.193] has quit [Remote host closed the connection]
09:49 -!- lightningbot [lightningb@azure.erisian.com.au] has joined #lightning-dev
09:55 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has joined #lightning-dev
09:58 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 255 seconds]
10:14 -!- belcher [~belcher@user/belcher] has joined #lightning-dev
10:18 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
10:51 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Quit: Konversation terminated!]
11:17 -!- lightningbot [lightningb@azure.erisian.com.au] has quit [Ping timeout: 246 seconds]
11:17 -!- lightningbot [~supybot@2400:8901::f03c:91ff:febb:bbc1] has joined #lightning-dev
11:52 -!- jarthur [~jarthur@user/jarthur] has joined #lightning-dev
12:14 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
12:26 -!- belcher [~belcher@user/belcher] has quit [Quit: Leaving]
13:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds]
13:31 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
14:08 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds]
14:10 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
14:26 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds]
14:30 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
15:07 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 268 seconds]
16:37 -!- rusty [~rusty@pa49-178-164-157.pa.nsw.optusnet.com.au] has joined #lightning-dev
17:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
17:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
17:48 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...]
18:16 -!- _flood [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Read error: Connection reset by peer]
18:17 -!- _flood [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #lightning-dev
18:20 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
18:25 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has quit [Ping timeout: 240 seconds]
18:59 -!- rusty [~rusty@pa49-178-164-157.pa.nsw.optusnet.com.au] has left #lightning-dev []
19:57 -!- jarthur_ [~jarthur@user/jarthur] has joined #lightning-dev
19:58 -!- jarthur [~jarthur@user/jarthur] has quit [Ping timeout: 264 seconds]
20:08 -!- z9z0b3t1c [~z9z0b3t1c@145.224.66.51] has joined #lightning-dev
20:10 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has quit [Ping timeout: 248 seconds]
20:13 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has joined #lightning-dev
20:15 -!- z9z0b3t1c [~z9z0b3t1c@145.224.66.51] has quit [Ping timeout: 256 seconds]
20:23 -!- z9z0b3t1c [~z9z0b3t1c@145.224.65.191] has joined #lightning-dev
20:25 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has quit [Ping timeout: 248 seconds]
20:26 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has joined #lightning-dev
20:28 -!- z9z0b3t1c [~z9z0b3t1c@145.224.65.191] has quit [Ping timeout: 244 seconds]
20:32 -!- zeropoint [~alex@c-67-169-157-130.hsd1.ca.comcast.net] has joined #lightning-dev
20:33 -!- zeropoint [~alex@c-67-169-157-130.hsd1.ca.comcast.net] has quit [Client Quit]
20:33 -!- z9z0b3t1c [~z9z0b3t1c@145.224.65.157] has joined #lightning-dev
20:35 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has quit [Ping timeout: 248 seconds]
21:53 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
21:53 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #lightning-dev
22:15 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Remote host closed the connection]
22:15 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Write error: Connection reset by peer]
22:16 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #lightning-dev
22:17 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
22:43 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 268 seconds]
22:50 -!- faceface [~faceface@user/faceface] has quit [Quit: Lost terminal]
--- Log closed Fri Jun 24 00:00:01 2022