--- Log opened Sun Feb 02 00:00:26 2020
00:31 -!- PaulTroon [~paultroon@155.254.96.21] has quit [Remote host closed the connection]
00:32 -!- PaulTroon [~paultroon@155.254.96.21] has joined #c-lightning
00:37 -!- PaulTroon [~paultroon@155.254.96.21] has quit [Ping timeout: 265 seconds]
01:26 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined #c-lightning
01:26 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Read error: Connection reset by peer]
01:27 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined #c-lightning
01:46 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz...]
02:49 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
03:03 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined #c-lightning
03:39 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz...]
04:04 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
04:04 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
05:18 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
05:18 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
05:52 -!- PaulTroon [~paultroon@209.95.56.110] has joined #c-lightning
05:56 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
06:47 < m-schmoock> yesterday I got my mobiles channel closed due to   CHANNELD_NORMAL:update_fee 45000 outside range 253-35390   :/  I thought those were resolved by exponetial smoothing.
06:50 < m-schmoock> They happen when both nodes disagree on current onchain fee situation... I checked the timestamp, there were no sudden spike in fees on johoes mempool at least. how can that happen? especially since both my LN nodes are connected to the same BTC node, there shouldnt be any disagreement
06:51 < m-schmoock> eclair_mobile -> eps -> my_btc_node     and clightningd -> my_btc_node
06:51 <@cdecker> m-schmoock: that's really weird, did a block throw off the estimation? But even then the smoothing should prevent this kind of thing, yes
06:51 < m-schmoock> yes, should happen for a single block
06:51 <@cdecker> It'd appear that eclair spiked, while c-lightning smoothed it? That could cause this
06:52 < m-schmoock> is eclair not doing any smoothing?
06:52 < m-schmoock> to be more tolerant for a while
06:54 < m-schmoock> is there a way to track down who send what update_fee. the logs I saw doesnt really help
06:55 < darosior> m-schmoock: It has happened in the past due to bitcoind failing to estimate
06:55 <@cdecker> Well, the log you posted is printed when we try to apply a feerate we got from the peer, so I think it's eclair sending the failing update_fee
06:55 < darosior> Does `bitcoin-cli estimatesmartfee 10` works ?
06:56 < m-schmoock> bitcoin-cli estimatesmartfee 10
06:56 < m-schmoock> { "feerate": 0.00008030, "blocks": 10
06:56 < m-schmoock> (yes)
06:56 < darosior> Arf
06:56 < m-schmoock> but the incident was yesterday
06:57 < darosior> Did you have any trace of fee estimation failure in your logs ? Aren't you in blocksonly ?
06:57 < darosior> You can grep for "failed to estimate"
06:57 < m-schmoock> on my mobile? :D
06:58 < darosior> AH !
06:58 < darosior> ^^
06:58 < m-schmoock> nvm
06:58 < m-schmoock> if it happens more often, we may tell acinq
06:58 < darosior> You running C-lightning on mobile ? I'm very much interested !
06:58 < m-schmoock> just wanted to drop that here
06:58 < m-schmoock> darosior: im running eclair on mobile and clnd on my host
06:58 < darosior> Ah
06:59 < m-schmoock> so actually 2 nodes
06:59 <@cdecker> For these cases it might be good to build a reverse proxy in front of bitcoind that logs RPC calls for forensic analysis :-)
06:59 < m-schmoock> yup
06:59 < m-schmoock> id would be good if I have had this :D
07:00 < m-schmoock> since they were both conencted to the same BTC node, it must have something to do with eclair not smoothing or something
07:00 < m-schmoock> gotta go, cu
07:02 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
07:05 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
07:20 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 245 seconds]
07:24 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
07:58 -!- moneyball [sid299869@gateway/web/irccloud.com/x-nygdhnfgbmhpblqo] has left #c-lightning []
08:20 -!- PaulTroon [~paultroon@209.95.56.110] has quit [Remote host closed the connection]
08:21 -!- PaulTroon [~paultroon@209.95.56.110] has joined #c-lightning
08:26 -!- PaulTroon [~paultroon@209.95.56.110] has quit [Ping timeout: 265 seconds]
09:01 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
09:04 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
09:05 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
09:37 -!- cdecker [~cdecker@mail.snyke.net] has quit [Quit: Bye bye]
09:37 -!- cdecker [~cdecker@mail.snyke.net] has joined #c-lightning
09:37 -!- mode/#c-lightning [+o cdecker] by ChanServ
10:04 -!- Kostenko [~Kostenko@2001:8a0:7281:e100:6b79:8499:c25d:fafd] has quit [Ping timeout: 265 seconds]
10:19 -!- Kostenko [~Kostenko@2001:8a0:7293:8f00:c82d:30c0:f65f:ddff] has joined #c-lightning
11:00 -!- PaulTroon [~paultroon@173.199.80.51] has joined #c-lightning
11:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
11:46 -!- PaulTroon [~paultroon@173.199.80.51] has quit [Ping timeout: 240 seconds]
11:50 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
12:12 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
12:12 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 265 seconds]
12:51 -!- fjahr [sid374480@gateway/web/irccloud.com/x-ycxxkxjyiukxhegd] has quit []
12:51 -!- fjahr [sid374480@gateway/web/irccloud.com/x-efkrfktxtctjelbc] has joined #c-lightning
13:22 -!- midnightmagic is now known as midnight
13:29 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
13:30 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
15:04 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
15:06 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined #c-lightning
15:07 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
15:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
15:14 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
15:14 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
16:31 < fiatjaf> can we have a method for including arbitrary channels in the gossip store?
16:31 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
16:31 < fiatjaf> how terrible is this idea?
16:32 < fiatjaf> specifically I want to experiment with off-protocol ways to transmit data about private channels that can later be used for routing
16:33 < zmnscpxj> They are not private channels, they are unpublished channels, and yes, making unpublished nodes published is always a good idea
16:55 < fiatjaf> so maybe I should create an issue and wait for someone to love it
17:09 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
17:10 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
17:47 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning []
19:02 -!- Amperture [~amp@65.79.129.113] has joined #c-lightning
20:00 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
21:43 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
21:43 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
22:07 -!- Amperture [~amp@65.79.129.113] has quit [Remote host closed the connection]
23:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
23:45 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
--- Log closed Mon Feb 03 00:00:28 2020