--- Log opened Mon Apr 13 00:00:50 2020
00:03 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 256 seconds]
00:03 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
00:04 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
00:08 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
00:08 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
00:16 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Ping timeout: 260 seconds]
00:17 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
00:21 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
00:21 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
00:26 -!- jonatack_ [~jon@37.172.122.174] has joined #lightning-dev
00:29 -!- jonatack [~jon@37.170.20.209] has quit [Ping timeout: 265 seconds]
00:44 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
00:44 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
00:44 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
00:46 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
00:48 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
00:49 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
00:53 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
00:54 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
00:58 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
00:58 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
01:00 -!- sr_gi [~sr_gi@39.red-83-46-130.dynamicip.rima-tde.net] has joined #lightning-dev
01:00 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
01:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
01:01 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
01:04 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
01:04 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
01:08 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
01:08 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
01:11 -!- marcoagner [~user@2001:8a0:6a5f:a900:6d3e:1158:b50:97b6] has joined #lightning-dev
01:14 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
01:14 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
01:20 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
01:21 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
01:28 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 260 seconds]
01:31 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
01:31 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
01:36 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Ping timeout: 264 seconds]
01:39 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
01:43 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
01:44 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
01:50 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
01:51 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
01:56 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
02:02 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
02:03 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
02:12 -!- mauz555 [~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829] has joined #lightning-dev
02:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
02:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
02:16 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
02:16 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
02:17 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds]
02:18 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
02:21 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
02:21 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
02:31 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
02:31 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
02:38 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
02:38 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
02:52 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
02:53 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:00 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Ping timeout: 258 seconds]
03:02 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:05 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:05 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:07 -!- kloinka [~quassel@223.177.233.220.static.exetel.com.au] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
03:09 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:10 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:12 -!- kloinka [~quassel@223.177.233.220.static.exetel.com.au] has joined #lightning-dev
03:13 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:13 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:16 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:16 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:21 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:22 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:25 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #lightning-dev []
03:26 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:26 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:31 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:31 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:35 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:36 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:39 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 256 seconds]
03:40 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:41 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:45 -!- riclas [riclas@77.7.37.188.rev.vodafone.pt] has joined #lightning-dev
03:46 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:46 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:48 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:48 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:54 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
03:55 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
03:59 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev
04:04 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:04 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
04:09 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:09 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
04:12 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:13 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
04:19 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:20 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
04:28 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:28 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
04:28 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
04:36 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:36 -!- jonatack_ [~jon@37.172.122.174] has quit [Ping timeout: 256 seconds]
04:36 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
04:37 -!- jonatack_ [~jon@134.19.179.163] has joined #lightning-dev
04:41 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:41 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
04:47 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:47 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
04:51 -!- Kostenko [~Kostenko@2001:8a0:7297:3200:a9b8:62b6:5438:291d] has quit [Read error: Connection timed out]
04:52 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:52 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
04:54 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:55 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
04:58 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
04:58 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:01 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:01 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:03 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:03 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:09 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:09 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:13 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:14 -!- jonatack_ [~jon@134.19.179.163] has quit [Quit: jonatack_]
05:14 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:14 -!- jonatack [~jon@134.19.179.163] has joined #lightning-dev
05:18 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:18 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:22 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:22 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:26 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:26 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:27 -!- mauz555 [~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829] has quit [Read error: Connection reset by peer]
05:30 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:30 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:34 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:34 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:38 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:38 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:44 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:44 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:47 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:48 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:52 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:55 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
05:58 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
05:58 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:02 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:03 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:06 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:07 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:09 -!- mauz555 [~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829] has joined #lightning-dev
06:15 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:15 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:18 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:18 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:20 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:20 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:24 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:24 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:29 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:29 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:32 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:33 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:39 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:39 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:45 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:45 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:53 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:53 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:54 -!- Kostenko [~Kostenko@2001:8a0:7297:3200:a9b8:62b6:5438:291d] has joined #lightning-dev
06:56 -!- __gotcha1 [~Thunderbi@plone/gotcha] has joined #lightning-dev
06:58 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
06:59 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
06:59 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 256 seconds]
06:59 -!- __gotcha1 is now known as __gotcha
07:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit []
07:03 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:04 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:07 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:07 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:11 -!- per [~per@gateway/tor-sasl/wsm] has joined #lightning-dev
07:11 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:11 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:12 -!- kloinka [~quassel@223.177.233.220.static.exetel.com.au] has quit [Read error: Connection reset by peer]
07:13 -!- kloinka [~quassel@223.177.233.220.static.exetel.com.au] has joined #lightning-dev
07:15 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:15 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:19 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:19 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:23 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:23 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:25 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
07:28 -!- mol [~molly@unaffiliated/molly] has joined #lightning-dev
07:29 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Remote host closed the connection]
07:30 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:32 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:33 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:39 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:39 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:47 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:47 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:50 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:50 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:55 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
07:56 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
07:58 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Read error: Connection reset by peer]
07:59 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:00 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:04 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:04 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:05 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
08:09 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:09 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:11 -!- gleb [~gleb@cpe-67-244-100-77.nyc.res.rr.com] has quit [Quit: Ping timeout (120 seconds)]
08:11 -!- gleb [~gleb@cpe-67-244-100-77.nyc.res.rr.com] has joined #lightning-dev
08:12 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:12 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:16 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:16 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:19 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:20 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:23 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:24 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:28 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:29 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:30 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 256 seconds]
08:32 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:33 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:33 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
08:38 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:38 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:40 -!- Kostenko [~Kostenko@2001:8a0:7297:3200:a9b8:62b6:5438:291d] has quit [Remote host closed the connection]
08:41 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:41 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:44 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:44 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:48 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:48 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:51 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:51 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
08:55 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
08:56 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
09:00 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
09:01 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
09:05 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
09:06 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
09:09 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
09:09 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
09:15 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Ping timeout: 265 seconds]
09:16 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
09:26 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Ping timeout: 260 seconds]
09:29 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
09:32 -!- Kostenko [~Kostenko@2001:8a0:7297:3200:a9b8:62b6:5438:291d] has joined #lightning-dev
09:35 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #lightning-dev
09:43 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 265 seconds]
09:49 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
09:49 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
10:01 < ThomasV> I see a very low number of nodes (280) that advertise option_data_loss_protect_opt in their node_announcement. anyreason for that?
10:02 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
10:02 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
10:09 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
10:09 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
10:14 -!- hkjn0 [~hkjn@163.172.184.153] has joined #lightning-dev
10:15 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
10:15 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
10:16 -!- hkjn0 [~hkjn@163.172.184.153] has quit [Client Quit]
10:16 -!- hkjn0 [~hkjn@163.172.184.153] has joined #lightning-dev
10:18 -!- hkjn0 [~hkjn@163.172.184.153] has quit [Client Quit]
10:21 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
10:21 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
10:27 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 246 seconds]
10:30 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
10:30 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
10:31 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
10:32 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
10:33 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #lightning-dev
10:38 < cdecker> That'd be really bad since the security of static channel backups hinges on that :-s
10:39 < ThomasV> cdecker: they seem to support it and advertise it in INIT, but not in nodde_announcement
10:44 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
10:44 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
10:45 < cdecker> Interesting, that breaks node selection from gossip then
10:47 < ThomasV> well, that's what I want to know. it could also just be my code that is broken :)
10:49 < wpaulino> iirc they were only added to init at the time, but were later added to node announcements as part of the last lnd release
10:50 < wpaulino> we've had issues with node announcements propagating as well, so that may be why the number seems low
10:50 < ThomasV> wpaulino: true, but I measured the same proportion about 3 months ago. I was expecting it to increase with nodes updating..
10:52 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
10:52 < ThomasV> do other implementations than lnd advertise it only in INIT?
10:54 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
10:54 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
10:57 -!- molly [~molly@unaffiliated/molly] has joined #lightning-dev
10:59 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
11:00 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
11:00 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
11:10 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
11:10 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
11:17 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
11:18 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
11:20 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
11:20 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev
11:21 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 246 seconds]
11:24 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
11:24 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
11:30 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
11:30 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
11:39 < cdecker> c-lightning will keep init and node_announcement in sync, unless there is a good reason not to
11:42 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
11:43 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
11:50 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
11:50 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
11:51 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #lightning-dev
11:53 -!- molz_ [~molly@unaffiliated/molly] has joined #lightning-dev
11:55 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Ping timeout: 265 seconds]
11:55 -!- jonatack [~jon@134.19.179.163] has quit [Ping timeout: 256 seconds]
11:55 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
11:57 -!- jonatack [~jon@37.172.122.174] has joined #lightning-dev
11:58 -!- molz_ [~molly@unaffiliated/molly] has quit [Ping timeout: 258 seconds]
12:00 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
12:05 -!- mol [~molly@unaffiliated/molly] has joined #lightning-dev
12:10 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
12:11 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
12:20 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
12:21 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
12:24 -!- ironhelix [~d@193.56.117.99] has quit [Ping timeout: 256 seconds]
12:26 -!- jonatack_ [~jon@37.170.24.84] has joined #lightning-dev
12:27 -!- t-bast [~t-bast@2a01:e34:efde:97d0:de9:76ec:fb74:9c75] has joined #lightning-dev
12:29 -!- jonatack__ [~jon@37.165.18.125] has joined #lightning-dev
12:29 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
12:29 -!- jonatack [~jon@37.172.122.174] has quit [Ping timeout: 258 seconds]
12:29 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
12:32 -!- jonatack_ [~jon@37.170.24.84] has quit [Ping timeout: 260 seconds]
12:36 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
12:36 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
12:39 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
12:39 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
12:42 -!- jonatack__ [~jon@37.165.18.125] has quit [Read error: Connection reset by peer]
12:43 -!- jonatack__ [~jon@37.165.18.125] has joined #lightning-dev
12:43 -!- jonatack__ [~jon@37.165.18.125] has quit [Client Quit]
12:44 -!- jonatack [~jon@213.152.161.101] has joined #lightning-dev
12:44 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
12:44 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
12:44 -!- jonatack [~jon@213.152.161.101] has quit [Read error: Connection reset by peer]
12:45 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
12:46 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
12:50 -!- jonatack [~jon@37.165.18.125] has joined #lightning-dev
12:51 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
12:51 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
12:52 < jkczyz> Is the time for spec meeting posted anywhere online?
12:56 < t-bast> Good question, I think we should include it in the tracking issue.
12:56 < t-bast> I'll update it right now (may be too late though for this occurrence :/)
12:57 < jkczyz> Thanks! think daylight savings has mixed it up for me a couple times now
12:57 < ariard> it's in the CONTRIBUTING.md IIRC
12:57 < t-bast> It's very simple, the meeting happens every 2016 blocks :)
12:57 < t-bast> Bitcoin knows no daylight savings
12:58 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
12:58 < ariard> do you know about time-warp attack?
12:58 < t-bast> damn they could mess up our meeting with those, you're right
12:58 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
12:58 < t-bast> someone should invent a blockchain for tracking time 
12:59 < ariard> yeah time is so much overated in bitcoin
12:59 < cdecker> Well, logical timestamps ftw :-)
13:00 < niftynei> wasssup
13:00 < t-bast> hey cdecker and niftynei!
13:00 < cdecker> Morning t-bast :-)
13:00 -!- sstone [~sstone@185.186.24.109.rev.sfr.net] has joined #lightning-dev
13:01 < t-bast> c-lightning is probably the less impacted team by covid, how is it going for you?
13:01 < cdecker> Quite alright, though circumstances do slow us down as well
13:03 < niftynei> cabin fever is real :)
13:03 < cdecker> How about you? Hope everyone is doing well ^^
13:03 < sstone> hi everyone!
13:04 < t-bast> We're trying out the remote work experience, it's been working quite well for now, but I do agree in cabin fever!
13:04 < cdecker> Indeed, though my neighbors seem to suffer more cabin fever, they started snapping at kids everywhere for playing to loudly xD
13:04 < cdecker> Kind of miss my daily walking routine...
13:04 < t-bast> It must be hell to have young children in this situation, that probably explains rusty's empty commits xD
13:05 < niftynei> ehehe
13:05 < sstone> most people I see outside are either waling their dog or walking their kids :)
13:05 < sstone> walking
13:05 < cdecker> All on a leash I guess :-)
13:05 < t-bast> can you buy dogs on amazon (or kids)? I need one of those then 
13:06 < cdecker> My sister in law is actually walking her parents xD
13:06 < ariard> if someone wants to exchange against the full nyc ambulance every-15-min show lmk
13:06 < cdecker> Anyway, doesn't seem like too many people showed up on this fine (holi-)day :-)
13:06 < niftynei> i lent my dogs to my dad for a few weeks; it was not a smart decision on my part (but my dad really had a good time)
13:07 < t-bast> ariard: wow it's that tough in NYC?
13:07 < ariard> t-bast: we don't have a hard confinement, which means people are free to walk out, which means contagion rate is still pretty high
13:08 < t-bast> damn...
13:08 < t-bast> do we have people from lightning labs in the audience to start the meeting?
13:09 <+roasbeef> oy
13:10 < t-bast> hey roasbeef! how is it going?
13:12 <+roasbeef> not bad, haven't really gone outside for the past few weeks, but hey the window in my room gives me enough sunlight ;) 
13:12 < niftynei> is there an agenda for today's meeting?
13:12 < t-bast> yep let me post the link
13:12 < niftynei> ty!
13:12 <+roasbeef> yeh there's a bit, may be a ligther one 
13:12 < t-bast> https://github.com/lightningnetwork/lightning-rfc/issues/766
13:12 < t-bast> #startmeeting
13:12 < lightningbot> Meeting started Mon Apr 13 20:12:45 2020 UTC.  The chair is t-bast. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:12 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:13 < t-bast> Luckily we've been able to merge quite a few PRs recently, so I think this is a good opportunity to discuss long term stuff
13:13 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Ping timeout: 258 seconds]
13:13 < t-bast> What do you think of only doing long-term stuff tonight?
13:13 < t-bast> Unless you have PRs you want to have people look at
13:14 <+roasbeef> there's #764, but the text portion there is pretty small, can prob be mostly hashed out on the PR 
13:14 <+roasbeef> main thing there is finding some wording that isn't langauge specific 
13:14 <+roasbeef> we've had this issue in the past on the lnd side, and actually you need to specify a "nil vector" rather than "an empty one" 
13:15 < t-bast> #topic https://github.com/lightningnetwork/lightning-rfc/pull/764/
13:15 < t-bast> #link https://github.com/lightningnetwork/lightning-rfc/pull/764/
13:15 < t-bast> Agreed, it's a matter of wording, how is this worded in BIPs (if there are some where this case is mentioned)?
13:16 < darosior> It's worded as empty vector
13:16 < t-bast> roasbeef: you're a go developer, aren't you? nil vs empty? :)
13:16 < t-bast> ok so this is what ariard suggests in this PR
13:16 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
13:16 < t-bast> it's true that `0` is misleading
13:16 < ariard> t-bast: there is not BIP for this, it's a standard policy
13:17 < darosior> https://github.com/jl2012/bips/blob/minimalif/bip-minimalif.mediawiki
13:17 < cdecker> op_push(0)?
13:17 <+roasbeef> well many of the BIPs are also very language specific (C++)
13:17 < ariard> right, empty vector in PR wording
13:17 <+roasbeef> this is in BIP 141 
13:19 < ariard> roasbeef: right it's in BIP 141 but as standard policies?
13:19 < ariard> I mean rn it's not exported by bitcoinconsensus like other consensus flags
13:19 <+roasbeef> dunno what the lib exports, but yeh it's relay policy 
13:19 <+roasbeef> just meant that it's mentioned there at least 
13:20 < ariard> yeah it's not switched on in GetBlockScriptFlags
13:20 < ariard> okay so what's wording have people favor ? will update in consequence
13:21 < sstone> why not call it an empty witness field ?
13:21  * cdecker abstains
13:21 < sstone> it matches the BIP and is very specific
13:22 < t-bast> sstone: like `<empty>` or `<empty_witness>`?
13:22 <+roasbeef> sstone: "element" is used more commonly in my experience, but idk if saying empty witness element is all more that specific depending on the context...
13:22 < sstone> element is fine too
13:22 < niftynei> im not sure i grok what exactly 'empty vector' is in this context.. len-zero witness?
13:22 < t-bast> `<local_delayedsig> <empty>`?
13:22 < darosior> niftynei: bytes(0) in Python
13:23 < ariard> niftynei: OP_0 : an empty array of bytes is pushed onto the stack
13:23 < cdecker> b'\x00' is interpreted as OP_0 which pushes a zero-length vector / bytearray on the stack, but it's also used to represent false
13:23 <+roasbeef> the lowest level description may be the best here 
13:24 < niftynei> ok so len-zero data stack element
13:24 < ariard> witness may be quite confusing as per-BIP141 it has a definition
13:24 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 240 seconds]
13:24 < ariard> <empty_bytearray> ?
13:25 < niftynei> which would just be the len of the empty stack, which is OP_ZERO?
13:25 < niftynei> s/stack/data-element//
13:25 < niftynei> mebbe it's me but i find 'len-zero' a lot more descriptive than 'empty'
13:26 < sstone> why not keep the <> notation and explain at the beginning that it represent an empty witness element/field ? 
13:26 <+roasbeef> sstone: not a bad idea, then there's more room to elaborate 
13:26 < ariard> <zero-len vector> and a footnode linking back to jl2012 PR and mail?
13:27 < t-bast> agree, `<>` is concise and as long as there's a place where it's explained it's all good
13:27 < niftynei> wait why can't we just say OP_ZERO?
13:28 < ariard> sstone: where do you see to explain symbol notation ? beginning of BOLT3?
13:28 < niftynei> seems like that's the most explicit correct way to explain what's required by MINIMALIF? 
13:29 < niftynei> maybe we can take this to the PR?
13:29 < sstone> we already explain somewhere that the 'script' element is omitted for brevity, it could be added there
13:29 < sstone> (when we spend p2wsh outputs)
13:29 < ariard> okay in Use of Segwit I see, sgtm
13:30 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Ping timeout: 265 seconds]
13:30 < ariard> Let's settle on <> in witness dscription and explaining notation in Use of Segwit + footnote to explaining MINIMALIF
13:30 < ariard> and keep discussion for PR
13:30 < t-bast> ariard: sgtm
13:32 < t-bast> #action update to <> in witness dscription and explaining notation in Use of Segwit + footnote to explaining MINIMALIF, continue discussion on the PR
13:32 < t-bast> Any other PRs we want to look at or shall we jump to more long term things?
13:32 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
13:33 <+roasbeef> there's anchors, which I don't consider long-term (at least from teh PoV of lnd ;) ) 
13:34 <+roasbeef> impl wide on the lnd side not much has changed, ariard has a comment re someone trying to decrease the fee rate of a 2nd levle transaction, but that would require them to block broadcast of the base transaction which has a higher fee rate, so i don't think it's a major concern 
13:34 < t-bast> heh let's start with anchor outputs then
13:34 < t-bast> #topic Anchor Outputs
13:34 <+roasbeef> we'll be tagging lnd 0.10 this week, which as mentioned in my email from 2 weeks or so ago will include opt-in anchors as defined in the specification as is 
13:34 -!- ironhelix [~d@193.56.117.52] has joined #lightning-dev
13:35 <+roasbeef> i think on the spec end, we need to update some constants, but other than that it's pretty much in-line 
13:35 <+roasbeef> so my main question now is when/if the other implementations willl start to undertake the task of implementing it top to bottom? 
13:36 < t-bast> Is BlueMatt around? He mentioned rust-lightning would soon have time to look at it last time.
13:36 < ariard> roasbeef: not exactly a) you need to signal RBF on higher feerate original tx, b) it's going to be same issue than outputs without CSV_DELAY?
13:36 < niftynei> i'm super behind on writing up some thoughts i've had re:anchor outputs, but my general gist is that other than being 'more expensive in some cases, sort of' the only other real 2 quibbles i have with the existing proposal (not having implemented it) are 1) re-using to_remote and 2) the inclusion of uneconommical htlc outputs 
13:37 < ariard> t-bast: we're still working on this, implem is WIP
13:37 < niftynei> but 2)'s not really an issue until update_fee is removed so can be disregarded
13:37 <+roasbeef> niftynei: did you see my email to the list about that stuff? 
13:37 < t-bast> ariard: great, that should provide good feedback
13:38 < niftynei> by 'that stuff' are you referring to expense or to_remote?
13:38 <+roasbeef> ariard: iirc they already do signal opt-in, but you seem to assume that they'd race to get this into the mempool widelyu beofre ours? so they have a special hook up or are abel to censor our view of the network 
13:38 <+roasbeef> niftynei: yeh
13:38 < bitconner> fwiw, should clarify that lnd master implements the current proposal under feature bits 1336/1337
13:38 < niftynei> i did see your email and do not remember it addressing my specific concerns but i also haven't done the modeling i've been wanting to yet so haven't responded
13:39 <+roasbeef> niftynei: ok, wanna reply to it then to point out the gaps there in the arguments it presented? 
13:39 < niftynei> yes definitely!
13:40 <+roasbeef> the modeling is pretty trivial, the func is just: feeRate*weight + constant, the constant in this case is the extra anchor sats (660), the fee rate scaling dominates at anything above 1 sat/byte, which commitments would be above if theyr'e actually trying to get into the chain in time to resolve contracts 
13:40 < ariard> roasbeef: on RBF, they inherit RBF from commitment but if commitment gets confirmed in between 2nd-stage txn won't be RBF anymore? (need to verify mempool code on this)
13:41 < ariard> roasbeef: it's easy to win the race for an attacker, you just have to be connected to the base full-node of the LN node and don't respect tx-relay protocol
13:41 <+roasbeef> dunno what you mean by in-between, the transaction itself woudl still signal, and the  commitmetn needs to be confirmed before the second level can be spent, so it won't take in any unconfirmed inputs 
13:41 < ariard> tx-relay protcol have some timers at relay for privacy reasons
13:41 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Ping timeout: 264 seconds]
13:42 < niftynei> wrt to c-lightning implementation, which is probably more relevant it definitely won't be in the release we're cutting this week
13:42 < ariard> right now with anchor commitment transaction has to confirm before spending, but we don't signal RBF per-se on 2nd-stage txn ?
13:42 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
13:43 < niftynei> we should have a discussion shortly about the next release features, i'm pretty excited about the htlc tx batching that the anchors opens up and it'd be good to get that in for users
13:43 <+roasbeef> ariard: signalling is just a non final sequence, which is how they are or they inherit from the parent transaction 
13:44 < niftynei> it's looking like we'll probably ship some much better accounting facilities in this release which might make our users a bit more aware of chain fees in unilateral closures XD
13:44 <+roasbeef> ok cool, I also wouldn't under estimate the size of the implementation itself, since it touches so many aspects, for example in lnd we already have a CPFP bumping engine so we were able to plug that in pretty easily 
13:45 <+roasbeef> my main qualm is that it may be sometime near the end of summer before the other implementations have somethign operational for anchors itself, so do we want to block the spec progress on that all together? deployment-wide lnd is ambivalent as we're already at teh finish line and will have a way to update our commitments in-flight in stuff cahnges 
13:47 < ariard> roasbeef: you're right signaling is fine, but someone can still stuck in the mempool a low-feerate package, and you will have to pay more than its absolute fee to replace
13:48 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
13:48 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
13:48 < ariard> roasbeef: we already have dynamic bumping engine and refactored monitoring in backend, I think we can test inter-op by end of month
13:48 <+roasbeef> ariard: which may already be the  case given you should want to get that htlc in asap, so you should already be ready to bump the fee up as you go. either the other party needs to do this (only can after a commitment confirms), or someone needs to intercept before broadcast 
13:49 < t-bast> I think we've done quite a lot of comments without implementing it, so the state of the spec PR is what other implementations will be looking at while implementing. There will probably be new comments coming in as implementations catch up, but unless a comment really impacts the whole design we can probably make progress on the PR as it comes. WDYT?
13:49 <+roasbeef> ok, I mean this in an amicable manner, but do we "count" RL? given that it itself isn't really "finished" nor deployed anywhere in production 
13:49 < cdecker> Progress in what sense? Drop the "2 implementation" requirement?
13:50 <+roasbeef> cdecker: the operative question...!
13:50 < t-bast> I understood it as: keep the PR open while others implement
13:50 < cdecker> Ah ok
13:50 < t-bast> It needs at least a second implementation in production to be fully interop tested, right?
13:50 <+roasbeef> do CL or eclair commit to having this be a prio for their next releases? 
13:50 < cdecker> No
13:50  * roasbeef looks over at the other side of the IRC room....
13:51 < t-bast> For eclair we can't commit on that right now either
13:51 < ariard> roasbeef: we're spec compliant on 1.0 and we have tested against every other implem on testnet
13:51 <+roasbeef> ok, I expected as much 
13:51 < cdecker> I mean we won't commit to a major change to c-lightning that'd require shelving everything else for it
13:51 < t-bast> It's on our todo-list but I can't really commit on when exactly we'll be able to start implementing...
13:51 <+roasbeef> mhmm, totally reasonable 
13:52 <+roasbeef> on our end, it was a big thing we were working on over the past quarter or two, so understand that y'all would need to shift things around
13:52 < t-bast> agreed, but it's the same for trampoline on our side ;)
13:52 <+roasbeef> heheh yeh :p, prios prios prios 
13:52 < ariard> roasbeef: threat model is someone being connected to your full-node, not eclisping you, it's easy to intercept announced txn, add a low-feerate branch
13:53 < ariard> and do that iteratively at every bump fron the LN node
13:53 < cdecker> I'm just happy we're no longer discussing the realm byte reuse on the TLV proposal xD
13:53 <+roasbeef> kek
13:53 < t-bast> cdecker: xD
13:53 -!- mauz555 [~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829] has quit [Read error: Connection reset by peer]
13:53 < niftynei> hahaha
13:54 < t-bast> We have some work to do on our tx handling in eclair and phoenix as preliminary before anchor outputs, so it will take us some time. We're working towards it, but well...limited time!
13:54 <+roasbeef> fsho, yeh we also took some time to do some gardening along the way 
13:55 < t-bast> But rest assured that we're moving in that direction
13:55 < cdecker> As frustrating as it is, a slow moving spec is a good thing, allowing us to extensively inspect and analyse
13:55 < cdecker> (and ensure compatibility...)
13:55 < niftynei> should we move on to the next agenda item?
13:56 < t-bast> Yep, let's move on. How about we talk about Trampoline now?
13:56 < cdecker> +1 for trampolines (though I have to leave in a couple of mins)
13:56 < t-bast> It would love some feedback to move towards a solution everything likes
13:56 < t-bast> I can at least give a quick summary, things to look at, etc
13:57 < t-bast> 5 minutes top ;)
13:57 < cdecker> Yes, please
13:57  * BlueMatt notes that roasbeef et al explicitly maintained that anchor and other predecessors wasnt a priority for the last year or two
13:57 < niftynei> wait should we tag the topic change?
13:57 < BlueMatt> so I really dont think is fair to jump on it now
13:57 < t-bast> #topic Trampoline
13:57 < BlueMatt> anyway, I also think there are outstanding comments on the PR
13:57 < BlueMatt> (sorry, got dc'd)
13:57  * cdecker boing boing boing :-)
13:57 < niftynei> ty t-bast :)
13:57 < t-bast> #link https://github.com/lightningnetwork/lightning-rfc/pull/654
13:58 < t-bast> Allright as discussed last time, I spent some time splitting the trampoline PR
13:58 < t-bast> I made it into two documents; the first one in the "proposals" folder is what you should start with
13:58 < t-bast> It gives a higher level design overview, and lists many open questions and early proposals
13:58 <+roasbeef> BlueMatt: we've been working on it for over 6 months...and before then it was blocked on the carve out stuff 
13:59 < t-bast> Then trampoline-wip.md contains something that's more in "spec format" if you want to look at the details or prefer reading that.
13:59 < t-bast> I think reading the high level proposal shouldn't take too much time, if some of you can please spend a bit of time on that and leave comments that would be helpful to get the discussion going.
14:00 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
14:00 < t-bast> Even simply pointing out things that feel unclear will be helpful to make the review process smoother.
14:00 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
14:01 < cdecker> By the way, your diagrams look amazing if you pass them through ditaa :-)
14:01 < t-bast> I marked many earlier comments as resolved to avoid having too much to read for newcomers
14:01 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:01 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
14:01 < t-bast> I didn't know ditaa, this will make my life a lof better xD
14:02 < t-bast> I don't know about you but for onion things and packets, I feel it's much easier to understand something very visual like those diagrams
14:04 < cdecker> Definitely, I still have my desk full of scribbles for the RV proposal :-)
14:04 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
14:05 < t-bast> @BlueMatt note that trampoline works nicely with either blinded paths or rendezvous (I believe I mention it in the PR now)
14:07 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
14:08 < t-bast> On the implementation side, we've implemented a one-hop trampoline; this allowed us to validate the onion construction and play with MPP for Phoenix
14:09 < t-bast> The multi-hop trampoline has many sections where we have multiple options, so it will be interesting to start the discussion (gossip, filters, etc)
14:09 < BlueMatt> t-bast: nice! I'm happy on the progress, but, sadly I'm not 110% up on the latest state :(
14:10 <+roasbeef> motivation for trampoline in general is still lacking from my PoV based on where things are w/ the network even with shallow extrapolation 
14:10 < t-bast> BlueMatt: no worries, just to let you know when you have some time available to review
14:11 < niftynei> roasbeef, wdym by 'shallow extrapolation'
14:12 < t-bast> roasbeef: are you using a mobile wallet on something else than wifi?
14:12 < t-bast> roasbeef: and without using it every 6 hours?
14:12 < cdecker> I'd love to get a sample implementation done as a plugin, hopefully I can find some time to work on it and give feedback
14:13 < ThomasV> t-bast: do you have active mainnet or testnet trampoline nodes?
14:13 < t-bast> ThomasV: yes, on testnet it's the "endurance" node and on mainnet the "acinq" node
14:14 < ThomasV> nice. I'll try to play with it in the coming weeks
14:15 < t-bast> ThomasV: testnet is 03933884aaf1d6b108397e5efe5c86bcf2d8ca8d2f700eda99db9214fc2712b134@13.248.222.197:9735
14:16 < t-bast> ThomasV: it may need a specific feature bit in the invoice, don't hesitate to get in touch in private for help on making it work with your client code
14:17 < ThomasV> I will :)
14:17 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:17 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
14:17 < t-bast> roasbeef: honestly it's quite impossible to have a decent UX on mobile wallets without trampoline unless you're paying nodes you're directly connected to
14:18 <+roasbeef> niftynei: I mean like extrapolating some level of consistent growth in the number of open channels (imo we'll start to see it drop a bit as peopel start to manage their channels better), seems to early to jump to something like this which just concentrates paths even more (adding to the privacy short comings we already have) 
14:18 <+roasbeef> idk....there's a lot of design space that has yet to be explored 
14:18 <+roasbeef> re the 6hr thing, background syncing is possible, and the paths of an avg user are likely pretty concentrated, so you don't need to sync every random channel update 
14:19 < cdecker> Well, let's explore then, using the lack of research to shoot down a viable proposal seems weird... especially when it tackles an issue that one of us is already facing today
14:19 <+roasbeef> but ofc y'all are fee to explore this route given eclair is primarily used with a primary "gateway" node 
14:19 <+roasbeef> yeh ofc ofc
14:19 < t-bast> background syncing on iOS is pretty much unusable, and even on android if (like me and many others) you're frequently in battery saving explicitly to disable background jobs, you have 50k channel_updates to sync every time you launch the app...
14:20 < cdecker> Anyway need to get going, see you all around (hopefully in RL sometime as well) ^^
14:20 <+roasbeef> yeh don't sync 50k of them, maybe 10% of them even matter 
14:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
14:20 < t-bast> See you cdecker!
14:20 < t-bast> roasbeef: but then your payment fails very often
14:20 < t-bast> this is a horrible UX honestly, that just fuels opponents of lightning saying: look it never works, it has to retry 7 times before a payment goes through
14:20 <+roasbeef> depends...do you forget all past history after the payment attempt, are tehre additional hueristics which can be used? etc, etc 
14:21 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
14:21 <+roasbeef> yeh we can solve all that by just using 3 nodes as well (not saying this srsly, just this is the other extreme) 
14:21 < t-bast> I agree that there's design space to explore, but I think reviewing our proposal and pointing out what you don't like is a good first step, this way we can step-by-step do more research and converge towards something everything is comfortable with
14:21 <+roasbeef> also don't ignore the critical component of ppl actually manging their nodes properly, path finding can just route aruond those that set and forget 
14:22 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:22 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
14:22 <+roasbeef> i don't think we ultimatley  need something that everyone will adopt, we already have so mcuh hooks in the protocol as is for side routing protocols like these to emerge which is a great thing, I don't see everything using the base set of what we have years from now, as you may want to make certain tradeoffs to further optimize for certain use cases 
14:23 <+roasbeef> I also understand that eclair has a unique view point given it's a very popular mobile wallet and they deal directly w/ support tickets, etc 
14:24 < niftynei> i haven't had a lot of time to look at the existing trampoline proposal but i really like the 'proposal' design you've adopted for it t-bast
14:25 < niftynei> imo the fact that eclair is focusing pretty pointedly on the mobile usecase is great, since ya'll definitely are surfacing issues that probably wouldn't come up otherwise
14:25 <+roasbeef> we'll always need to straddle the boundary between the desire to have a diffuse/resllient graph and just concentrating things in order to achieve better ux (which also comes with several tradeoffs) 
14:25 < t-bast> roasbeef: I agree, but I really think this is a problem we need to start tackling as users are clearly asking for mobile LN wallets, and even if lnd doesn't implement this your opinion on the proposal is useful to shape this to a good solution that has as few trade-offs as possible
14:26 < t-bast> roasbeef: if you look at the proposal, you may be surprised, there has been changes since the ML discussions
14:26 < bitconner> t-bast: some drive by comments after a quick skim 1) the gossip filtering could probably be it's own proposal, it's pretty unrelated to the packet format/construction, 2) the privacy arguments are still pretty weak imo, idt they should be a core argument for trampoline, 3) o/w draft looks very detailed and thorough! overall tho i still think trampoline is a little premature when there are simpler 
14:26 < bitconner> ways of improving graph sync and/or shrinking the graph
14:26 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:26 < niftynei> but i'm sure i'm missing some nuance of roasbeef's points. i also sadly have to run, but it was great to talk to some ppl today :)
14:27 < t-bast> niftynei: thanks, I really think that this high-level proposal format is very useful for review/design discussions :)
14:27 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
14:27  * t-bast waves goodbye at niftynei
14:27 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
14:27 <+roasbeef> mhmm, also don't forget that we also observe/support the mobile use case (although it isn't our primary focus rn) and have from a a distinct perspective (we don't operate a gateway node for the app users) 
14:28 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
14:28 < t-bast> bitconner: thanks! Clearly I think the PR will eventually be split (I believe I do mention this in the description), I totally agree on that but wanted a first high-level view that encompasses most aspects.
14:28 -!- mauz555 [~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829] has joined #lightning-dev
14:29 < t-bast> bitconner: can you suggest other ways of improving graph sync? Honestly we've tried some of those and found them all lacking
14:29 <+roasbeef> btw, i'm not trying to like shoot this down or anything, just sharing a bit of my pov which includes a foray into the mobile land and also the belief there's a lot we can gain from better node management tools for the internal network 
14:30 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:30 <+roasbeef> t-bast: i think it depepnds on if you always want the entire graph, or are willinag to prune more aggressilvey at the clients to only keep the graph that you'll likely need to traverse 
14:30 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
14:30 < t-bast> roasbeef: the issue is that many things can go wrong in estimating what "you'll likely need to traverse" :)
14:31 < ThomasV> roasbeef: what would bea good pruning strategy?
14:31 < t-bast> either it ends up still requiring more syncing than is acceptable for a decent mobile UX on non 4G network, or payments fail quite often
14:32 < t-bast> I'll have to drop off too it's getting late here :), but thanks for your early comments roasbeef/bitconner. I'd really appreciate a summary of those on the PR to keep the discussion going (and potentially explore other ideas) and allow others to chime in
14:33 < t-bast> #endmeeting
14:33 < lightningbot> Meeting ended Mon Apr 13 21:33:06 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
14:33 < lightningbot> Minutes:        http://www.erisian.com.au/meetbot/lightning-dev/2020/lightning-dev.2020-04-13-20.12.html
14:33 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/lightning-dev/2020/lightning-dev.2020-04-13-20.12.txt
14:33 < lightningbot> Log:            http://www.erisian.com.au/meetbot/lightning-dev/2020/lightning-dev.2020-04-13-20.12.log.html
14:33 < bitconner> sounds good i'll follow up there, later t-bast!
14:33 < ThomasV> ok, good night
14:33 < t-bast> thanks a lot! see you all on github ;)
14:34 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:34 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
14:34 -!- sstone [~sstone@185.186.24.109.rev.sfr.net] has quit [Quit: Leaving]
14:35 -!- t-bast [~t-bast@2a01:e34:efde:97d0:de9:76ec:fb74:9c75] has quit [Quit: Leaving]
14:38 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:39 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
14:43 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:43 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
14:47 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:48 <+roasbeef> ThomasV: depends on what you want to optimize for, the beauty of it is that it's also something at the end points and not internal network changes, not sure if you've been following the latest iterations of what we call "mission control" in lnd? 
14:48 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
14:49 < ThomasV> not really.. 
14:49 < ThomasV> but I agree internal network changes should be avoided if possible
14:50 -!- per [~per@gateway/tor-sasl/wsm] has quit [Remote host closed the connection]
14:50 -!- per_ [~per@gateway/tor-sasl/wsm] has joined #lightning-dev
14:51 -!- mauz555 [~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829] has quit [Read error: Connection reset by peer]
14:52 < bitconner> t-bast, ThomasV: here's one example of a stricter pruning strategy we can consider https://github.com/lightningnetwork/lightning-rfc/pull/767
14:52 < ThomasV> but is trampoline really 'internal', when nobody knows what's in the onion? :D
14:53 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:53 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
14:55 -!- arij [uid225068@gateway/web/irccloud.com/x-bjjrqpoqlrkhmyom] has quit [Quit: Connection closed for inactivity]
14:55 < ThomasV> bitconner: ty
14:58 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
14:59 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:02 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:03 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:04 < darosior> bitconner: re your PR, "The current pruning strategy will keep the channel in its routing table because y'alls continues to send fresh channel_updates, but the channel is actually unusable because the other party is never online" => but we prune if you don't have *both* channel updates new than (now - 2weeks) ?
15:04 < darosior> Or am i missing something ?
15:05 < darosior> (At least that's what CL does)
15:05 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:06 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:08 < bitconner> darosior: maybe CL is stricter than the spec in this regard? lnd uses the latest timestamp
15:09 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:09 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:10 < bitconner> last i checked all impls seem to have pretty similar graph sizes, i would be a little surprised if we weren't all applying the same strategy atm
15:12  * darosior double checks
15:12 < darosior> Ok, no, my bad : we prune if both updates are before the deadline :-)
15:13  * darosior goes back to sleep
15:13 < bitconner> hehe :) 
15:14 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:14 <+roasbeef> ThomasV: well it needs certain nodes to actually be able to switch over to the diff forwawrding scheme, so that's internal ofc it can still work if less than 100% of the network adopts it, but if only a handful do then the anon set is even further restricted (on top of all the issues we already have) 
15:14 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 260 seconds]
15:14 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:17 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:18 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:23 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:23 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:27 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:27 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:29 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 256 seconds]
15:32 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:32 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:36 -!- mauz555 [~mauz555@88.125.182.66] has joined #lightning-dev
15:38 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev
15:39 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:39 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:42 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:42 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:46 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 265 seconds]
15:47 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:48 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:54 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:54 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
15:57 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
15:57 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:02 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:02 -!- marcoagner [~user@2001:8a0:6a5f:a900:6d3e:1158:b50:97b6] has quit [Ping timeout: 260 seconds]
16:02 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:05 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:05 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:06 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:06 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #lightning-dev
16:06 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:09 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:10 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:13 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:14 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
16:14 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:16 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:17 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 256 seconds]
16:17 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:18 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Quit: Leaving]
16:18 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:19 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:22 -!- mauz555 [~mauz555@88.125.182.66] has quit [Remote host closed the connection]
16:22 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:25 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:27 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:27 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:32 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
16:33 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:34 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:36 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:37 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:39 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
16:41 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:41 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:44 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:45 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:49 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 256 seconds]
16:52 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:52 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
16:54 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
16:55 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
17:01 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
17:02 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
17:07 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
17:07 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
17:12 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
17:13 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
17:17 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 265 seconds]
17:28 -!- mauz555 [~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829] has joined #lightning-dev
17:33 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev
17:33 -!- mauz555 [~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829] has quit [Ping timeout: 246 seconds]
17:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev
17:44 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds]
17:51  * rusty turns up 5 hours late for the meeting!
17:57 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Remote host closed the connection]
17:57 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
18:04 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
18:04 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
18:05 -!- jonatack [~jon@37.165.18.125] has quit [Ping timeout: 256 seconds]
18:06 -!- jonatack [~jon@109.202.107.147] has joined #lightning-dev
18:09 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
18:14 -!- riclas [riclas@77.7.37.188.rev.vodafone.pt] has quit [Ping timeout: 256 seconds]
18:18 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
18:19 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
18:24 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
18:24 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
18:29 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
18:29 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
18:30 -!- Goriya [~Goriya@tcmson2003w-lp140-01-69-159-34-103.dsl.bell.ca] has joined #lightning-dev
18:31 < Goriya> heyy!!
18:34 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
18:34 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
18:35 <+roasbeef> rusty: heh, isn't AU the reason it changes 3 times a year? :p 
18:35 < rusty> roasbeef: yeah, am still lobbying to remove DST :(
18:47 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
18:48 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
18:48 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #lightning-dev
18:55 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
18:55 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
18:58 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
18:58 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #lightning-dev
18:59 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
18:59 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
19:09 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
19:09 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
19:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
19:13 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
19:13 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
19:17 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev
19:18 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 260 seconds]
19:21 -!- mol [~molly@unaffiliated/molly] has joined #lightning-dev
19:24 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
19:24 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
19:25 -!- mol [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer]
19:26 -!- mol [~molly@unaffiliated/molly] has joined #lightning-dev
19:33 -!- hkjn0 [~hkjn@163.172.184.153] has joined #lightning-dev
19:53 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
19:53 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
20:05 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
20:05 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
20:11 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
20:11 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
20:14 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Remote host closed the connection]
20:15 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
20:25 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
20:26 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
20:30 -!- captjakk [~captjakk@174-29-9-247.hlrn.qwest.net] has quit [Remote host closed the connection]
20:31 -!- captjakk [~captjakk@174-29-9-247.hlrn.qwest.net] has joined #lightning-dev
20:32 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
20:33 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
20:34 -!- captjakk [~captjakk@174-29-9-247.hlrn.qwest.net] has quit [Remote host closed the connection]
20:35 -!- captjakk [~captjakk@174-29-9-247.hlrn.qwest.net] has joined #lightning-dev
20:37 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
20:38 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
20:43 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
20:43 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
20:49 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
20:49 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
20:58 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
20:59 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
21:08 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
21:08 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
21:16 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
21:16 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
21:21 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
21:21 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
21:31 -!- jimpo_ [~jimpo@ec2-13-57-39-52.us-west-1.compute.amazonaws.com] has joined #lightning-dev
21:35 -!- drolmer_ [~drolmer@unaffiliated/drolmer] has joined #lightning-dev
21:35 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #lightning-dev
21:36 -!- sanket1729_ [~sanket172@72.36.89.11] has joined #lightning-dev
21:38 -!- warren_ [~warren@fedora/wombat/warren] has joined #lightning-dev
21:38 -!- jonasschnelli_ [~jonasschn@2a01:4f8:172:10da::2] has joined #lightning-dev
21:40 -!- Netsplit *.net <-> *.split quits: sanket1729, jonasschnelli, drolmer, warren, jimpo
21:42 -!- gambpang [~gambpang@unaffiliated/gambpang] has quit [Ping timeout: 264 seconds]
21:45 -!- gambpang [~gambpang@unaffiliated/gambpang] has joined #lightning-dev
21:46 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
21:46 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
22:03 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Remote host closed the connection]
22:04 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
22:08 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev
22:09 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
22:09 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
22:13 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
22:14 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
22:16 -!- captjakk [~captjakk@174-29-9-247.hlrn.qwest.net] has quit [Remote host closed the connection]
22:17 -!- captjakk [~captjakk@174-29-9-247.hlrn.qwest.net] has joined #lightning-dev
22:17 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
22:17 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
22:21 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
22:21 -!- captjakk [~captjakk@174-29-9-247.hlrn.qwest.net] has quit [Ping timeout: 265 seconds]
22:22 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
22:23 -!- Goriya [~Goriya@tcmson2003w-lp140-01-69-159-34-103.dsl.bell.ca] has quit [Ping timeout: 265 seconds]
22:29 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
22:29 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
22:39 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
22:39 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
22:44 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
22:45 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
22:52 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 258 seconds]
23:00 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
23:00 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
23:06 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
23:06 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
23:28 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
23:30 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 260 seconds]
23:30 -!- achow101 [~achow101@unaffiliated/achow101] has joined #lightning-dev
23:32 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #lightning-dev
23:36 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
23:36 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
23:52 -!- nibbier [~quassel@mx01.geekbox.info] has quit [Read error: Connection reset by peer]
23:53 -!- nibbier [~quassel@mx01.geekbox.info] has joined #lightning-dev
--- Log closed Tue Apr 14 00:00:51 2020