oceanslim Roland replied below.

Moritz I think I see. We need some changes to config to add the env variable needed for CLN, then in lnclient we need a cln package and with a wrapper for albyhub can pass cln commands. Is there anything else I would need to look at? You can reach me quicker on nostr oceanslim@happytavern.co or on github @0ceanslim

oceanslim you need to create another implementation of the LNClient interface. How it is implemented internally and whether or not you want to create a wrapper is up to you. You can look at the other implementations for reference. LND might be a good reference since it similarly connects to an external node, however please note LDK is the default and most complete implementation.

Definitely bigger than many people think :-)
Lightweight modular code in C and BOLT 12 invoices...

jakub Yeah, CLN has great features.
I am looking for sound estimations.

Moritz Ok. It is not easy to recognize the LN node implementation from the LN protocol. The studies that have looked into this have been based on setting some node parameters and comparing them with the default values of each implementation.

I quickly googled for example this article:

https://stacker.news/items/97320

So there is a certain amount of inaccuracy in this, but it mostly states LND above 90% and CLN within 7-8%. For some 15k nodes in the network, the CLN is about 1000.