--- Log opened Thu Nov 05 00:00:07 2020 00:01 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 01:08 < m-schmoock> niftynei: I have a open question/suggestion with rusty on #4168 . Technically wise I can ACK, though I think the current way of setting before/after per hook and not per plugin seems a bit overkill to me. ( https://github.com/ElementsProject/lightning/pull/4168#issuecomment-721008371 ) 01:11 < m-schmoock> niftynei: Also #4175 #4176 are issues I discovered recently. Not critical, but ugly 01:15 -!- kexkey [~kexkey@static-198-54-132-134.cust.tzulo.com] has quit [Ping timeout: 256 seconds] 01:18 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 01:18 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection] 01:45 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 01:49 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds] 01:50 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 01:54 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds] 01:57 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 02:08 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 02:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 02:12 -!- vasild_ is now known as vasild 02:22 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 02:22 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 03:02 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection] 03:03 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 03:10 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 03:17 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 03:17 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 03:20 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds] 03:21 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 03:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 03:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 03:46 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 03:52 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 03:56 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 264 seconds] 05:06 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 05:15 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 256 seconds] 05:24 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Quit: leaving] 05:27 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection] 05:27 < m-schmoock> cdecker: I'm still undecided if we should really merge closure cause 'onchain' to 'remote' or rather keep it. I see a node can force close on "fee issues for committed htlcs" (test_onchain_feechange), on fee issues while closing (test_closing_different_fees), on penalty, on ... If someone closes on us for these reasons, they are all not really 'remote' (intentionally). And since we can't see their 05:27 < m-schmoock> internal protocol reasons (because we can't read their RAM :) we may distinguish "onchain" from "remote", as "remote" currently really only means "by remote peer". 05:27 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has joined #c-lightning 05:28 < m-schmoock> When writing the tests this becomes more obvious... but the feature actually works, this is now just naming and categorization issues 05:45 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 260 seconds] 06:47 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 06:47 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 06:55 -!- kexkey [~kexkey@static-198-54-132-150.cust.tzulo.com] has joined #c-lightning 06:58 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 07:01 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 07:55 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: Leaving] 08:01 < willcl_ark> Can I reload a config file while my node is still running to for example update log-level without restarting? IIRC SIGHUP is used for log file rotation, but perhaps there is something similar for config file? 08:03 < az0re> willcl_ark: Try signal 9, I think that does it 08:04 < zmnscpxj_> Is that not SIGKILL? 08:04 < az0re> hehehe 08:04 < willcl_ark> that is SIGKILL 08:04 < az0re> :) 08:04 < az0re> ah well, it was worth a try 08:04 < willcl_ark> perhaps not possible to reload config without restart, but it would be nice to be able to change log-levels on the fly, IMO 08:10 < willcl_ark> zmnscpxj_: CLBOSS seemed to cope ok even during that crazy fee market. It did open two channels (when I had zero) at a rate of 250s/vB (two in one transaction), but then seemed to "wait" until fees were lower again to open a further 5. I suppose because of how agnositc it is, 5 out of 7 channels are to various LNBIG nodes which is probably not ideal, but difficult to automatically bucket peers by "likely same 08:10 < willcl_ark> owner" 08:11 < zmnscpxj_> Yes, if a majority of your funds is outside of channels, CLBOSS will put as much as possible into channels even if feerates are high 08:12 < zmnscpxj_> but it tries to hold off as much as it can until feerates go low 08:12 < willcl_ark> That is pretty much exactly what I saw 08:12 < zmnscpxj_> works as designed then 08:13 < willcl_ark> :) 08:13 < zmnscpxj_> TheBlueMatt has suggested IP binning before (in the context of routing, but still...) so it might be useful to consider that as well 08:13 < zmnscpxj_> in order to avoid the "everryone is LNBIG in purgatory" 08:13 < willcl_ark> TBH, looks like the LNBIG nodes are hosted in different locations (on 1ML) so not sure that will help 08:13 < zmnscpxj_> awww crap 08:13 < willcl_ark> you could base it on Alias, but that's easy to break too 08:13 < zmnscpxj_> yes 08:14 < zmnscpxj_> and using IP binning does not help with .onion as well 08:14 < willcl_ark> actually I am not correct, all the LNBIG nodes I partnered with appear to be (Ashburn, VA, United States) 08:14 < willcl_ark> might be worth to have it "just in case", even if it's not perfect, I don't think it would make anything worse 08:15 < zmnscpxj_> okay, looks like IP binning might be useful at least to *reduce* the possibility 08:15 < willcl_ark> exactly 08:15 < zmnscpxj_> Dunno what to do about .onion though, oh well 08:16 < zmnscpxj_> And I have to wonder about IPv6 as well 08:17 < darosior> asmap ? 08:17 < zmnscpxj_> what is asmap? 08:18 < darosior> bitcoind's new technique to make sybil connections more costy but that may be nonsensical for your matter 08:18 < zmnscpxj_> references? 08:19 < darosior> https://github.com/bitcoin/bitcoin/issues/16599 08:19 < zmnscpxj_> yes, TheBlueMatt has also suggested this for LN routing as well 08:21 < zmnscpxj_> though he suggests all .onion should go into a single bin, which worries me 08:22 < willcl_ark> You could allow more from the tor bin, than other bins? 08:22 < zmnscpxj_> could be done as well. 08:23 -!- Teoti [~teoti@66.245.254.7] has joined #c-lightning 08:37 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Quit: Leaving] 08:38 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 09:25 -!- jasan [~jasan@adsl-dyn222.91-127-240.t-com.sk] has joined #c-lightning 09:26 < jasan> cdecker: is https://hdevalence.ca/blog/2020-10-04-its-25519am 09:26 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection] 09:27 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 09:28 < jasan> (relevant?) 09:31 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds] 09:36 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 10:24 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 10:26 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 10:30 -!- jasan [~jasan@adsl-dyn222.91-127-240.t-com.sk] has quit [Quit: bye!] 10:35 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 10:43 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 264 seconds] 11:36 -!- jasan [~jasan@2001:470:6f:200:7d50:2ff3:2464:ad91] has joined #c-lightning 11:37 -!- jasan [~jasan@2001:470:6f:200:7d50:2ff3:2464:ad91] has quit [Client Quit] 11:42 -!- aj [aj@cerulean.erisian.com.au] has quit [Quit: leaving] 12:07 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 12:08 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 12:17 < HelloShitty> Hello everyone 12:18 < HelloShitty> Can we check if our node has served anyone's payment as route? 12:27 < darosior> Hi, you can check if you forwarded a payment with `listforwards` and the payer will know if their payment went through you 12:27 < darosior> Without asking the payer you can't *reliably 12:27 < darosior> * know 12:43 < HelloShitty> darosior: I know some payment went through me 12:43 < HelloShitty> because the balance of one of my channels has changed 12:44 < HelloShitty> an I haven't made any payment. So I know, some payment has through my node, I guess. 12:45 < darosior> Yeah, `listforwards` will return some successful payments then 12:45 < darosior> https://lightning.readthedocs.io/lightning-listforwards.7.html 12:46 <@niftynei> `getinfo` will also list total routing fees earned 12:46 <@niftynei> if the value is greater than zero, you have successfully routed a payment 12:47 < HelloShitty> hum, let me check 12:47 < HelloShitty> actually I have 2 channels which balance has changed 12:50 < HelloShitty> yeah, at least 2 forward payments 12:50 < HelloShitty> all the other says "WIRE_TEMPORARY_CHANNEL_FAILURE" 13:17 < darosior> Yeah you usually have more failure than success :) 13:31 < HelloShitty> darosior: why that happens? Recent node? Is that it? Or because my channel's overal capacity is still very small? 13:34 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection] 13:44 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 13:46 < darosior> You can't know, if i know your id i could make a payment coming through your node right now that will never succeed 13:48 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 13:49 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 13:54 < HelloShitty> darosior: but you say that because you could try to create an invoice in which you insert some conitions that would make it fail? 13:54 < HelloShitty> Or why you say that? 13:54 < HelloShitty> I mean, if you do that with a value higher than my overall channel capacity, for sure it will fail, right? 13:54 < darosior> To point out that you can't know why it failed and for whatever reason it did 13:55 < HelloShitty> In the best case scenario. Many others can happen, like any node in the routing be also unable to provide liquidity to route that trnascation 13:55 < HelloShitty> ah ok 13:55 < darosior> If i do that to me with a hash for which i won't release the preimage 13:56 < darosior> Or for an applied example see https://github.com/lightningd/plugins/tree/master/probe 13:56 < HelloShitty> yeah, that means you try to execute a transaction for which you don't have the unlock key/password 13:56 < HelloShitty> ohh, let me read that link 13:56 < HelloShitty> seems interesting, actually 14:12 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection] 14:12 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has joined #c-lightning 14:36 < darosior> Arf good catch niftynei :( 14:44 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 14:45 < darosior> Will address the review tomorrow morning 14:45 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 14:52 -!- belcher_ is now known as belcher 15:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:08 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection] 16:47 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 16:52 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds] 16:58 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 17:24 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 18:18 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Client Quit] 18:35 -!- gwillen [~gwillen@unaffiliated/gwillen] has quit [Ping timeout: 256 seconds] 18:37 -!- gwillen [~gwillen@unaffiliated/gwillen] has joined #c-lightning 18:48 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 18:53 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds] 19:02 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds] 19:09 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 19:15 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 19:27 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 19:32 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 256 seconds] 19:53 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 19:53 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds] 20:30 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 20:31 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 20:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 20:31 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 20:36 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 256 seconds] 20:46 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 20:50 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Read error: Connection reset by peer] 20:50 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has joined #c-lightning 21:28 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 21:37 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds] 23:15 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning --- Log closed Fri Nov 06 00:00:08 2020