bitcoindinstalled, synced on mainnet, and running as a daemon.
bitcoin.conffile has ZMQ publishing turned on.
lndinstance first make sure your remote
lnd.conffile contains the following additional configuration settings:
~/.lnd/data/chain/bitcoin/mainnetdirectory on your remote machine to
/some/folder/with/lnd/data/on your local machine (where you’ll be running LiT):
~/Library/Application Support/Lit/lit.conffile means you do not need to type in the command line arguments every time you start the server. Make sure you don't add any section headers (the lines starting with [ and ending with ], for example [Application Options]) as these don't work with the additional levels of sub configurations.
lit.conffile into your terminal, and fill in the placeholders with your specific information.
lndinstance is running, it's time to get LiT!
faradayfor that matter) is available through the web UI, it will still be necessary to interact with those daemons through the command line.
--networkflag and the
--macaroonpathare implied by looking inside the default directories for that network. Or you specify the
--macaroonpathflags explicitly, then you must not set the
--networkflag. Otherwise, you will get an error like:
[lncli] could not load global options: unable to read macaroon path (check the network setting!): open /Users/<user>/Library/Application Support/Lnd/data/chain/bitcoin/testnet/admin.macaroon: no such file or directory
lnclicommands in the "integrated" mode are the same as if
lndwas running standalone. The
--lnddirflag does not need to be specified as long as it is the default directory (
loopdalso runs on the same gRPC server as
lnd. That's why we have to both specify the
host:portas well as the TLS certificate of
loopdverifies its own macaroon, so we have to specify that one from the
pooldalso runs on the same gRPC server as
lndand we have to specify the
host:portand the TLS certificate of
lndbut use the macaroon from the