--- Log opened Fri Mar 27 00:00:35 2020
00:40 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
00:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
00:43 -!- vasild_ is now known as vasild
01:59 -!- sr_gi [~sr_gi@132.red-83-34-186.dynamicip.rima-tde.net] has joined #c-lightning
02:09 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
02:14 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
02:16 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
02:18 < vasild> travis seems to be stuck at https://github.com/ElementsProject/lightning/pull/3390 for a few days, not starting the tests
02:58 < m-schmoock> I also had this the other day
02:58 < m-schmoock> Just change the commit message by a blankspace and forcepush
02:59 < m-schmoock> Hum, Isnt that the build? https://travis-ci.org/github/ElementsProject/lightning/builds/666490253?utm_medium=notification&utm_source=github_status
03:00 < m-schmoock> hm no
03:00 < m-schmoock> this is 645a6af 
03:00 < m-schmoock> and github doesnt know it
03:03 < m-schmoock> sorry, I cant help, just retry with a modified commit msg. travis doesnt seem to know 7b99bd8
03:04 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
03:06 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
03:07 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
03:09 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
03:24 < m-schmoock> cdecker: are we done here or should I minor optimizations, i.e. merging the duplicated blocks so code gets compacter?:   https://github.com/ElementsProject/lightning/pull/3572#issuecomment-602239069
03:37 < vasild> m-schmoock: done, thanks! :)
04:25 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
04:26 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
04:28 <@cdecker> m-schmoock: sorry for the delay, I'll review and merge today :+1:
05:27 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
05:27 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
05:47 < m-schmoock> thx :D  if you like you can merge the two blocks in a cleanup commit, but its very readable as is at well
06:04 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack]
06:10 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
06:30 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
06:46 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
07:16 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
07:17 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
08:02 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
08:21 < m-schmoock> cdecker: I have updated the description of decommission   https://github.com/ElementsProject/lightning/issues/3550   if you like to have a look
08:22 < m-schmoock> since the base stuff is clear I will start implementing, we can change details on the run
08:28 <@cdecker> Good points, but I still think that both fast and eco decommission are really the same, except for the calls to `withdraw`.
08:29 <@cdecker> You point out that we could drain, or generally reduce our stake in channels by consolidating onto a single channel, before closing, and I think that makes sense in both scenarios since it reduces our on-chain footprint considerably
08:30 <@cdecker> eco: Fewer outputs in the commitment -> fewer/smaller withdraw transactions -> fewer fees
08:30 <@cdecker> fast: Fewer outputs -> smaller withdraw transactions -> more ban for the buck :-)
08:49 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
08:56 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
09:12 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
10:03 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
10:09 < m-schmoock> cdecker: even if we drain a channel before closing, since we (currenlty) maintain the reserves, there will always be an output until we talk about eltoo, right?
10:19 <@cdecker> Uff, you're right...
10:19 < m-schmoock> so okay, until then its just a measure to get liquidity reduced before closing. so maybe we dont implement this yet
10:28 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
10:46 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
12:40 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
12:40 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
12:43 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
12:43 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
12:44 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
12:44 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
12:44 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined #c-lightning
12:45 -!- m-schmoock [~will@schmoock.net] has quit [Ping timeout: 265 seconds]
12:45 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
12:45 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
12:45 -!- jtimon [~quassel@206.160.134.37.dynamic.jazztel.es] has quit [Quit: No Ping reply in 180 seconds.]
12:45 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
12:45 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
12:45 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
12:45 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
12:46 -!- jtimon [~quassel@206.160.134.37.dynamic.jazztel.es] has joined #c-lightning
12:47 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
12:50 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
12:54 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
13:15 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Read error: Connection reset by peer]
13:15 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has quit [Read error: Connection reset by peer]
13:15 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
13:15 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
14:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
14:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
15:16 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
15:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
15:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
15:46 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has joined #c-lightning
15:50 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds]
16:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
17:08 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
17:13 -!- sr_gi [~sr_gi@132.red-83-34-186.dynamicip.rima-tde.net] has quit [Quit: Leaving...]
17:30 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
18:17 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 272 seconds]
18:57 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
18:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
18:59 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
19:36 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
19:57 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
20:13 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
20:13 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
20:21 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
21:57 -!- jtimon [~quassel@206.160.134.37.dynamic.jazztel.es] has quit [Ping timeout: 256 seconds]
22:43 -!- ariard [~ariard@167.99.46.220] has joined #c-lightning
22:48 < ariard> hey, a question on cl gossip logic :)
22:48 < ariard> , as far as I understand gossip_store_next is the main loader for flushing gossips but it's only triggered in openingd/channeld/closingd...?
22:49 < ariard> so if I've a node connected signaling initial_routing_sync but no channel, how gossips sync will happen, where should I look?
23:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
23:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
23:43 < zmnscpxj_> ariard: connect to any node I think, that should trigger it downloading the routemap?
--- Log closed Sat Mar 28 00:00:35 2020