--- Log opened Tue Nov 24 00:00:25 2020 00:34 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 00:42 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 00:48 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 00:55 -!- reallll is now known as belcher 01:37 -!- vasild_ is now known as vasild 02:04 -!- kexkey [~kexkey@static-198-54-132-134.cust.tzulo.com] has quit [Ping timeout: 260 seconds] 02:19 -!- willcl_ark [~quassel@cpc123780-trow7-2-0-cust177.18-1.cable.virginm.net] has quit [Ping timeout: 256 seconds] 02:20 -!- willcl_ark [~quassel@cpc123780-trow7-2-0-cust177.18-1.cable.virginm.net] has joined #c-lightning 02:27 -!- willcl_ark [~quassel@cpc123780-trow7-2-0-cust177.18-1.cable.virginm.net] has quit [Ping timeout: 256 seconds] 02:37 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 244 seconds] 02:43 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #c-lightning 03:06 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 03:14 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #c-lightning 03:16 -!- gb3901 [b905a59d@185.5.165.157] has joined #c-lightning 03:17 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #c-lightning [] 03:17 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning 03:22 < gb3901> hey, is there a way to use Loop out or similar methods to balance a channel with c-lightning? 03:36 < m-schmoock> gb3901: check out these plugins: https://github.com/lightningd/plugins/tree/master/feeadjuster and https://github.com/lightningd/plugins/tree/master/rebalance 03:36 < m-schmoock> first one tries to manage channels so they are more balanced when used for routing 03:36 < m-schmoock> second one can do manual rebalancing 03:37 < gb3901> Thanks, I will check them out. 03:38 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 04:08 < m-schmoock> general question: is it safe to --enable-developer on a mainnet node? (reduced gossip update timer etc) ? 04:55 < m-schmoock> darosior: regarding feeadjuster: should there be a check that prevents the plugin from setting 'too low' or 'too high' fees and limit the extreme values? 04:56 < darosior> Don't think we really need bounds, at least with the current basic formula 05:08 < m-schmoock> Is it save to track the channel balance like here? https://github.com/lightningd/plugins/blob/d55b9a273bf9b6b699413e4add0c5747290b6d50/feeadjuster/feeadjuster.py#L132 or can it happen that we run below zero somehow? If so, our math can be wrong and cause negative fees 05:09 < m-schmoock> what about failed HTLCs? will they always close a channel and we must not care? 05:35 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 05:38 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 05:43 < darosior> I think it is, actually i'm confident it is if lightningd never lies to us :) 05:45 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has quit [Ping timeout: 240 seconds] 05:48 < darosior> Re HTLCs, we don't treat failed ones https://github.com/lightningd/plugins/blob/d55b9a273bf9b6b699413e4add0c5747290b6d50/feeadjuster/feeadjuster.py#L127 05:59 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #c-lightning 06:20 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 06:32 < m-schmoock> darosior: ah okay. So even if that would be a chained hook and a plugin after use 'rejects' it (does that even make sense for a settlement?) we calculate correctly. 06:43 < darosior> This is not a hook, but a notification so no chain. In addition it would be too late 06:44 < m-schmoock> yup, your right 06:44 < m-schmoock> when I see code that is 'tracking' some value and makes assumptions on it later I just think about all the corner cases 06:45 < m-schmoock> because I have seen such things causing problems often enough in my life 07:06 -!- gb3901 [b905a59d@185.5.165.157] has quit [Remote host closed the connection] 07:07 < m-schmoock> *bump* general question: is it safe to --enable-developer on a mainnet node? (reduced gossip update timer etc) ? 07:13 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 07:15 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 08:00 -!- kexkey [~kexkey@static-198-54-132-118.cust.tzulo.com] has joined #c-lightning 08:01 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has quit [Read error: Connection reset by peer] 08:01 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has joined #c-lightning 08:32 -!- vasild_ is now known as vasild 09:06 -!- fiatjaf [~fiatjaf@2804:7f2:2a88:96ec:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 240 seconds] 09:44 -!- willcl_ark [~quassel@cpc123780-trow7-2-0-cust177.18-1.cable.virginm.net] has joined #c-lightning 10:20 <@niftynei> m-schmoock, what do you mean by 'safe'? 10:22 -!- ksedgwic [~ksedgwic@192-184-134-31.fiber.dynamic.sonic.net] has quit [Quit: Lost terminal] 10:29 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 10:49 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 256 seconds] 10:54 -!- ksedgwic [~ksedgwic@192-184-134-31.fiber.dynamic.sonic.net] has joined #c-lightning 10:55 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has joined #c-lightning 10:57 -!- HelloShitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Quit: leaving] 10:58 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 11:02 -!- helloshitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 11:04 -!- helloshitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Client Quit] 11:05 -!- helloshitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 11:15 -!- helloshitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Quit: leaving] 11:15 -!- helloshitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 11:32 -!- fiatjaf [~fiatjaf@2804:7f2:2a88:96ec:ea40:f2ff:fe85:d2dc] has joined #c-lightning 11:35 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 11:43 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #c-lightning [] 11:43 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning 12:29 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 12:31 -!- fiatjaf [~fiatjaf@2804:7f2:2a88:96ec:ea40:f2ff:fe85:d2dc] has quit [Read error: No route to host] 13:34 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection] 13:34 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 13:38 < m-schmoock> niftynei: Im not talking about the additional dev-commands that may be unsafe if used unwisely. I mean if my node repspecting protocol parameters so it does not get blacklisted or something 13:39 < m-schmoock> because im running a dev node on mainnet for years and never thought about this :D 13:47 <@niftynei> Yes it shouldn't change your protocol parameters 13:49 < m-schmoock> thx 14:25 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Quit: Leaving] 14:26 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has joined #c-lightning 14:26 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning 14:26 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection] 14:44 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 14:45 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 15:31 -!- helloshitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Quit: leaving] 15:31 -!- helloshitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 15:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:21 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has quit [Read error: Connection reset by peer] 16:22 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has joined #c-lightning 17:35 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 17:38 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 18:47 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 260 seconds] 19:55 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning 19:57 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds] 20:05 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #c-lightning [] 20:05 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning 20:23 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Ping timeout: 240 seconds] 20:23 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has joined #c-lightning 20:26 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 20:34 -!- qubenix [~qubenix@66.172.11.228] has quit [Ping timeout: 272 seconds] 20:44 -!- qubenix [~qubenix@66.172.11.228] has joined #c-lightning 21:24 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 22:04 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Quit: Leaving] 23:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 256 seconds] 23:39 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 23:44 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds] --- Log closed Wed Nov 25 00:00:26 2020