--- Log opened Fri Jan 25 00:00:30 2019
00:13 -!- nirved [~nirved@2a02:8071:b58a:3c00:3ca6:9fb9:2e23:4e12] has quit [Ping timeout: 268 seconds]
00:21 -!- nirved [~nirved@HSI-KBW-095-208-248-049.hsi5.kabel-badenwuerttemberg.de] has joined #lightning-dev
00:35 -!- enemabandit [~enemaband@185.227.37.188.rev.vodafone.pt] has joined #lightning-dev
00:54 -!- JackH [~laptop@host86-175-127-233.range86-175.btcentralplus.com] has quit [Ping timeout: 240 seconds]
01:32 -!- jungly [~quassel@host97-200-static.8-79-b.business.telecomitalia.it] has joined #lightning-dev
01:35 -!- JackH [~laptop@62.232.170.181] has joined #lightning-dev
02:03 -!- kexkey [~kexkey@199.229.249.116] has quit [Read error: Connection reset by peer]
03:15 -!- Ov1se [~Ov1se@138.68.75.100] has joined #lightning-dev
03:15 -!- Ov1se [~Ov1se@138.68.75.100] has quit [Client Quit]
04:33 -!- drolmer_ is now known as drolmer
04:34 -!- riclas [riclas@148.63.37.111] has joined #lightning-dev
05:00 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 244 seconds]
05:18 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds]
05:44 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
06:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
07:42 -!- sstone [~sstone@ec2-35-180-216-238.eu-west-3.compute.amazonaws.com] has joined #lightning-dev
07:48 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #lightning-dev
08:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
08:30 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
08:34 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 240 seconds]
08:35 -!- lukedashjr is now known as luke-jr
08:41 -!- jungly [~quassel@host97-200-static.8-79-b.business.telecomitalia.it] has quit [Remote host closed the connection]
09:12 -!- JackH [~laptop@62.232.170.181] has quit [Quit: Leaving]
09:13 -!- sstone [~sstone@ec2-35-180-216-238.eu-west-3.compute.amazonaws.com] has quit [Quit: Leaving]
10:07 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #lightning-dev
10:09 < cdecker> roasbeef: the issue I think is that if lnd is disconnected while it reaches the announcement threshold it'll send both in an undetermined order since local funding locked and announcement sig exchange would coincide in this case
10:10 < cdecker> i.e., this happens to us when we are offline while the channel confirms and we later reconnect with 6+ confirmations
10:25 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8daa:4eaf:6ad5:2731] has joined #lightning-dev
10:39 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8daa:4eaf:6ad5:2731] has quit [Remote host closed the connection]
10:47 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
10:48 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev
10:57 -!- enemabandit [~enemaband@185.227.37.188.rev.vodafone.pt] has quit [Ping timeout: 272 seconds]
12:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds]
12:01 -!- grubles [~grubles@unaffiliated/grubles] has joined #lightning-dev
12:04 < lndbot> <johanth> sounds right, it'll be a race between the fundingmanager and gossiper at reconnection, since they'll both attempt to re-send
12:04 < lndbot> <johanth> cc @wilmer.paulino 
12:05 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Remote host closed the connection]
12:14 <+roasbeef> yeah they aren't synchronized at all, and imo they shuldn't be 
12:14 <+roasbeef> one is network level, the other is link level 
12:19 -!- amp__ [~amp@24.136.5.183] has quit [Remote host closed the connection]
12:27 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #lightning-dev
12:45 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt]
13:18 -!- enemabandit [~enemaband@16.77.54.77.rev.vodafone.pt] has joined #lightning-dev
13:42 -!- nirved [~nirved@HSI-KBW-095-208-248-049.hsi5.kabel-badenwuerttemberg.de] has quit [Killed (sinisalo.freenode.net (Nickname regained by services))]
13:42 -!- nirved [~nirved@2a02:8071:b58a:3c00:daf:cc6c:bba6:f6cf] has joined #lightning-dev
13:45 < niftynei> fwiw the bigger problem with respect to channel ordering isn't funding_locked / announcement sigs, it's channel_reestablish / announcement sigs
13:45 < niftynei> s/channel ordering/message ordering
13:47 < niftynei> the problem is that channel_reestablish isn't the first message across the wire on reconnect
13:47 < niftynei> it seems reasonable to expect that level of ordering imo
13:49 < niftynei> in the linklevel/network level parlance that'd be ascertaining that you can re-establish the link before sending network msgs. i think lol
14:42 -!- thomasan_ [~thomasand@2605:a601:b021:f00:4ce2:9c48:a420:7c9a] has joined #lightning-dev
14:46 -!- thomasan_ [~thomasand@2605:a601:b021:f00:4ce2:9c48:a420:7c9a] has quit [Remote host closed the connection]
14:52 <+roasbeef> niftynei: yeh you can, both can happen concurrently, there's no hard synchronization requirement 
15:02 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
15:21 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev
15:43 -!- enemabandit [~enemaband@16.77.54.77.rev.vodafone.pt] has quit [Ping timeout: 240 seconds]
15:57 < niftynei> other than the fact that c-lightning currently requires it, this is true :P
15:58 < niftynei> the thing i don't understand about your argument is that it seems useless to announce a channel that you're going to fail because they're out of sync
15:58 < niftynei> like, what's the rationale for sending a channel announcement before you know that the channel is still good?
15:59 < niftynei> well, annoucement sigs, but still
16:03 <+roasbeef> good point, but just the case that atm the two systems don't communicate w/ each other, and just try to do their job independently 
16:03 <+roasbeef> also the case that this doesn't always happen 100% due to asynchrony 
16:09 < niftynei> i might be missing something but it feels like you're arguing behavior based on your current implementation (re 'the two systems don't communicate)
16:11 < niftynei> i'm making assumptions here, but at some point when the channel fails you're going to clean up the announcement machinery for it. so it's not like they're entirely separate
16:17 <+roasbeef> yeh but the source there is the chain 
16:19 <+roasbeef> i'm not arguing the behavior, telling you how it works atm
16:24 < niftynei> oic.. . this explains a lot "but the source there is the chain" 
16:24 < niftynei> kkk
16:26 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.3]
16:27 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #lightning-dev
16:44 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]
16:44 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #lightning-dev
16:50 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]
16:56 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #lightning-dev
17:00 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Client Quit]
17:35 -!- riclas [riclas@148.63.37.111] has quit [Ping timeout: 250 seconds]
18:39 -!- unixb0y [~unixb0y@p5B029B5C.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
18:42 -!- unixb0y [~unixb0y@p2E555460.dip0.t-ipconnect.de] has joined #lightning-dev
18:58 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #lightning-dev
19:14 -!- grubles [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection]
19:22 -!- kexkey [~kexkey@199.229.249.116] has joined #lightning-dev
19:35 -!- grubles [~grubles@unaffiliated/grubles] has joined #lightning-dev
19:50 -!- deusexbeer [~deusexbee@080-250-075-168-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!]
20:07 -!- grubles [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection]
20:45 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]
20:48 -!- grubles [~grubles@unaffiliated/grubles] has joined #lightning-dev
21:05 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev
21:07 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds]
21:50 -!- Amperture [~amp@24.136.5.183] has joined #lightning-dev
21:51 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
22:07 -!- diackca [~abdoulaye@41.190.2.214] has joined #lightning-dev
22:14 -!- diackca [~abdoulaye@41.190.2.214] has quit [Remote host closed the connection]
22:15 -!- diackca [~abdoulaye@41.190.2.214] has joined #lightning-dev
22:15 -!- diackca [~abdoulaye@41.190.2.214] has quit [Read error: Connection reset by peer]
--- Log closed Sat Jan 26 00:00:31 2019