--- Log opened Wed Dec 16 00:00:48 2020 00:14 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 00:38 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning [] 00:38 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning 01:24 -!- vincenzopalazzo [~vincent@2001:b07:6474:9d49:fc00:1cb5:3dd3:aa91] has joined #c-lightning 01:42 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 01:53 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 01:55 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Ping timeout: 260 seconds] 02:13 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 246 seconds] 02:15 -!- jonatack [~jon@134.19.179.147] has joined #c-lightning 02:45 <@cdecker> ark: `lightning-cli listforwards` will show all forwards, filtering can be done on top of the full result for example with `jq` (`jq '.forwards[-2:]'` will show the last two entries for example) 03:51 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 244 seconds] 04:00 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #c-lightning 04:27 < ark> cdecker: 04:27 < ark> Yeah, I know that 04:27 < ark> The thing is that as the number of entries grows it can become very heavy to receive updates from that list. That's why I was saying it. Same as with databases. It could be useful to be able to make requests for it to only be displayed from an index 04:28 <@cdecker> Sure, that kind of pagination is certainly useful, but we currently don't have the facilities to implement that (mostly stuck on designing it, not implementing) 04:29 <@cdecker> Ideally we'd have a common `page` element that describes the ordering, offset and number of elements 04:29 <@cdecker> However that is difficult to design in a way that is consistent: switching from one page to another can contain duplicates if the underlying records changed (added, removed, re-ordered) 04:30 -!- jonatack [~jon@134.19.179.147] has quit [Quit: jonatack] 04:30 <@cdecker> So for now we punted that to the caller until we have a better idea on how to implement it in a generic and useful way 04:33 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning 04:38 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 246 seconds] 04:39 -!- jonatack [~jon@213.152.186.173] has joined #c-lightning 04:45 < ark> And do you plan to implement an uptime and lifetime counter as they have in lnd? 04:45 < ark> It could be useful to obtain metrics 04:49 <@cdecker> So that's uptime = time since last startup, and lifetime = sum of all uptimes? Sounds interesting 04:49 <@cdecker> Certainly doable with the current infrastructure 04:49 <@cdecker> (except lifetime, which can be lossy with unexpected shutdowns) 04:51 < ark> yes 04:51 < ark> Okay 04:51 < ark> But you don't need extreme precision. 04:51 < ark> I mean, its usefulness is to get metrics and see which channels are interesting to keep 04:52 <@cdecker> Oh, you mean on a per-channel basis 04:53 <@cdecker> The summary plugin has that 04:53 < ark> Since you only allow one channel per node, it doesn't matter a bit 04:55 <@cdecker> Yep, the summary plugin will give you a percentage of availability for the last 24h, but can easily be extended 04:56 <@cdecker> We've had that since August apparently and I didn't know ^^ 05:00 < ark> great then 05:01 < ark> It is that I am making an adapter of the interface from cln to lnd in order to use many of the services already implemented 05:05 <@cdecker> Oh, that's really cool ^^ 05:20 -!- vincenzopalazzo [~vincent@2001:b07:6474:9d49:fc00:1cb5:3dd3:aa91] has quit [Remote host closed the connection] 05:34 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 256 seconds] 05:36 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 05:36 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services] 05:36 -!- vasild_ is now known as vasild 05:53 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 05:53 -!- vincenzopalazzo [~vincent@2001:b07:6474:9d49:1cd0:876b:6bfb:cb4a] has joined #c-lightning 07:34 -!- kexkey [~kexkey@static-198-54-132-94.cust.tzulo.com] has joined #c-lightning 07:57 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 07:57 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection reset by peer] 08:17 -!- belcher_ is now known as belcher 08:21 -!- ctrlbreak [~ctrlbreak@159.2.165.130] has quit [Remote host closed the connection] 08:21 -!- ctrlbreak [~ctrlbreak@159.2.165.130] has joined #c-lightning 08:31 -!- ksedgwic [~ksedgwic@192-184-134-31.fiber.dynamic.sonic.net] has quit [Quit: Lost terminal] 08:31 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Remote host closed the connection] 08:32 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 08:36 -!- ksedgwic [~ksedgwic@192-184-134-31.fiber.dynamic.sonic.net] has joined #c-lightning 08:44 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning 08:52 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning [] 08:52 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning 09:16 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 09:19 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 12:46 -!- ark [~ark@89.32.80.84] has quit [Read error: Connection reset by peer] 12:47 -!- ark [~ark@89.32.80.84] has joined #c-lightning 13:17 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Read error: Connection reset by peer] 13:18 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning 14:31 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 14:32 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 14:55 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 272 seconds] 14:59 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #c-lightning 15:08 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 15:15 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 258 seconds] 15:19 -!- vincenzopalazzo [~vincent@2001:b07:6474:9d49:1cd0:876b:6bfb:cb4a] has quit [Remote host closed the connection] 15:33 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #c-lightning 16:15 -!- HelloShitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Quit: leaving] 17:06 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning [] 17:06 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning 17:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:24 -!- Netsplit *.net <-> *.split quits: michaelfolkson, RubenSomsen, ksedgwic, achow101 17:30 -!- Netsplit over, joins: RubenSomsen, ksedgwic, achow101, michaelfolkson 17:36 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services] 17:36 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 17:36 -!- vasild_ is now known as vasild 17:44 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Quit: Leaving] 17:58 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection] 17:58 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:18 < ark> cdecker: Could you put the equivalent of the getblockheader command in cln? 18:21 < ark> I say it because seeing that you already have getrawblockbyheight 18:21 < ark> It should not be very expensive to return only the header 18:21 < ark> I could do it myself with that function, but I see a bit inefficient transmitting a whole 1MB when in reality I am only interested in the header 18:54 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 21:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 21:36 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 22:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds] 22:28 -!- mrostecki [mrostecki@nat/suse/x-wasokcvpgafclwxo] has quit [Quit: WeeChat 1.8] 23:12 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 23:13 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 23:14 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Quit: %bye%] 23:15 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 23:15 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 23:17 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 23:36 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds] 23:36 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 23:37 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 23:37 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning --- Log closed Thu Dec 17 00:00:49 2020