--- Log opened Sun Oct 10 00:00:31 2021
00:15 -!- jasan [~j@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has quit [Ping timeout: 246 seconds]
00:18 -!- jasan [~j@adsl-dyn71.78-98-36.t-com.sk] has joined #c-lightning
02:30 -!- Jackielove4u [uid43977@user/jackielove4u] has quit [Read error: Connection reset by peer]
02:33 -!- Jackielove4u [uid43977@user/jackielove4u] has joined #c-lightning
02:41 -!- jasan [~j@adsl-dyn71.78-98-36.t-com.sk] has quit [Ping timeout: 252 seconds]
02:43 -!- jasan [~j@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has joined #c-lightning
03:04 -!- kexkey [~kexkey@static-198-54-132-108.cust.tzulo.com] has quit [Ping timeout: 245 seconds]
03:05 -!- kexkey [~kexkey@static-198-54-132-124.cust.tzulo.com] has joined #c-lightning
03:35 -!- Jackielove4u_ [uid43977@user/jackielove4u] has joined #c-lightning
03:35 -!- Jackielove4u [uid43977@user/jackielove4u] has quit [Ping timeout: 260 seconds]
03:35 -!- Jackielove4u_ is now known as Jackielove4u
05:58 -!- jonatack40 [jonatack@user/jonatack] has joined #c-lightning
05:58 -!- jonatack [jonatack@user/jonatack] has quit [Ping timeout: 245 seconds]
08:49 < nathanael> 'lightning-cli istforwards status=local_failed' shows the 'in_channel' - is there a way to know the 'out_channel' or is that payment failing before 'going out'?
08:49 < nathanael> *listforwards
08:50 < mschmoock> hm. for me it shows in_channel and out_channel
08:51 < nathanael> oh wait maybe i am blind
08:52 < nathanael> hmm, with status=failed i have a out_channel but with status=local_failed i don't seem to have one
08:53 < mschmoock> yes, because it failed at your node :D
08:54 < nathanael> but the failreson is 'WIRE_TEMPORARY_CHANNEL_FAILURE' which according to the source code means that the capacity was insufficient
08:55 < nathanael> doesn't the other node know the capacity of my channel with it? 
08:55 < nathanael> it doesn't now the outgoing capacity
08:55 < nathanael> of my node 
08:55 < nathanael> *know
08:55 < mschmoock> my node show WIRE_FEE_INSUFFICIENT (which would not have an out_channel), WIRE_REQUIRED_NODE_FEATURE_MISSING (also okay to have no out channel) and WIRE_TEMPORARY_CHANNEL_FAILURE  where I would agree there 'could' be an out_channel. 
08:56 < mschmoock> ah and WIRE_PERMANENT_CHANNEL_FAILURE and WIRE_UNKNOWN_NEXT_PEER
08:56 < nathanael> i've only WIRE_TEMPORARY_CHANNEL_FAILURE and thought there should be a out_channel
08:57 < mschmoock> if the WIRE_TEMPORARY_CHANNEL_FAILURE was caused by the in channel (I wonder why) it could have no out_channel. But I agree that I would expect more ones with out_channel. maybe worth investiaging
08:57 < nathanael> i agree. shouldn't be cause by the in channel cause that node knows the capacity
08:58 < mschmoock> For WIRE_PERMANENT_CHANNEL_FAILURE it shows me an out_channel even with status local_failed
08:58 < nathanael> yeah i have not one with out_channel
08:59 < mschmoock> okay, but if the reason is local_failed, then there cannot ever be an out_channel that is causing it
09:00 < mschmoock> so all the WIRE_TEMPORARY_CHANNEL_FAILURE we see must relate to something else, which Im also interested in now :D
09:01 < mschmoock> maybe exactly that your in_channel has not enough capacity and the way to respond to that is WIRE_TEMPORARY_CHANNEL_FAILURE
09:02 < mschmoock> lol I found one WIRE_INVALID_ONION_HMAC in my failed forwards. I how that happened
09:02 < mschmoock> *I wonder
09:02 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
09:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 276 seconds]
09:08 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
09:09 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
09:26 < mschmoock> today I learned how not to use wiregen :D
09:29 < nathanael> was afk. hmm, status=failed doesn't show any failreason (cause we don't know?!)
09:30 < nathanael> hmm, if the combination of local_failed and WIRE_TEMPORARY_CHANNEL_FAILURE means there is never an out_channel, why is the reason insufficient funds? cause the in_channel should know the capacity and not use the channel if the capacity is too low
09:31 < nathanael> btw. i am taking the info about not sufficient capacity from this comment: https://github.com/ElementsProject/lightning/blob/5c38e5a08fbf15cc4a7e31ef1a017b580b11a4c6/plugins/libplugin-pay.c#L1250
09:32 < nathanael> my technical understanding of lightning is still a wip, maybe (probably) i miss something here :)
09:46 < mschmoock> The reason why we do not have a code for INSUFFICIENT_CAPACITY is that we dont want other to know our balance which is why we aggregate all errors to be WIRE_TEMPORARY_CHANNEL_FAILURE
09:49 < nathanael> so WIRE_TEMPORARY_CHANNEL_FAILURE could mean something else than INSUFFICIENT_CAPCITY? especially when there is no out_channel right? cause the node on the other side of the in_channel should know the capacity of the channel and not trigger INSUFFICIENT_CAPACITY/WIRE_TEMPORARY_CHANNEL_FAILURE
09:58 < mschmoock> yes, the in_channel node should have not send us an HTLC when he already knows we cant handle it
09:58 < mschmoock> however we would still responde with WIRE_TEMPORARY_CHANNEL_FAILURE I guess
10:01 < nathanael> ok thx
12:16 -!- function1 [~shawoop@199.115.117.198] has joined #c-lightning
12:24 < function1> is it normal to see a lot of "Sending XXXmsat over Y hops..." followed by "htlc failed from nth node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)"
16:22 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 252 seconds]
16:33 -!- rusty [~rusty@pa49-178-39-200.pa.nsw.optusnet.com.au] has joined #c-lightning
16:35 -!- belcher [~belcher@user/belcher] has joined #c-lightning
17:19 -!- rusty [~rusty@pa49-178-39-200.pa.nsw.optusnet.com.au] has quit [Ping timeout: 252 seconds]
18:30 -!- jarthur [~jarthur@cpe-70-114-198-37.austin.res.rr.com] has quit [Ping timeout: 265 seconds]
18:36 -!- jarthur [~jarthur@2603-8080-1540-002d-0c1e-9eda-4f87-19b3.res6.spectrum.com] has joined #c-lightning
18:37 -!- Jackielove4u [uid43977@user/jackielove4u] has quit [Read error: Connection reset by peer]
18:52 -!- Jackielove4u [uid43977@user/jackielove4u] has joined #c-lightning
19:47 -!- kexkey [~kexkey@static-198-54-132-124.cust.tzulo.com] has quit [Quit: Textual IRC Client: www.textualapp.com]
20:02 -!- jarthur [~jarthur@2603-8080-1540-002d-0c1e-9eda-4f87-19b3.res6.spectrum.com] has quit [Quit: jarthur]
20:23 -!- rusty [~rusty@pa49-178-39-200.pa.nsw.optusnet.com.au] has joined #c-lightning
20:32 -!- rusty [~rusty@pa49-178-39-200.pa.nsw.optusnet.com.au] has quit [Ping timeout: 252 seconds]
20:53 -!- rusty [~rusty@pa49-178-39-200.pa.nsw.optusnet.com.au] has joined #c-lightning
21:15 -!- rusty [~rusty@pa49-178-39-200.pa.nsw.optusnet.com.au] has quit [Ping timeout: 252 seconds]
22:08 -!- rusty [~rusty@pa49-178-39-200.pa.nsw.optusnet.com.au] has joined #c-lightning
22:59 -!- rusty [~rusty@pa49-178-39-200.pa.nsw.optusnet.com.au] has quit [Ping timeout: 265 seconds]
23:56 -!- Guest38 [~Guest38@2603-8081-2504-2b23-e1a6-c28e-417b-de2c.res6.spectrum.com] has joined #c-lightning
23:56 < Guest38> is there a way to change where the rpc port in the config?
--- Log closed Mon Oct 11 00:00:32 2021