--- Log opened Mon Oct 16 00:00:57 2023
00:24 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
00:24 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
00:52 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #lightning-dev
01:00 -!- riclas [~riclas@26.27.71.148.rev.vodafone.pt] has joined #lightning-dev
01:00 -!- warmhug [~warmhug@gateway/tor-sasl/warmhug] has quit [Ping timeout: 252 seconds]
01:08 -!- warmhug [~warmhug@gateway/tor-sasl/warmhug] has joined #lightning-dev
01:11 -!- b42 [~mmilata@b42.cz] has joined #lightning-dev
02:00 -!- Zenton [~user@user/zenton] has joined #lightning-dev
03:54 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
04:40 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Read error: Connection reset by peer]
04:40 -!- warmhug [~warmhug@gateway/tor-sasl/warmhug] has quit [Read error: Connection reset by peer]
04:41 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
04:41 -!- warmhug [~warmhug@gateway/tor-sasl/warmhug] has joined #lightning-dev
04:54 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:23 -!- test__ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #lightning-dev
05:24 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #lightning-dev
05:28 -!- test__ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 264 seconds]
05:29 -!- flooded is now known as _flood
06:10 -!- endothermicdev [~endotherm@2600:1700:8481:8900:84a6:e2c0:2568:5fe1] has quit [Remote host closed the connection]
06:11 -!- endothermicdev [~endotherm@2600:1700:8481:8900:82b6:3b33:6838:c1e0] has joined #lightning-dev
06:21 -!- endothermicdev [~endotherm@2600:1700:8481:8900:82b6:3b33:6838:c1e0] has quit [Quit: Leaving]
08:37 -!- warmhug [~warmhug@gateway/tor-sasl/warmhug] has quit [Remote host closed the connection]
08:39 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
08:39 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #lightning-dev
08:41 -!- warmhug [~warmhug@gateway/tor-sasl/warmhug] has joined #lightning-dev
08:42 -!- warmhug [~warmhug@gateway/tor-sasl/warmhug] has quit [Client Quit]
09:04 -!- proofofkeags [~proofofke@172.59.231.27] has joined #lightning-dev
09:53 -!- proofofkeags [~proofofke@172.59.231.27] has quit [Remote host closed the connection]
09:54 -!- proofofkeags [~proofofke@2607:fb90:6d8b:86ab:b885:7dbc:f6f7:ae1] has joined #lightning-dev
09:58 -!- proofofkeags [~proofofke@2607:fb90:6d8b:86ab:b885:7dbc:f6f7:ae1] has quit [Ping timeout: 260 seconds]
10:03 < BlueMatt[m]> so we're working on removing the application of htlc-error-received channel_updates to the network graph. one interesting question - do we remove the permanent-failure-removes-channel too, or do we keep that?
10:04 < BlueMatt[m]> Personally I'm leaning towards keeping it, but it does have the same privacy issues (just you can only do it once per channel, and you lose out on forwarding fees if you start doing it too much)
10:11 < realtbast[m]> Can you detail what you mean exactly by "removing the application of htlc-error-received channel_updates to the network graph"? That's unclear to me
10:14 < BlueMatt[m]> in the previous call, rusty pointed out that if you take a channel_update from an update_fail_htlc onion error packet and apply it to your network graph, the node that failed the htlc can trivially identify who the sender was
10:14 < BlueMatt[m]> which is, uhhhh, a really bad privacy issue
10:19 < realtbast[m]> gotcha, I get what you mean now
10:20 < realtbast[m]> in eclair we don't apply those channel updates to the graph or retransmit them
10:20 < BlueMatt[m]> has that always been the case?
10:20 < realtbast[m]> yes I believe so
10:20 < BlueMatt[m]> oh lol, why didnt you tell the rest of us :p
10:21 < BlueMatt[m]> but, yea, imo we should remove them from the onion error entirely.
10:21 < realtbast[m]> I wasn't on the last call :D
10:21 < BlueMatt[m]> (nodes already have to handle the missing-channel_update case because CLN spuriously generates them sometimes already 😂)
10:23 -!- warmhug [~warmhug@gateway/tor-sasl/warmhug] has joined #lightning-dev
10:27 < BlueMatt[m]> so back to the other question - if you get a permenent channel failure error, do you remove the channel info from your graph?
10:30 < realtbast[m]> actually I'm not a 100% sure of my previous claim, I'll need to dive into that code again, it's been a while!
10:31 < realtbast[m]> I'll have a closer look at that tomorrow and will let you know
10:35 -!- proofofkeags [~proofofke@172.58.60.226] has joined #lightning-dev
11:59 -!- proofofkeags [~proofofke@172.58.60.226] has quit [Remote host closed the connection]
12:00 -!- proofofkeags [~proofofke@2607:fb90:6d1c:c8fc:b13c:a856:a3a:a2ec] has joined #lightning-dev
12:04 -!- proofofkeags [~proofofke@2607:fb90:6d1c:c8fc:b13c:a856:a3a:a2ec] has quit [Ping timeout: 248 seconds]
14:38 -!- proofofkeags [~proofofke@8.36.227.157] has joined #lightning-dev
14:42 -!- proofofkeags [~proofofke@8.36.227.157] has quit [Ping timeout: 240 seconds]
15:31 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
15:32 -!- jonatack [~jonatack@user/jonatack] has joined #lightning-dev
15:33 -!- DarrylTheFiiish [~DarrylThe@user/DarrylTheFish] has quit [Remote host closed the connection]
15:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
15:34 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has joined #lightning-dev
15:39 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Ping timeout: 258 seconds]
16:40 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #lightning-dev
16:44 -!- _flood [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 264 seconds]
16:44 -!- proofofkeags [~proofofke@65.158.198.4] has joined #lightning-dev
17:17 -!- proofofkeags [~proofofke@65.158.198.4] has quit [Remote host closed the connection]
17:17 -!- proofofkeags [~proofofke@65.158.198.4] has joined #lightning-dev
17:28 -!- proofofkeags [~proofofke@65.158.198.4] has quit [Ping timeout: 240 seconds]
17:29 -!- proofofkeags [~proofofke@65.158.198.4] has joined #lightning-dev
17:34 -!- proofofkeags [~proofofke@65.158.198.4] has quit [Ping timeout: 272 seconds]
18:14 -!- riclas [~riclas@26.27.71.148.rev.vodafone.pt] has quit [Ping timeout: 260 seconds]
18:48 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has joined #lightning-dev
19:35 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 252 seconds]
20:18 -!- warmhug [~warmhug@gateway/tor-sasl/warmhug] has quit [Remote host closed the connection]
20:18 -!- warmhug [~warmhug@gateway/tor-sasl/warmhug] has joined #lightning-dev
20:31 -!- DarrylTheFiish [~DarrylThe@user/DarrylTheFish] has joined #lightning-dev
20:34 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Ping timeout: 248 seconds]
20:43 -!- DarrylTheFiish [~DarrylThe@user/DarrylTheFish] has quit [Remote host closed the connection]
20:50 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has joined #lightning-dev
20:51 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Remote host closed the connection]
20:52 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has joined #lightning-dev
20:54 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Remote host closed the connection]
20:55 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has joined #lightning-dev
20:57 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Read error: Connection reset by peer]
21:40 -!- zeropoint [~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net] has joined #lightning-dev
21:55 -!- zeropoint [~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net] has quit [Quit: leaving]
22:04 -!- Ademan [~ademan@47.161.41.51] has quit [Quit: leaving]
--- Log closed Tue Oct 17 00:00:58 2023