--- Log opened Sat Sep 12 00:00:16 2020
00:22 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 272 seconds]
00:23 -!- fjahr [sid374480@gateway/web/irccloud.com/x-vddusacsufeecjsf] has quit [Ping timeout: 240 seconds]
00:24 -!- fjahr [sid374480@gateway/web/irccloud.com/x-iivtmbwrteacwior] has joined #c-lightning
00:28 -!- RubenSomsen_ [sid301948@gateway/web/irccloud.com/x-lgebcwdtscmlevxn] has joined #c-lightning
00:30 -!- RubenSomsen [sid301948@gateway/web/irccloud.com/x-jtzagdzztgwrkvbx] has quit [Ping timeout: 244 seconds]
00:30 -!- RubenSomsen_ is now known as RubenSomsen
01:15 < darosior> az0re, zmnscpxj: https://github.com/lightningd/plugins/pull/147 :-)
01:15 < darosior> By the way interested if you have some conceptual thoughts on that zmnscpxj 
01:15 < zmnscpxj> does the algo have hysteresis?
01:16 < zmnscpxj> e.g. you are in a low-fee bucket, so the threshold to go to a higher-fee bucket should be higher
01:16 < zmnscpxj> and if you are in a high-fee bucket, the threshold to go to a lower-fee bucket should be lower
01:17 < az0re> was also thinking about that
01:17 < zmnscpxj> for example, suppose you have a threshold of 50%, below 50% you have low fees, above 50% you have high fees
01:17 < zmnscpxj> if you are current low-fee, you need to reach a threshold of say 60% before moving to the high fee
01:17 < zmnscpxj> if you are currently high-fee, you need to reach a threshold of say 40% before moving to the low fee
01:17 < zmnscpxj> something like that
01:18 < zmnscpxj> this should help reduce spamming channel updates
01:20 < darosior> cdecker told me to add this, thanks for detailing i was not sure about the meaning :)
01:20 < zmnscpxj> haha
01:20 < darosior> Yeah, ok
01:20 < darosior> I think my formula does that
01:20 < darosior> It's "exponential"
01:20 < zmnscpxj> another idea to help reduce the privacy-leak aspects would be to trigger at random times, say at a random second each hour, instead of triggering at each forward
01:21 < darosior> new_fees = fees * 50**(0.5 - our_percentage)
01:22 < zmnscpxj> that is not my usual implementation of hysteresis (it usually involves if-then), but I know some continuous models use exponentials to simulate the thresholds, so maybe?
01:22 < az0re> darosior: Nice to see it's being worked on
01:22 < zmnscpxj> <--- not a mathist
01:22 < az0re> I'll look at the code more in-depth later
01:23 < darosior> At 50% it's fees * 1, at 60% it's 1.478 and at 40% it's 0.676
01:23 -!- jonatack [~jon@37.173.136.184] has joined #c-lightning
01:23 < zmnscpxj> hysteresis is not smooth :)
01:23 < zmnscpxj> hmmm
01:23 < darosior> Ah i misunderstood then :)
01:23  * darosior goes checking Wikipedia
01:23 < zmnscpxj> https://en.wikipedia.org/wiki/Schmitt_trigger#/media/File:Hysteresis_sharp_curve.svg
01:24 < darosior> re random time: christian told me about that too ^^
01:24 < zmnscpxj> "out" = fee, "in" = channel share
01:24 < darosior> Oh nice thanks
01:25 < zmnscpxj> also read the article on Schmitt trigger as well, it is a basic electronics engineering trope to handle problems like having a noisy input signal
01:25 < zmnscpxj> I mean imagine if your channel is moving a large payment back and forth
01:30 < darosior> Will definitely do, thanks for the input!
02:11 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Ping timeout: 256 seconds]
02:27 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
02:27 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
02:29 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Quit: ZNC 1.7.5 - https://znc.in]
02:34 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning
02:44 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
02:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
02:50 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
02:51 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
02:52 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
02:53 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
02:57 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
02:57 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
03:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
04:01 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
04:42 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
04:46 -!- jonatack [~jon@37.173.136.184] has quit [Read error: Connection reset by peer]
04:47 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 246 seconds]
04:47 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Read error: Connection reset by peer]
04:48 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
04:49 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
05:37 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
05:57 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning
06:37 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Quit: ZNC 1.7.5 - https://znc.in]
06:41 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning
07:05 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
07:06 -!- jonatack [~jon@static-176-139-55-163.ftth.abo.bbox.fr] has joined #c-lightning
07:09 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]
07:10 -!- jonatack [~jon@static-176-139-55-163.ftth.abo.bbox.fr] has quit [Ping timeout: 244 seconds]
07:12 -!- jonatack [~jon@109.232.227.138] has joined #c-lightning
07:41 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
08:26 -!- jonatack [~jon@109.232.227.138] has quit [Ping timeout: 244 seconds]
09:01 -!- belcher_ is now known as belcher
09:17 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
09:24 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds]
10:35 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
10:35 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
11:30 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
12:30 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
13:22 -!- bdykesfr [~bdykesfr@dhcp-077-249-069-106.chello.nl] has joined #c-lightning
13:48 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
14:04 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection]
14:18 -!- bdykesfr [~bdykesfr@dhcp-077-249-069-106.chello.nl] has quit [Remote host closed the connection]
14:45 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
15:01 < az0re> On the 1ml node explorer, I see these columns for channel details: Alias, Capacity, Time Lock Delta, Min HTLC, Base Fee, Fee Rate.
15:03 < az0re> Can someone please explain to me what are Time Lock Delta and Min HTLC?  For my own channels/peers, I see the JSON fields for different things like max_htlc_value_in_flight_msat, but it's not clear to me how that's related (or if anything I see in `listpeers` output is related) to these columns in the 1ml node explorer channel details
15:09 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
15:18 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
15:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
16:01 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
16:24 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
16:40 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
16:41 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
17:38 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit]
17:39 -!- qubenix [~qubenix@66.172.11.228] has joined #c-lightning
17:49 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: Leaving]
18:14 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
18:28 < az0re> Another question: When opening a channel, I get "local/remote feerates are too different: remoteFeeratePerKw=253 localFeeratePerKw=20015".  I explicitly set the fee rate to 253perkw, but I get the same error message.  What's going on?
18:55 < az0re> I guess the `fundchannel` plugin only sets the `feerate` field in some JSON request it sends to bcli, which presumably refers to the fee rate used for the funding tx.  But that error comes from a disparity in fee rates for the closing transaction; a failure in negotiation between that node and mine.
18:55 < az0re> Does that mean there is actually no way for me to control (via lightning-cli) the closing tx fee rate parameters?
18:58 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
18:59 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
20:44 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 244 seconds]
20:44 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 244 seconds]
20:45 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Ping timeout: 244 seconds]
20:45 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
20:46 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Ping timeout: 244 seconds]
20:49 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning
20:50 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning
21:52 < az0re> s/closing/commitment/g
22:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
23:09 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds]
23:09 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
23:38 -!- grubles [~unknown@unaffiliated/grubles] has quit [Ping timeout: 240 seconds]
23:48 -!- Netsplit *.net <-> *.split quits: paultroon, ixaeon
23:48 -!- Netsplit *.net <-> *.split quits: mrostecki, k3tan, az0re, kristapsk, ghost43, vasild, jb55, Dean_Guss
23:52 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 240 seconds]
23:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
--- Log closed Sun Sep 13 00:00:17 2020