This version of Lightning Terminal (LiT) includes lnd v0.21.1-beta, tapd v0.8.0, loop v0.33.3-beta and pool v0.7.1-beta. This release also introduces native SQL database backend support for LiT, and adds support for migrating legacy bbolt database backends to sql.

Action required: Database Migration

This release contains a sensitive database migration from bbolt to SQL-based database backends. It has been extensively tested and while it is recommended for all users, the migration requires your explicit approval or disapproval.

To continue with the migration:

When starting LiT you may input yes via stdin where available or
Add auto-migrate-to-sql=true to your lit.conf or
Set the following environment variable: LIT_AUTO_MIGRATE_TO_SQL=true

Important note: Once the migration has run successfully, the existing bbolt database becomes incompatible with LiT. After this, it will not be possible to downgrade LiT to a version prior to v0.17.0-alpha or migrate back.

To defer the migration:

You may opt to not run or defer the database migration by setting databasebackend=bbolt in your lit.conf

Important note: With this release (v0.17.0-alpha) bbolt support will be considered deprecated. Eventually support for bbolt will be removed from LiT, and the migration will become mandatory.

We'll be continuously working to improve the user experience based on feedback from the community.

Installation and configuration instructions can be found in the README.

This release packages LND v0.21.1-beta, Taproot Assets Daemon v0.8.0, Loop v0.33.3-beta, Pool v0.7.1-beta and Faraday v0.2.16-alpha.

IMPORTANT NOTE: Read the Operational Safety Guidelines before before using Taproot Assets on mainnet!

Breaking changes (from v0.14.x to v0.17.x)

After successfully migrating an existing bbolt database to SQL, you will no longer be able to downgrade LiT to a version before v0.17.0-alpha. An existing SQL database can also not be used with any LiT version prior to v0.17.0-alpha.

There are no breaking changes between litd v0.14.1-alpha and v0.17.0-alpha that prevents upgrading LiT from litd v0.14.1-alpha to v0.17.0-alpha.
If you are upgrading from an older version than litd v0.14.1-alpha, please carefully read the release notes of litd v0.14.1-alpha.

Important note for Umbrel/Lightning Terminal users

DO NOT UNDER ANY CIRCUMSTANCE uninstall (or re-install) the "Lightning Terminal" app without first making a manual backup of all local tapd data, if you are using Taproot Assets as part of the "Lightning Terminal" app with Umbrel -- or any comparable node-in-a-box solution. Uninstalling Umbrel apps deletes application data. This Taproot Assets application data encumbers Taproot Assets AND bitcoin funds. Receiving and sending tapd assets updates the daemon's funds-custody material. Merely having the lnd seed phrase is NOT enough to restore assets minted or received. WITHOUT BACKUP BEFORE DELETION, FUNDS ARE DESTROYED.

`lnd` in remote mode (`lnd-mode=remote`)

NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.19.0-beta.

Required changes when running in `lnd` remote mode

When connecting to an existing lnd node, that node must enable the RPC middleware interceptor feature. You can enable that by specifying the --rpcmiddleware.enable command line flag or by adding rpcmiddleware.enable=true to your lnd.conf file. See the remote configuration docs for more information.

NOTE: Taproot Assets Channel functionality is only available when both lnd
and tapd are running in the same process (by setting both lnd-mode=integrated and taproot-assets-mode=integrated). Remote mode support will be available in the future.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import ViktorT-11's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys C20A78516A0944900EBFCA29961CC8259AE675D4

Once you have his PGP key you can verify the release (assuming manifest-ViktorT-11-v0.17.0-alpha.sig and manifest-v0.17.0-alpha.txt are in the current directory) with:

gpg --verify manifest-ViktorT-11-v0.17.0-alpha.sig manifest-v0.17.0-alpha.txt

You should see the following if the verification was successful:

gpg: Signature made Tue Jun 30 20:04:35 2026 CEST
gpg:                using EDDSA key C20A78516A0944900EBFCA29961CC8259AE675D4
gpg: Good signature from "Viktor Torstensson <viktor.t.git@gmail.com>" [ultimate]

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.17.0-alpha.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.17.0-alpha