layout	title	nav_order
default	Lightning	40

{% include_relative include_deprecated-notice.md %}

Lightning: LND

{: .no_toc }

We set up LND, the Lightning Network Daemon by Lightning Labs{:target="_blank"}.

Installation

The installation of LND is straight-forward, but the application is quite powerful and capable of things not explained here. Check out their Github repository{:target="_blank"} for a wealth of information about their open-source project and Lightning in general.

Download

Download and install LND

$ cd /tmp
$ wget https://github.com/lightningnetwork/lnd/releases/download/v0.13.3-beta/lnd-linux-armv7-v0.13.3-beta.tar.gz
$ wget https://github.com/lightningnetwork/lnd/releases/download/v0.13.3-beta/manifest-v0.13.3-beta.txt
$ wget https://github.com/lightningnetwork/lnd/releases/download/v0.13.3-beta/manifest-roasbeef-v0.13.3-beta.sig
$ wget -O roasbeef.asc https://keybase.io/roasbeef/pgp_keys.asc

$ sha256sum --check manifest-v0.13.3-beta.txt --ignore-missing
> lnd-linux-armv7-v0.13.3-beta.tar.gz: OK

$ gpg ./roasbeef.asc
> pub rsa4096 2019-10-13 [C] E4D85299674B2D31FAA1892E372CBD7633C61696
> uid Olaoluwa Osuntokun <laolu32@gmail.com>

$ gpg --import ./roasbeef.asc
$ gpg --verify manifest-roasbeef-v0.13.3-beta.sig manifest-v0.13.3-beta.txt
>gpg: Signature made Mon 04 Oct 2021 03:20:20 PM GMT
>gpg:                using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
>gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [unknown]
>gpg: WARNING: This key is not certified with a trusted signature!
>gpg:          There is no indication that the signature belongs to the owner.
>Primary key fingerprint: E4D8 5299 674B 2D31 FAA1  892E 372C BD76 33C6 1696
>     Subkey fingerprint: 60A1 FA7D A5BF F08B DCBB  E790 3BBD 59E9 9B28 0306

$ tar -xzf lnd-linux-armv7-v0.13.3-beta.tar.gz
$ sudo install -m 0755 -o root -g root -t /usr/local/bin lnd-linux-armv7-v0.13.3-beta/*
$ lnd --version
> lnd version 0.13.3 commit=v0.13.3-beta

(Warning: the video below is outdated and does not correspond exactly to the commands above)

Configuration

Now that LND is installed, we need to configure it to work with Bitcoin Core and run automatically on startup.

Open a "bitcoin" user session
```
$ sudo su - bitcoin
```

Create the LND working directory and the corresponding symbolic link

$ mkdir /mnt/ext/lnd
$ ln -s /mnt/ext/lnd /home/bitcoin/.lnd
$ ls -la

Create the LND configuration file and paste the following content (adjust to your alias). Save and exit.

$ nano /mnt/ext/lnd/lnd.conf

# RaspiBolt: lnd configuration
# /mnt/ext/lnd/lnd.conf

[Application Options]
alias=YOUR_FANCY_ALIAS
color=#FFFF00
debuglevel=info
maxpendingchannels=5
listen=localhost

# Fee settings - default LND base fee = 1000 (mSat), default LND fee rate = 1 (ppm)
bitcoin.basefee=1000
bitcoin.feerate=1

# Minimum channel size (in satoshis, default is 20,000 sats)
minchansize=100000

# Accept AMP (multi-paths) payments, wumbo channels and do not prevent the creation of anchor channel (default value)
accept-amp=true
protocol.wumbo-channels=true
protocol.no-anchors=false

# Save on closing fees
## The target number of blocks in which a cooperative close initiated by a remote peer should be confirmed (default: 10 blocks).
coop-close-target-confs=24

#########################
# Improve startup speed # (from https://www.lightningnode.info/advanced-tools/lnd.conf by Openoms)
#########################
# If true, we'll attempt to garbage collect canceled invoices upon start.
gc-canceled-invoices-on-startup=true
# If true, we'll delete newly canceled invoices on the fly.
gc-canceled-invoices-on-the-fly=true
# Avoid historical graph data sync
ignore-historical-gossip-filters=1
# Enable free list syncing for the default bbolt database. This will decrease
# start up time, but can result in performance degradation for very large
# databases, and also result in higher memory usage. If "free list corruption"
# is detected, then this flag may resolve things.
sync-freelist=true
# Avoid high startup overhead
# If true, will apply a randomized staggering between 0s and 30s when
# reconnecting to persistent peers on startup. The first 10 reconnections will be
# attempted instantly, regardless of the flag's value
stagger-initial-reconnect=true

########################
# Compact the database # (slightly modified from https://www.lightningnode.info/advanced-tools/lnd.conf by Openoms)
########################
# Can be used on demand by commenting in/out the two options below: it can take several minutes
[bolt]
# Whether the databases used within lnd should automatically be compacted on
# every startup (and if the database has the configured minimum age). This is
# disabled by default because it requires additional disk space to be available
# during the compaction that is freed afterwards. In general compaction leads to
# smaller database files.
db.bolt.auto-compact=true
# How long ago the last compaction of a database file must be for it to be
# considered for auto compaction again. Can be set to 0 to compact on every
# startup. (default: 168h; the time unit must be present, i.e. s, m or h, except for 0)
db.bolt.auto-compact-min-age=168h

[Bitcoin]
bitcoin.active=1
bitcoin.mainnet=1
bitcoin.node=bitcoind

[tor]
tor.active=true
tor.v3=true
tor.streamisolation=true

🔍 more: sample-lnd.conf{:target="_blank"} with all possible options in the LND project repository

(Warning: the video below is outdated and does not correspond exactly to the commands above)

Run LND

Still with user "bitcoin", we first start LND manually to check if everything works fine.

$ lnd

The daemon prints the status information directly to the command line. This means that we cannot use that session without stopping the server. We need to open a second SSH session.

Wallet setup

Start your SSH program (eg. PuTTY) a second time, connect to the Pi and log in as "admin". Commands for the second session start with the prompt $2 (which must not be entered).

Once LND is started, the process waits for us to create the integrated Bitcoin wallet (it does not use the "bitcoind" wallet).

Start a "bitcoin" user session
```
$2 sudo su - bitcoin
```
Create the LND wallet
```
$2 lncli create
```
If you want to create a new wallet, enter your password [C] as wallet password, select n regarding an existing seed and enter the optional password [D] as seed passphrase. A new cipher seed consisting of 24 words is created.

These 24 words, combined with your passphrase (optional password [D]) is all that you need to restore your Bitcoin wallet and all Lighting channels. The current state of your channels, however, cannot be recreated from this seed, this requires a continuous backup and is still under development for LND.

🚨 This information must be kept secret at all times. Write these 24 words down manually on a piece of paper and store it in a safe place. This piece of paper is all an attacker needs to completely empty your wallet! Do not store it on a computer. Do not take a picture with your mobile phone. This information should never be stored anywhere in digital form.

exit "bitcoin" user session
```
$2 exit
```

💡 _In this screencast I use the awesome tmux{:target="blank"} to run multiple Terminal sessions in parallel. But you can just connect to your RaspiBolt with two separate SSH sessions.

Authorization for "admin"

Let's authorize the "admin" user to work with LND using the command line interface lncli. For that to work, we need to copy the Transport Layer Security (TLS) certificate and the permission files (macaroons) to the admin home folder.

Check if the TLS certificates (tls.cert and tls.key) have been created.
```
$2 sudo ls -la /mnt/ext/lnd/
```

Check if the permission files admin.macaroon has been created.

$2 sudo ls -la /home/bitcoin/.lnd/data/chain/bitcoin/mainnet/

Link the LND data directory in the user "admin" home. As a member or the group "bitcoin", admin has read-only access to certain files. We also need to make all directories browsable for the group (with g+X) and allow it to read the admin.macaroon.
```
$2 ln -s /mnt/ext/lnd /home/admin/.lnd
$2 sudo chmod -R g+X /home/admin/.lnd/data/
$2 sudo chmod g+r /home/admin/.lnd/data/chain/bitcoin/mainnet/admin.macaroon
```
Make sure that lncli works by unlocking your wallet (enter password [C] ) and getting some node infos.
```
$2 lncli unlock
```
Check the current state of LND
```
$2 lncli getinfo
```

You can also see the progress of the initial sync of LND with Bitcoin in the first SSH session.

Let's stop the server for the moment and focus on our primary SSH session again.

$2 lncli stop
$2 exit

This should terminate LND "gracefully" in SSH session 1 that can now be used interactively again.

(Warning: the video below is outdated and does not correspond exactly to the commands above)

Autostart on boot

Now, let's set up LND to start automatically on system startup.

Exit the "bitcoin" user session back to "admin"
```
$ exit
```

Create LND systemd unit with the following content. Save and exit.

$ sudo nano /etc/systemd/system/lnd.service

# RaspiBolt: systemd unit for lnd
# /etc/systemd/system/lnd.service

[Unit]
Description=LND Lightning Network Daemon
Wants=bitcoind.service
After=bitcoind.service

[Service]

# Service execution
###################

ExecStart=/usr/local/bin/lnd


# Process management
####################

Type=simple
Restart=always
RestartSec=30
TimeoutSec=240
LimitNOFILE=128000


# Directory creation and permissions
####################################

# Run as bitcoin:bitcoin
User=bitcoin
Group=bitcoin

# /run/lightningd
RuntimeDirectory=lightningd
RuntimeDirectoryMode=0710


# Hardening measures
####################

# Provide a private /tmp and /var/tmp.
PrivateTmp=true

# Mount /usr, /boot/ and /etc read-only for the process.
ProtectSystem=full

# Disallow the process and all of its children to gain
# new privileges through execve().
NoNewPrivileges=true

# Use a new /dev namespace only populated with API pseudo devices
# such as /dev/null, /dev/zero and /dev/random.
PrivateDevices=true

# Deny the creation of writable and executable memory mappings.
MemoryDenyWriteExecute=true


[Install]
WantedBy=multi-user.target

Enable, start and unlock LND

$ sudo systemctl enable lnd
$ sudo systemctl start lnd
$ systemctl status lnd
$ lncli unlock

Now, the daemon information is no longer displayed on the command line but written into the system journal. You can monitor the LND startup progress until it caught up with the testnet blockchain (about 1.3m blocks at the moment). This can take up to 2 hours, after that you see a lot of very fast chatter (exit with Ctrl-C).
```
$ sudo journalctl -f -u lnd
```

LND in action

Now your Lightning node is ready. This is also the point of no return. Up until now, you can just start over. Once you send real bitcoin to your RaspiBolt, you have "skin in the game".

Make sure your RaspiBolt is working as expected.
Get a little practice with bitcoin-cli and its options (see Bitcoin Core RPC documentation{:target="_blank"})
Try a few restarts (first stop lnd and bitcoind with lncli stop, sudo systemctl stop lnd, sudo systemctl stop bitcoind and then reboot with sudo reboot), is everything starting fine (don't forget to unlock the wallet after each reboot with lncli unlock)?

Funding your Lightning node

Generate a new Bitcoin address (p2wkh = native SegWit/Bech32) to receive funds on-chain and send a small amount of Bitcoin to it from any wallet of your choice. 🕮 newaddress{:target="_blank"}
```
$ lncli newaddress p2wkh
> "address": "bc1..."
```

Check your LND wallet balance 🕮 walletbalance{:target="_blank"}

$ lncli walletbalance
{
    "total_balance": "712345",
    "confirmed_balance": "0",
    "unconfirmed_balance": "712345"
}

As soon as your funding transaction is mined (1 confirmation), LND will show its amount as "confirmed_balance".

💡 If you want to open a few channels, you might want to send a few transactions. If you have only one UTXO, you need to wait for the change to return to your wallet after every new channel opening.

(Warning: the video below is outdated and does not correspond exactly to the commands above)

Opening channels

Although LND features an optional "autopilot", we manually open some channels. I recommend to go on Amboss.Space{:target="_blank"} or 1ML.com{:target="_blank"} and look for a mix of big and small nodes with decent Node Ranks.

To connect to a remote node, you need its URI that looks like <pubkey>@host:

the <pubkey> is just a long hexadecimal number, like 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f
the host can be a domain name, an ip address or a Tor onion address, followed by the port number (usually :9735)

Just grab the whole URI above the big QR code and use it as follows (we will use the ACINQ node as an example):

Connect to the remote node, with the full URI. 🕮 connect{:target="_blank"}

$ lncli connect 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@34.239.230.56:9735

Open a channel using the <pubkey> and the channel capacity in satoshis. 🕮 openchannel{:target="_blank"}

One Bitcoin equals 100 million satoshis, so at $10'000/BTC, $10 amount to 0.001 BTC or 100'000 satoshis. To avoid mistakes, you can just use an online converter.

The command as a built-in fee estimator, but to avoid overpaying fees, you can manually control the fees for the funding transaction by using the sat_per_byte argument as follows (to select the appropriate fee, in sats/vB, check mempool.space{:target="_blank"})
```
$ lncli openchannel --sat_per_vbyte 8 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f 100000 0
```
Check your funds, both in the on-chain wallet and the channel balances. 🕮 walletbalance{:target="_blank"} 🕮 channelbalance{:target="_blank"}
```
$ lncli walletbalance
$ lncli channelbalance
```
List active channels. Once the channel funding transaction has been mined and gained enough confirmations, your channel is fully operational. That can take an hour or more. 🕮 listchannels{:target="_blank"}
```
$ lncli listchannels
```
Make a Lightning payment. These work with invoices, so everytime you buy something or want to send money, you need to get an invoice first. To try, why not send me a single satoshi to view my Twitter profile?
- Click on this paywall link: https://paywall.link/to/468ad
- Click on "Manual Payment Information" and copy the Invoice.
- Pay me 1 satoshi (~ $0.0001) 🤑
```
* lncli payinvoice lnbc10n1pw......................gsj59
```

(Warning: the video below is outdated and does not correspond exactly to the commands above)

More commands

A quick reference with common commands to play around with:

list all arguments for the CLI (command line interface)
```
$ lncli
```
get help for a specific command
```
$ lncli help [COMMAND]
```
Find out some general stats about your node: 🕮 getinfo{:target="_blank"}
```
$ lncli getinfo
```
Check the peers you are currently connected to: 🕮 listpeers{:target="_blank"}
```
$ lncli listpeers
```
Check the status of your pending channels: 🕮 pendingchannels{:target="_blank"}
```
$ lncli pendingchannels
```
Check the status of your active channels: 🕮 listchannels{:target="_blank"}
```
$ lncli listchannels
```
Before paying an invoice, you should decode it to check if the amount and other infos are correct: 🕮 decodepayreq{:target="_blank"}
```
$ lncli decodepayreq [INVOICE]
```
Pay an invoice:
```
$ lncli payinvoice [INVOICE]
```
Send a payment to a node without invoice using AMP (both sender and receiver nodes have to have AMP enabled): 􀀁 sendpayment{:target="_blank"}
```
$ lncli sendpayment --amp --fee_limit 1 --dest=<node_pubkey> --final_cltv_delta=144 --amt=<amount_in_sats>
```
Check the payments that you sent: 🕮 listpayments{:target="_blank"}
```
$ lncli listpayments
```
Create an invoice: 🕮 addinvoice{:target="_blank"}
```
$ lncli addinvoice [AMOUNT_IN_SATOSHIS]
```
List all invoices: 🕮 listinvoices{:target="_blank"}
```
$ lncli listinvoices
```
to close a channel, you need the following two arguments that can be determined with listchannels and are listed as "channelpoint": FUNDING_TXID:OUTPUT_INDEX 🕮 closechannel{:target="_blank"}
```
$ lncli listchannels
$ lncli closechannel --sat_per_vbyte <fee> [FUNDING_TXID] [OUTPUT_INDEX]
```
to force close a channel (if your peer is offline or not cooperative), use --force
```
$ lncli closechannel --force [FUNDING_TXID] [OUTPUT_INDEX]
```

🔍 more: full LND API reference

LND upgrade

If you want to upgrade to a new release of LND in the future, check out the FAQ section: How to upgrade LND

Optional: Using LiT (Lightning Terminal) instead of LND

LiT is a software suite of Lightning Labs which contains LND, Faraday (accounting service), Loop (client software for submarine swaps with LOOP node of Lightning Labs) and Pool (client software to submit orders to buy and sell inbound liquidity through unique price auction at each new block found). LiT provides a user interface to make submarine swap easily, it now also features a UI for Pool Market which is a good tool to estimate the price of liquidity.

Because Pool is alpha software, LiT is alpha software too. The LND part is however in beta and the behavior is exactly the same as LND.

You cannot run LiT and LND at the same time.

The Lightning Terminal UI requires a password. Select a new password:

[ E ] Master user password

Download LiT

Download and install LiT

$ cd /tmp
$ wget https://github.com/lightninglabs/lightning-terminal/releases/download/v0.5.0-alpha/lightning-terminal-linux-armv7-v0.5.0-alpha.tar.gz
$ wget https://github.com/lightninglabs/lightning-terminal/releases/download/v0.5.0-alpha/manifest-v0.5.0-alpha.txt
$ wget https://github.com/lightninglabs/lightning-terminal/releases/download/v0.5.0-alpha/manifest-roasbeef-v0.5.0-alpha.sig
$ wget https://keybase.io/roasbeef/pgp_keys.asc

$ sha256sum --check manifest-v0.5.0-alpha.txt --ignore-missing
> lightning-terminal-linux-armv7-v0.5.0-alpha.tar.gz: OK

$ gpg ./pgp_keys.asc
> E4D85299674B2D31FAA1892E372CBD7633C61696

$ gpg --import ./pgp_keys.asc
$ gpg --verify manifest-roasbeef-v0.5.0-alpha.sig manifest-v0.5.0-alpha.txt
> gpg: Signature made Tue 22 Jun 2021 00:14:50 CEST
> gpg:                using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
> gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:          There is no indication that the signature belongs to the owner.
> Primary key fingerprint: E4D8 5299 674B 2D31 FAA1  892E 372C BD76 33C6 1696
>      Subkey fingerprint: 60A1 FA7D A5BF F08B DCBB  E790 3BBD 59E9 9B28 0306

$ tar -xzf lightning-terminal-linux-armv7-v0.5.0-alpha.tar.gz
$ sudo install -m 0755 -o root -g root -t /usr/local/bin lightning-terminal-linux-armv7-v0.5.0-alpha/*
$ litd --lnd.version
> litd version 0.13.0-beta commit=lightning-terminal-v0.5.0-alpha

Configuration

LiT has its own configuration file. The settings for LND, Pool, Faraday, Loop can all be put in the LiT configuration file

Open a "bitcoin" user session
```
$ sudo su - bitcoin
```
Create the LiT working directory
```
$ mkdir /home/bitcoin/.lit
```

Create the LiT configuration file and paste the following content (adjust to your alias and paste password [B] as required in the Faraday section). Save and exit.

$ nano lit.conf

# RaspiBolt: lit configuration
# /home/bitcoin/.lit/lit.conf

# Feel free to change this IP depending of you need to access the UI
# If you want the UI to be available ONLY from your home network,
# replace 0.0.0.0 by the local IP of the RaspiBolt
# 0.0.0.0 let you access the UI from anywhere
httpslisten=0.0.0.0:8443

# Your password for the UI must be at least 8 characters long

uipassword=PASSWORD_[E]
lnd-mode=integrated

# LND settings
# [Application Options]
lnd.lnddir=/mnt/ext/lnd
lnd.alias=YOUR_FANCY_ALIAS
lnd.color=#FFFF00
lnd.debuglevel=info
lnd.maxpendingchannels=5
lnd.listen=localhost

# Fee settings - default LND base fee = 1000 (mSat), default LND fee rate = 1 (ppm)
lnd.bitcoin.basefee=1000
lnd.bitcoin.feerate=10

# Minimum channel size (in satoshis, default is 20,000 sats)
lnd.minchansize=100000

# Accept AMP (multi-paths) payments, wumbo channels and do not prevent the creation of anchor channel (default value)
lnd.accept-amp=true
lnd.protocol.wumbo-channels=true
lnd.protocol.no-anchors=false

# Save on closing fees
## The target number of blocks in which a cooperative close initiated by a remote peer should be confirmed (default: 10 blocks).
lnd.coop-close-target-confs=24

#########################
# Improve startup speed # (from https://www.lightningnode.info/advanced-tools/lnd.conf by Openoms)
#########################
# If true, we'll attempt to garbage collect canceled invoices upon start.
lnd.gc-canceled-invoices-on-startup=true
# If true, we'll delete newly canceled invoices on the fly.
lnd.gc-canceled-invoices-on-the-fly=true
# Avoid historical graph data sync
lnd.ignore-historical-gossip-filters=1
# Enable free list syncing for the default bbolt database. This will decrease
# start up time, but can result in performance degradation for very large
# databases, and also result in higher memory usage. If "free list corruption"
# is detected, then this flag may resolve things.
lnd.sync-freelist=true
# Avoid high startup overhead
# If true, will apply a randomized staggering between 0s and 30s when
# reconnecting to persistent peers on startup. The first 10 reconnections will be
# attempted instantly, regardless of the flag's value
lnd.stagger-initial-reconnect=true

########################
# Compact the database # (slightly modified from https://www.lightningnode.info/advanced-tools/lnd.conf by Openoms)
########################
# Can be used on demand by commenting in/out the two options below: it can take several minutes
# [bolt]
# Whether the databases used within lnd should automatically be compacted on
# every startup (and if the database has the configured minimum age). This is
# disabled by default because it requires additional disk space to be available
# during the compaction that is freed afterwards. In general compaction leads to
# smaller database files.
lnd.db.bolt.auto-compact=true
# How long ago the last compaction of a database file must be for it to be
# considered for auto compaction again. Can be set to 0 to compact on every
# startup. (default: 168h; the time unit must be present, i.e. s, m or h, except for 0)
lnd.db.bolt.auto-compact-min-age=168h

# [Bitcoin]
lnd.bitcoin.active=1
lnd.bitcoin.mainnet=1
lnd.bitcoin.node=bitcoind

# [tor]
lnd.tor.active=true
lnd.tor.v3=true
lnd.tor.streamisolation=true

#################
# Pool settings #
#################
# This option avoids the creation of channels with nodes with whom you already have a channel (set to 0 if you don't mind)
pool.newnodesonly=1

####################
# Faraday settings #
####################
# If connect_bitcoin is set to 1, Faraday can connect to a bitcoin node (with --txindex set) to provide node accounting services
faraday.connect_bitcoin=1
# The Bitcoin node IP is the IP address of the Raspibolt, i.e. an address like 192.168.0.20
faraday.bitcoin.host=[Bitcoin node IP]:8332
# bitcoin.user provides to Faraday the bicoind RPC username, as specified in our bitcoin.conf
faraday.bitcoin.user=raspibolt
# bitcoin.password provides to Faraday the bitcoind RPC password, as specified in our bitcoin.conf
faraday.bitcoin.password=PASSWORD_[B]

🔍 Notice that the options for LND, Faraday, Loop and Pool can be set in this configuration file but you must prefix the software with a dot as we made here. Use samples configuration files shown in github repo of each software for more options

Running LiT

Start your SSH program (eg. PuTTY) a second time, connect to the Pi and log in as “admin”. Commands for the second session start with the prompt $2 (which must not be entered). We must never run LND and LiT at the same time to avoid corruption of the channels database. So we must first stop LND and its systemd service.

$2 lncli stop
$2 sudo systemctl stop lnd

Once everything is stopped, we can test that LiT is correctly using the LND database.

$2 sudo su - bitcoin
$2 litd

Now go back to the first session and try to unlock your wallet, if you already used your node a lot you must wait for the LND database to be open (you can take a look at the log returned in the second session where LiT is running).

$ lncli unlock

Type your password [C] to unlock the wallet. You can check the state with lncli getinfo, it should be synced with graph and chain. If it works, you can stop LiT running in the second section using Ctrl + C and exit it

$2 exit

Autostart LiT on boot

We stopped lnd service, now that LiT is running we can replace the autostart service for LND by the LiT's one. We modify LND systemd unit:

$2 sudo systemctl disable lnd
$2 sudo nano /etc/systemd/system/lnd.service

We can just change the line ExecStart=/usr/local/bin/lnd for ExecStart=/usr/local/bin/litd, rename the file and enable, start, unlock LiT:

$2 sudo mv /etc/systemd/system/lnd.service /etc/systemd/system/litd.service
$2 sudo systemctl enable litd
$2 sudo systemctl start litd
$2 systemctl status litd
$2 lncli unlock

If you wish to look at the daemon information, they are in the system journal

$2 sudo journalctl -f -u litd

Using other software packaged in LiT

Others softwares have their own macaroon files too, they are created in .loop, .faraday and .pool directories of bitcoin home by default. So we create symbolic link so that admin user can use them.

$2 ln -s /home/bitcoin/.loop /home/admin/.loop
$2 ln -s /home/bitcoin/.pool /home/admin/.pool
$2 ln -s /home/bitcoin/.faraday /home/admin/.faraday

For now, softwares packaged in LiT are all listening to the same port 10009 as LND. This is not the default behavior set in the code of these sofware so you must always indicate the RPC port when using them.

For example, the following will not work to look at the last auction snapshot:

$2 pool auction snapshot

It will returns the following error:

> [pool] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp [::1]:12010: connect: connection refused"

It says that the pool command try to interact with your pool client on localhost's port 12010. However your instance of Pool is not listening to the default port 12010, but port 10009 ! It also needs to know where the TLS certificate to securely interact with LND is.

That's why this will work:

$2 pool --rpcserver=localhost:10009 --tlscertpath=~/.lnd/tls.cert auction snapshot

It can be convenient to create alias to not have to type the rpc server address at every command. Use alias command in bash for that

$2 alias poolit="pool --rpcserver=localhost:10009 --tlscertpath=~/.lnd/tls.cert"
$2 poolit auction snapshot

You can add your aliases in .bashrc file of admin

$2 nano ~/.bashrc

Add the following at the end of the file then save and exit:

$2 alias poolit="pool --rpcserver=localhost:10009 --tlscertpath=~/.lnd/tls.cert"
$2 alias loopit="loop --rpcserver=localhost:10009 --tlscertpath=~/.lnd/tls.cert"
$2 alias frclit="frcli --rpcserver=localhost:10009 --tlscertpath=~/.lnd/tls.cert"

Use help and documentation on Pool, Loop and Faraday respectively for information on these command.

Access LiT UI for easy Loop Out/In and Liquidity trading

LiT provides a UI that allows you to use Loop and Pool conveniently. The UI is running on port 8443. To access it you must be in your home network (or connected through a VPN like WireGuard) and ufw should allow access to the port 8443:

$2 sudo su
# ufw allow 8443 comment 'allow LiT UI'
# ufw disable
# ufw enable
# exit

You can now connect from your home to https://[your_pi_local_ip]:8443 with your browser and enjoy the nice GUI of LiT ! Use PASSWORD_[B] to log in.

LiT upgrade

Open a session with "admin". You must stop LiT with lncli stop then sudo systemctl stop litd before upgrading !

Proceed as LND, but use the binaries of the LiT repo and do not delete the LND macaroons. Replace wget https://github.com/lightningnetwork/lnd by wget https://github.com/lightninglabs/lightning-terminal when downloading binaries and check signature as the "download" part of this guide.

Next: Electrum >>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

raspibolt_40_lnd.md

raspibolt_40_lnd.md

Lightning: LND

Table of contents

Installation

Download

Configuration

Run LND

Wallet setup

Authorization for "admin"

Autostart on boot

LND in action

Funding your Lightning node

Opening channels

More commands

LND upgrade

Optional: Using LiT (Lightning Terminal) instead of LND

Download LiT

Configuration

Running LiT

Autostart LiT on boot

Using other software packaged in LiT

Access LiT UI for easy Loop Out/In and Liquidity trading

LiT upgrade

Files

raspibolt_40_lnd.md

Latest commit

History

raspibolt_40_lnd.md

File metadata and controls

Lightning: LND

Table of contents

Installation

Download

Configuration

Run LND

Wallet setup

Authorization for "admin"

Autostart on boot

LND in action

Funding your Lightning node

Opening channels

More commands

LND upgrade

Optional: Using LiT (Lightning Terminal) instead of LND

Download LiT

Configuration

Running LiT

Autostart LiT on boot

Using other software packaged in LiT

Access LiT UI for easy Loop Out/In and Liquidity trading

LiT upgrade