--- Log opened Mon Jan 03 00:00:19 2022
03:36 -!- opsec_x122 [~opsec_x12@44-25-143-42.ip.hamwan.net] has quit [Remote host closed the connection]
03:36 -!- sr_gi [~sr_gi@static-120-137-229-77.ipcom.comunitel.net] has quit [Ping timeout: 260 seconds]
03:36 -!- opsec_x122 [~opsec_x12@44-25-143-42.ip.hamwan.net] has joined #c-lightning
04:52 -!- jespada [~jespada@87.74.33.157] has quit [Quit: Textual IRC Client: www.textualapp.com]
05:01 -!- kexkey__ [~kexkey@static-198-54-132-158.cust.tzulo.com] has quit [Ping timeout: 260 seconds]
05:02 -!- kexkey [~kexkey@static-198-54-132-126.cust.tzulo.com] has joined #c-lightning
05:08 -!- jespada [~jespada@87.74.33.157] has joined #c-lightning
09:27 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
10:37 -!- jonatack [jonatack@user/jonatack] has joined #c-lightning
10:45 -!- jarthur [~jarthur@2603-8080-1540-002d-b547-ef3f-a0b7-179d.res6.spectrum.com] has joined #c-lightning
10:52 -!- rusty [~rusty@123-243-220-254.tpgi.com.au] has joined #c-lightning
11:36 < plant-boy[m]> Hi, I tried running a LND node, I was surprised to see that it appears to have a better view of the network. I.e., while the LND node lists ~82k channels, the c-lightning one only lists around 79k channels. Is there a natural explanation why LND see ~3000 more channels? And if it is really the case that c-lightning discovers a lot fewer channels, would that not be a problem for routing? 
11:36 < plant-boy[m]> The c-lightning node has way more channels/peers, so connectivity does not seem to be the problem.
11:38 < plant-boy[m]> (c-lightning node has also been running for significantly longer, so it does seem to be a problem that it will "catch up" on)
12:43 -!- rusty [~rusty@123-243-220-254.tpgi.com.au] has quit [Ping timeout: 256 seconds]
12:59 -!- rusty [~rusty@123-243-220-254.tpgi.com.au] has joined #c-lightning
13:51 -!- rusty [~rusty@123-243-220-254.tpgi.com.au] has quit [Ping timeout: 256 seconds]
13:56 -!- jespada [~jespada@87.74.33.157] has quit [Ping timeout: 256 seconds]
13:57 -!- jespada [~jespada@87.74.32.18] has joined #c-lightning
14:01 -!- rusty [~rusty@123-243-220-254.tpgi.com.au] has joined #c-lightning
14:09 -!- rusty [~rusty@123-243-220-254.tpgi.com.au] has quit [Ping timeout: 256 seconds]
14:33 -!- rusty [~rusty@pa49-178-113-171.pa.nsw.optusnet.com.au] has joined #c-lightning
14:39 -!- rusty [~rusty@pa49-178-113-171.pa.nsw.optusnet.com.au] has quit [Read error: Connection reset by peer]
14:56 -!- rusty [~rusty@pa49-178-113-171.pa.nsw.optusnet.com.au] has joined #c-lightning
15:04 -!- rusty [~rusty@pa49-178-113-171.pa.nsw.optusnet.com.au] has quit [Ping timeout: 256 seconds]
15:06 -!- rusty [~rusty@123-243-220-254.tpgi.com.au] has joined #c-lightning
15:07 < willcl_ark> For me `lightning-cli listchannels | jq '.[] | length'` returns ~148k (uni-directional) channels., of which 129k are listed as active and 19k as inactive. So you might have a better view than me :)
15:07 -!- vincenzopalazzo [~vincenzop@2001:470:69fc:105::a67] has joined #c-lightning
15:07 -!- merkle_noob[m] [~merklenoo@2001:470:69fc:105::bad0] has joined #c-lightning
15:07 -!- openoms[m] [~openomsma@2001:470:69fc:105::c2f] has joined #c-lightning
15:07 -!- kon[m] [~konnixbit@2001:470:69fc:105::b9af] has joined #c-lightning
15:07 -!- kakolainen[m] [~kakolaine@2001:470:69fc:105::34f9] has joined #c-lightning
15:07 -!- johncantrell97[m [~johncantr@2001:470:69fc:105::1:3780] has joined #c-lightning
15:07 -!- devrandom [~devrandom@2001:470:69fc:105::d4d] has joined #c-lightning
15:09 < willcl_ark> C-Lightning does not permit multiple parallel channels with a direct peer for various reasons, and I was wondering if that might also extend out into the network graph so that we can only see a single channel between two remote peers -- who actually have many parallel channels -- but I am not sure about that.
15:13 -!- rusty [~rusty@123-243-220-254.tpgi.com.au] has quit [Ping timeout: 256 seconds]
15:29 -!- rusty [~rusty@123-243-220-254.tpgi.com.au] has joined #c-lightning
16:47 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
16:47 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
18:04 -!- An0rak [An0rak@user/an0rak] has joined #c-lightning
20:12 -!- jespada [~jespada@87.74.32.18] has quit [Ping timeout: 240 seconds]
20:15 -!- jespada [~jespada@87.74.32.18] has joined #c-lightning
21:05 -!- jarthur [~jarthur@2603-8080-1540-002d-b547-ef3f-a0b7-179d.res6.spectrum.com] has quit [Quit: jarthur]
23:28 -!- HelloShitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Quit: leaving]
23:33 -!- HelloShitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning
23:44 < cdecker[m]> No, that limitation is a local one only, we do track multiplexed channels correctly, it's just we don't support them locally (yet).
23:44 < cdecker[m]> The difference may come from passive pruning, i.e. cleaning up channels after 2 weeks of activity, depending on when you trigger a cleanup and how strict you are with the 2 weeks you may end up with more or less channels. Either way, they're oldish and haven't shown any activity for weeks, so missing them is unlikely to make a difference in payments 
--- Log closed Tue Jan 04 00:00:20 2022