--- Log opened Fri Nov 20 00:00:22 2020
01:15 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
01:21 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
01:52 -!- jonatack [~jon@213.152.162.79] has quit [Ping timeout: 260 seconds]
02:05 -!- kexkey [~kexkey@static-198-54-132-107.cust.tzulo.com] has quit [Ping timeout: 264 seconds]
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
03:56 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
04:18 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
04:20 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
05:21 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
05:22 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
05:30 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
05:37 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
06:25 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
06:28 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
06:34 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
06:40 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection]
06:45 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
07:26 -!- kexkey [~kexkey@static-198-54-132-139.cust.tzulo.com] has joined #c-lightning
07:56 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
08:01 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #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 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning
08:02 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has joined #c-lightning
08:35 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
08:39 -!- kexkey [~kexkey@static-198-54-132-139.cust.tzulo.com] has quit [Ping timeout: 240 seconds]
08:43 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
09:07 -!- fiatjaf [~fiatjaf@191.30.40.41] has quit [Ping timeout: 240 seconds]
09:09 -!- fiatjaf [~fiatjaf@2804:7f2:2a88:96ec:ea40:f2ff:fe85:d2dc] has joined #c-lightning
09:16 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
10:11 < sr_gi> Is there any easy way of checking how many commitments updates have been in a channel, or to keep track of when something gets routed? Got someone asking me because looks like some recent traffic is not showing on `listforwards`, but not sure if there's any better command :S
10:51 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
10:55 < darosior> sr_gi: listforwards should not (:tm:) be missing any information about routing
10:56 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 265 seconds]
10:57 < sr_gi> He just opened an issue on GH. I went over his node's logs with him and saw that some revocations were being sent/received, which triggered the commitment-revocation hook, but that data was not showing anywhere he could tell 
10:57 < sr_gi> I may have missed something tho :(
10:58 -!- jonatack [~jon@213.152.162.181] has joined #c-lightning
10:58 -!- jonatack [~jon@213.152.162.181] has quit [Client Quit]
10:58 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
11:03 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 240 seconds]
11:04 -!- jonatack [~jon@213.152.162.181] has joined #c-lightning
11:41 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Quit: liberliver]
12:28 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
12:32 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: Leaving]
12:32 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
12:34 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
13:35 < darosior> sr_gi: maybe just an update_fee ?
13:48 -!- belcher_ is now known as belcher
13:59 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
14:14 -!- ksedgwic [~ksedgwic@192-184-134-31.static.sonic.net] has quit [Ping timeout: 260 seconds]
14:14 -!- ksedgwic [~ksedgwic@192-184-134-31.fiber.dynamic.sonic.net] has joined #c-lightning
15:04 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
15:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
16:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:22 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #c-lightning []
16:22 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has quit [Read error: Connection reset by peer]
16:22 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning
16:23 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has joined #c-lightning
16:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]
18:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
18:38 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]
18:42 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
18:43 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
19:54 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
19:57 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds]
23:11 -!- jonatack [~jon@213.152.162.181] has quit [Ping timeout: 260 seconds]
23:13 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
--- Log closed Sat Nov 21 00:00:23 2020