Integrating litd

Move LND, Loop, Pool, Taproot Assets and litd all into a single binary: litd in integrated mode.

Litd is most conveniently run in integrated mode, meaning litd, LND, Loop, Pool, Taproot Assets and Faraday are bundled into a single binary, simplifying the process of starting, stopping and upgrading all your Lightning Labs tools.

Whether you have only recently begun running litd or are still considering adding litd to your node, integrating litd is easy and convenient. The process is easily reversible anytime.

Evaluate

First, consider your current node software stack. You are running LND, but are you also running litd, Loop, Pool and Faraday? Would you like to integrate all of these, or only some?

Not integrating a specific service makes sense when you are running custom code or pre-release software, or simply would like to have more granular control over when to upgrade each service.

If you are running pre-release software, please make sure you are not downgrading LND or any other service, as this might cause problems. You can see which software is bundled with the latest release of litd here.

Integrate

• To integrate a service, simply stop litd and the process you are integrating. If you are integrating LND, please stop all processes.

• Next, configure litd to integrate the service, for example by setting lnd-mode=integrated in your lit.conf file, or by passing it as --lnd-mode=integrated at startup. If your .lnd directory, macaroon and TLS certificate are in a non-standard location, don’t forget to specify these as well.

• We will need to migrate the lnd.conf configurations to the lit.conf. To do that, simply copy over all configurations from lnd.conf add them to your lit.conf file, prefixed with lnd. For example, bitcoin.active=1 becomes lnd.bitcoin.active=1

• Finally, start litd with the command litd. This command should start litd and all processes set to integrated mode. All remote processes will have to be started separately.

Interact with your integrated litd

When integrating LND, the service will remain reachable with the same macaroon at the usual port, meaning no adjustments are necessary.

The Loop, Pool and Faraday processes are reachable inside litd at port 8443 using the litd TLS certificate.

Read more: litd Command Line Interface

When running litd in integrated mode, all logs are written to ~/.lnd/logs/bitcoin/mainnet/lnd.log

Remote

It is always possible to go back to remote mode for any of the integrated services. To do this, simply stop the litd process, change its configuration and start the remote services separately before restarting litd in remote mode.