I’ve seen that installing both Core and Knots on your nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll can cause issues.
Is the same true of Core Lightning and LND? I see LND is an optional dependency for the self-hosted nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm Hub, so I’m just not certain what to run.
Also, what makes a dependency “optional” and what is the best practice there?
It’s downright incredible how easy #start9 makes it to level up your sovereign stack from like 25 to 95. Your own node(s)… self-hosted cloud storage, RoboSats, Nostr Relay, SimpleX, password manager, mempool, Jam conjoins, and the list goes on…
Did I read that joinmarket transactions don’t actually look like coinjoins the way whirlpool does?)
I have much to learn. I love that.
#asknostr #plebchain
Replies (13)
I’m running both LND and Core with no issues. As for Core and Knots, I’m not aware that you can run both at the same time.
If you have Core installed and go to install Knots, it will replace Core. Same thing the other direction. Doesn't have to re-download the blockchain or anything.
Moreover, any app I have tried that has Core as a dependency will work with Knots, too. Knots is based on Core and just has more configuration options.
LND and Core Lightning are very different implementations of Lightning. Other apps with them as a dependency will typically be built to work with one or the other.
The reason Alby Hub has LND only as an optional dependency is because Alby Hub can run on its own without an existing LND node. Alby Hub has LND built in and can therefore be its own Lightning node.
That said, I recommend using LND + Alby Hub for the most versatility, and so you can manage your node using other apps like Ride the Lightning or Thunderhub, too.
Do you mean Bitcoin Core + LND, or Core Lightning + LND?
My (limited) understanding is that running both bitcoin core + knots can cause issues for services that rely on the node as a dependency, since they share the historical timechain database.. something like that!
There's no issue with running both Core Lightning and LND. I am doing so myself. I have my LND node as my main node with a few channels and it has a channel to my CLN node so I can receive Lightning payouts from OCEAN.
I realized I wasn’t clear after reading my original response. I run a LND Node and a Core Lightning Node on the same box with no uses.
I didn’t know you could run BTC Core and Knots on the same box. It is my understanding that nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll has trouble differentiating the two (for selecting the icon) because Knots is a fork of BTC Core.
Yep. No Bolt-12 on LND and OCEAN needs Bolt-12 to work.
Are you able to receive ocean payouts to your cln with just one channel to your LND node? private or public channel?
Yes, I am able to receive just fine with only the one channel to my LND node. My LND node is well connected, so my CLN node doesn't need anything more than the one channel. I do believe it is a public channel, but even that shouldn't matter. The Bolt-12 offer has routing hints.
Very cool setup, nice work 🤙
Alby Hub supports different lightning backends. The default integrated version is based on LDK. LND is another option.
In the default Alby Hub (LDK) we we can offer automated backups and it is very resource efficient for your hardware.
You can run LND and CLN together, not problem. Recommended in fact :)
