--- Log opened Mon Dec 19 00:00:49 2022
00:37 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has joined #lightning-dev
00:52 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
00:52 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #lightning-dev
00:53 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has quit [Ping timeout: 255 seconds]
00:54 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has joined #lightning-dev
00:55 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 255 seconds]
00:56 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
00:59 -!- riclas [~riclas@26.27.71.148.rev.vodafone.pt] has joined #lightning-dev
01:06 -!- riclas [~riclas@26.27.71.148.rev.vodafone.pt] has quit [Ping timeout: 260 seconds]
01:19 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
01:19 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #lightning-dev
01:42 -!- UncleBen [~UncleBens@user/UncleBen] has joined #lightning-dev
02:24 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #lightning-dev
02:26 -!- UncleBen [~UncleBens@user/UncleBen] has quit [Quit: ____________________________________________________________________________________________________________________________________________]
02:30 -!- UncleBen [~UncleBens@user/UncleBen] has joined #lightning-dev
02:38 -!- UncleBen [~UncleBens@user/UncleBen] has quit [Quit: ____________________________________________________________________________________________________________________________________________]
02:45 -!- riclas [~riclas@26.27.71.148.rev.vodafone.pt] has joined #lightning-dev
03:25 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
03:26 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #lightning-dev
03:53 -!- UncleBen [~UncleBens@user/UncleBen] has joined #lightning-dev
04:17 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...]
04:45 -!- UncleBen [~UncleBens@user/UncleBen] has quit [Quit: celebrate free speech \o/]
04:46 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #lightning-dev
04:52 -!- UncleBen [~UncleBens@user/UncleBen] has joined #lightning-dev
05:44 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #lightning-dev
05:45 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
06:00 -!- MrFrancis [~MrFrancis@bl15-115-2.dsl.telepac.pt] has joined #lightning-dev
06:03 < realtbast[m]> It's not about pinning (at least not why it's on my todo-list) but rather getting your funds back more quickly: you always have an incentive to see the remote commitment confirmed instead of your local commitment so that there's no CSV delay for your outputs
06:20 -!- UncleBen [~UncleBens@user/UncleBen] has quit [Quit: UncleBen]
06:38 < BlueMatt[m]> Why bother looking at the mempool, then? You know the txid, just try to broadcast a spend
06:41 < realtbast[m]> Agreed, I didn't necessarily wanted to look at the mempool when doing that, we can do a blind attempt at spending our anchor in the remote commitment
06:51 -!- MrFrancis [~MrFrancis@bl15-115-2.dsl.telepac.pt] has quit [Ping timeout: 252 seconds]
07:04 -!- jonatack2 [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
07:44 -!- _flood [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Read error: Connection reset by peer]
07:51 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
07:52 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #lightning-dev
07:57 -!- MrFrancis [~MrFrancis@2001:8a0:fa4c:901:7889:c073:b49b:b2a3] has joined #lightning-dev
08:38 -!- jonatack2 [~jonatack@user/jonatack] has joined #lightning-dev
08:51 -!- jonatack2 [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
08:51 -!- jonatack3 [~jonatack@user/jonatack] has joined #lightning-dev
09:30 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has quit [Remote host closed the connection]
09:31 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has joined #lightning-dev
09:33 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
09:34 -!- MrFrancis [~MrFrancis@2001:8a0:fa4c:901:7889:c073:b49b:b2a3] has quit [Ping timeout: 256 seconds]
10:02 -!- jonatack [~jonatack@user/jonatack] has joined #lightning-dev
10:03 -!- jonatack3 [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds]
10:23 -!- riclas [~riclas@26.27.71.148.rev.vodafone.pt] has quit [Ping timeout: 260 seconds]
10:45 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 255 seconds]
10:47 -!- jon_atack [~jonatack@user/jonatack] has joined #lightning-dev
10:49 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
10:51 < realtbast[m]> Hey all, if people are on vacation we'll probably skip the meeting tonight. I'm interested in implementers' opinion on this comment and whether we should fix it: https://github.com/lightning/bolts/pull/851#discussion_r1044648808 
10:51 < realtbast[m]> The TL;DR is that since dual funding provides an opportunity to create a new set of open/accept messages, we should probably fix things that weren't done properly in the first version of open/accept messages
10:51 < realtbast[m]> One such thing is the per-commitment points
10:52 < realtbast[m]> In channel open v1, open and accept include the first per-commitment point, but since we sign an initial commitment before signing the funding transaction, we actually care about the second per-commitment point for future commitments, and it is only transmitted with channel_ready
10:53 < realtbast[m]> In our data model in eclair, that means we have a weird case for the first commitment where we cannot correctly fill data about the next commitment, whereas it can always be filled in later commitments, I'm wondering if other implementations (especially strongly-typed ones such as rust-lightning) have the same issue?
10:54 < realtbast[m]> It's somewhat minor, but it's weird, so if we can get rid of it, it's probably better?
10:56 < realtbast[m]> Here is where this weirdness materializes in eclair if anyone's interested: https://github.com/ACINQ/eclair/blob/b5a2d3a6654c64bf4def3db4d409792145c73e07/eclair-core/src/main/scala/fr/acinq/eclair/channel/fsm/ChannelOpenSingleFunded.scala#L285
10:56 -!- endothermicdev [~endotherm@2600:1700:8481:8900:d25b:da7b:f18f:e400] has joined #lightning-dev
10:56 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
11:58 -!- MrFrancis [~MrFrancis@2001:8a0:fa4c:901:7889:c073:b49b:b2a3] has joined #lightning-dev
12:15 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has quit [Ping timeout: 255 seconds]
12:15 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has joined #lightning-dev
12:52 -!- MrFrancis [~MrFrancis@2001:8a0:fa4c:901:7889:c073:b49b:b2a3] has quit [Remote host closed the connection]
12:52 -!- MrFrancis [~MrFrancis@2001:8a0:fa4c:901:7889:c073:b49b:b2a3] has joined #lightning-dev
14:01 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has quit [Remote host closed the connection]
14:01 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has joined #lightning-dev
14:44 -!- treyd [~treyd@ip68-9-43-78.cl.ri.cox.net] has joined #lightning-dev
15:03 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 255 seconds]
15:06 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
15:46 -!- MrFrancis [~MrFrancis@2001:8a0:fa4c:901:7889:c073:b49b:b2a3] has quit [Ping timeout: 252 seconds]
16:43 -!- treyd [~treyd@ip68-9-43-78.cl.ri.cox.net] has quit [Quit: Leaving]
17:16 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 255 seconds]
17:27 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
18:36 -!- MrFrancis [~MrFrancis@bl15-115-2.dsl.telepac.pt] has joined #lightning-dev
18:37 -!- FrancisMr [~MrFrancis@bl15-115-2.dsl.telepac.pt] has joined #lightning-dev
18:38 -!- FranMr [~MrFrancis@2001:8a0:fa4c:901:70cd:7ac8:9a76:cb5f] has joined #lightning-dev
18:41 -!- MrFrancis [~MrFrancis@bl15-115-2.dsl.telepac.pt] has quit [Ping timeout: 272 seconds]
18:42 -!- FrancisMr [~MrFrancis@bl15-115-2.dsl.telepac.pt] has quit [Ping timeout: 272 seconds]
19:00 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has quit [Remote host closed the connection]
19:00 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has joined #lightning-dev
19:13 -!- FranMr [~MrFrancis@2001:8a0:fa4c:901:70cd:7ac8:9a76:cb5f] has quit [Ping timeout: 260 seconds]
22:35 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has quit [Ping timeout: 255 seconds]
22:35 -!- bitipy [~quassel@gateway/tor-sasl/bitipy] has joined #lightning-dev
23:21 -!- FranMr [~MrFrancis@2001:8a0:fa4c:901:70cd:7ac8:9a76:cb5f] has joined #lightning-dev
--- Log closed Tue Dec 20 00:00:50 2022