--- Log opened Mon Sep 28 00:00:31 2020
00:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
00:28 -!- jonatack [~jon@37.167.90.115] has quit [Ping timeout: 265 seconds]
00:30 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer]
00:30 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has joined #c-lightning
00:39 -!- jonatack [~jon@37.167.90.115] has joined #c-lightning
00:43 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
00:49 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
00:51 -!- jonatack [~jon@37.167.90.115] has quit [Quit: jonatack]
00:51 -!- jonatack [~jon@213.152.180.5] has joined #c-lightning
01:00 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
01:04 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
01:10 -!- vincenzopalazzo [~vincent@host-79-43-189-105.retail.telecomitalia.it] has joined #c-lightning
02:32 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
03:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
03:11 -!- timCF [511495c8@200-149-20-81.sta.estpak.ee] has joined #c-lightning
03:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
03:12 < timCF> Hi guys! Is there some sort of detailed API documentation for c-lightning JSON RPC? I have seen only CLI examples, not not actual web API docs
03:14 < vincenzopalazzo> can you look here https://lightning.readthedocs.io/PLUGINS.html
03:16 < timCF> Thanks!
03:33 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
03:47 -!- jonatack [~jon@213.152.180.5] has quit [Ping timeout: 240 seconds]
03:57 -!- timCF [511495c8@200-149-20-81.sta.estpak.ee] has quit [Remote host closed the connection]
04:17 -!- jonatack [~jon@37.167.111.11] has joined #c-lightning
04:25 -!- ark [59205054@89.32.80.84] has joined #c-lightning
04:27 < ark> HelloIs there a way to know which channel a payment was being routed through when a local failure occurred?It would be useful to optimize the liquidity of the channels
04:33 -!- jonatack [~jon@37.167.111.11] has quit [Ping timeout: 256 seconds]
04:56 < m-schmoock> ark: the `listforwards` command has two properties for that 'in_channel' and 'out_channel'
04:56 < m-schmoock> is that what you have been looking for?
05:18 < ark> yes
05:19 < ark> {         "payment_hash": "76e5183f747a1e855cf54dcb6290e507efd60491780d8093f1390428e60224a9",         "in_channel": "620541x2466x1",         "in_msatoshi": 165035130,         "in_msat": "165035130msat",         "status": "local_failed",         "failcode": 4103,         "failreason": "WIRE_TEMPORARY_CHANNEL_FAILURE",         "received_time":
05:19 < ark> 1601266587.597      }
05:20 < ark> But when it fails on the local node it doesn't show the output channel for which it has failed
05:21 < m-schmoock> you mean if your node is the originator of the payment or if a remote payment fails at your node?
05:23 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
05:24 < ark> Not
05:24 < ark> I mean that if my node is forwarding a payment and it fails because there is not enough outgoing balance on the channel they ask me to resend. I want to know which channel was the one that caused the problem
05:24 < darosior> ark: then it's an incoming channel failure. You can checkout a summary of outbound failure with:
05:24 < darosior> for scid in $(lc listpeers |jq -r '.peers | map(.channels[].short_channel_id)[]');do echo "$scid failed $(lc listforwards |jq -r '.forwards | map(select(.status | contains("failed")).out_channel)' |grep $scid |wc -l) times";done
05:24 < darosior> From https://gist.github.com/darosior/f85aed5bcc9c0a40f9fc3fe204b3f6c9
05:24 < darosior> Ah and lc is lightning-cli
05:26 < darosior> As per the presence of the outgoing channel it's determined --as per the manpage https://lightning.readthedocs.io/lightning-listforwards.7.html#return-value -- by the presence of a failure before we even determine this outgoing channel.
05:28 < ark> thank you
05:29 < m-schmoock> darosior: nice script h4cks :D
05:29 < darosior> :) I should really add those to the summary plugin
05:29 < darosior> But i wanted to make it nicer before doing so
05:29 < darosior> And never got to it
05:31 < m-schmoock> darosior: maybe I can do that. If its gonna be in the summary in an extra column we need to calculate this on the fly via hooks, as the computation would take to long wverytime the user executes summary
05:32 < darosior> I was thinking as an additional command
05:32 < darosior> routing-summary like
05:32 < m-schmoock> yes
05:32 < darosior> To keep the plugin stateless
05:33 < m-schmoock> also the average size of failed and forwarded htlcs would be interesting
05:33 < m-schmoock> maybe even top and lowest 10 percentile
05:33 < m-schmoock> darosior: summary is already stateful
05:34 < m-schmoock> it maintains a file to track the remotes availability already
05:34 < darosior> Oh yeah i forgot
05:34 < m-schmoock> but I dont think the output would fit
05:34 < m-schmoock> maybe via additional switch
05:34 < m-schmoock> but then nobody  knows, maybe a own plugin with more stuff
05:34 < darosior> Maybe better off using a small sqlite at this stage
05:34 < m-schmoock> maybe we start with a 'routingstats' plugin 
05:35 < darosior> Yeah def
05:35 < m-schmoock> cool
05:35 < m-schmoock> looking forward to it
05:35 < darosior> I started porting my hacks slowly
05:35 < darosior> to lightningd/plugins
05:35 < m-schmoock> nvm, my todo list is ultra large
05:36 < darosior> Like https://github.com/lightningd/plugins/pull/147 or https://github.com/lightningd/plugins/pull/82
05:37 < ark> It would be great what you comment
05:37 < m-schmoock> I really like 147
05:38 < ark> Another thing that could be good is to see the average rates of the nodes in the environment
05:40 < ark> Or even if onion routing is not used. Know the route that a payment has taken to do studies and find out if it would be profitable to open a channel with a previous node
05:48 -!- skme9 [~skme9@2402:3a80:698:c90c:34d1:4385:33f9:f2f5] has quit [Ping timeout: 240 seconds]
05:49 < darosior> Definitely, that's the goal of 82
05:52 < m-schmoock> yes. working on channel hygiene and network health is one of the more important stuff we can work on. Having a LN node you will likely never get rich of, but you can at least improve the network :D. Because currently I think a lot of bad and outdated nodes do more harm than good to the network
07:17 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
07:37 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
07:37 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
08:04 -!- ark [59205054@89.32.80.84] has quit [Remote host closed the connection]
08:08 -!- skme9 [~skme9@2402:3a80:698:c90c:40a3:3720:ba34:18d8] has joined #c-lightning
08:47 -!- skme9 [~skme9@2402:3a80:698:c90c:40a3:3720:ba34:18d8] has quit [Ping timeout: 240 seconds]
08:50 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer]
08:51 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has joined #c-lightning
10:20 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection]
10:22 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
10:26 < az0re> I assume other people are doing LN channel graph analysis to optimize various channel metrics; is there anything public?
10:29 < az0re> darosior:
10:29 < az0re> user@host:~$ for scid in $(lc listpeers |jq -r '.peers | map(.channels[].short_channel_id)[]');do echo "$scid failed $(lc listforwards |jq -r '.forwards | map(select(.status | contains("failed")).out_channel)' |grep $scid |wc -l) times";done
10:29 < az0re> parse error: Invalid numeric literal at line 1, column 5
10:30 < az0re> Oh, probably lc is supposed to be an alias for lightning-cli
10:53 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
12:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
12:42 -!- martindale [ericfabric@gateway/shell/matrix.org/x-pjuyuxqsnaoarwte] has joined #c-lightning
13:16 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
13:45 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
14:04 < m-schmoock> darosior: I made a quick review on plugins #147 and test it for a couple of days
14:11 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
14:12 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection]
14:12 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
14:14 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
14:14 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
14:15 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning
14:42 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
14:54 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
15:02 < m-schmoock> darosior: using your success/failure HTLC stat snippet, I figured I have some channels that fail on HTLCs about 90% of the time or more. Then I have some that are 50/50 and some that are really good on forwarding. Do you think one should care about bad peers in terms of HTLC forwarding successrate stats?
15:04 < m-schmoock> I try to understand if theres more metrics we can calculate and/or give to the users. I.e. relative channel size, small channels tend to have a worse successrate. maybe other ideas?
15:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
15:12 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
15:16 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
15:17 -!- vincenzopalazzo [~vincent@host-79-43-189-105.retail.telecomitalia.it] has quit [Remote host closed the connection]
15:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
15:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
16:16 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
16:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
16:49 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
17:48 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
17:48 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
17:53 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
18:00 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
18:00 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
18:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
18:37 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
18:40 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
18:42 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
19:08 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
19:08 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
19:10 -!- skme9 [~skme9@2402:3a80:691:8f38:28cb:2224:2052:d7ad] has joined #c-lightning
19:10 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
19:20 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Remote host closed the connection]
19:21 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning
19:28 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
20:13 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
20:13 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
20:18 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
20:40 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
22:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
23:11 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
23:21 -!- skme9 [~skme9@2402:3a80:691:8f38:28cb:2224:2052:d7ad] has quit [Ping timeout: 240 seconds]
23:25 -!- skme9 [~skme9@2402:3a80:691:8f38:28cb:2224:2052:d7ad] has joined #c-lightning
23:57 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds]
--- Log closed Tue Sep 29 00:00:32 2020