New in this version of Lightning Terminal (LiT) : taproot-assets v0.8.4.

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.3-beta, Taproot Assets Daemon v0.8.4, Loop v0.35.0-beta, Pool v0.7.1-beta and Faraday v0.2.19-alpha.

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

Database Migration: Action required for users upgrading from 0.16.1 and earlier

A sensitive database migration from bbolt to SQL-based database backends has been included in all releases since v0.17.0-alpha. 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 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.

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.5-alpha that prevents upgrading LiT from litd v0.14.1-alpha to v0.17.5-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.5-alpha.sig and manifest-v0.17.5-alpha.txt are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: Signature made Thu Sep 17 01:44:58 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.5-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.5-alpha

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-ViktorT-11-v0.17.5-alpha.sig.ots.

Assuming you have the OpenTimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-ViktorT-11-v0.17.5-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.5.md

New in this version of Lightning Terminal (LiT) : lnd v0.21.3-beta, taproot-assets v0.8.3 and faraday v0.2.19-alpha.

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.3-beta, Taproot Assets Daemon v0.8.3, Loop v0.35.0-beta, Pool v0.7.1-beta and Faraday v0.2.19-alpha.

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

Database Migration: Action required for users upgrading from 0.16.1 and earlier

A sensitive database migration from bbolt to SQL-based database backends has been included in all releases since v0.17.0-alpha. 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 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.

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.4-alpha that prevents upgrading LiT from litd v0.14.1-alpha to v0.17.4-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.4-alpha.sig and manifest-v0.17.4-alpha.txt are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: Signature made Thu Sep  3 18:00:28 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.4-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.4-alpha

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-ViktorT-11-v0.17.4-alpha.sig.ots.

Assuming you have the OpenTimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-ViktorT-11-v0.17.4-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.4.md

New in this version of Lightning Terminal (LiT) : loop v0.35.0-beta and faraday v0.2.18-alpha.

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.2-beta, Taproot Assets Daemon v0.8.1, Loop v0.35.0-beta, Pool v0.7.1-beta and Faraday v0.2.18-alpha.

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

Database Migration: Action required for users upgrading from 0.16.1 and earlier

A sensitive database migration from bbolt to SQL-based database backends has been included in all releases since v0.17.0-alpha. 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 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.

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.3-alpha that prevents upgrading LiT from litd v0.14.1-alpha to v0.17.3-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.3-alpha.sig and manifest-v0.17.3-alpha.txt are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: Signature made Fri Aug 28 00:15:55 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.3-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.3-alpha

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-ViktorT-11-v0.17.3-alpha.sig.ots.

Assuming you have the OpenTimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-ViktorT-11-v0.17.3-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.3.md

lightning-terminal v0.17.2-alpha-docker

This version of Lightning Terminal (LiT) ships taproot-assets v0.8.1 and loop v0.34.0-beta-v0.8.1-tapd. This version also includes a bug fix for an issue that caused litd to error during startup when used in combination with large lnd nodes in the previous release.

Action required: Database Migration

The previous 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 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.2-beta, Taproot Assets Daemon v0.8.1, Loop v0.34.0-beta-v0.8.1-tapd, 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.2-alpha that prevents upgrading LiT from litd v0.14.1-alpha to v0.17.2-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.2-alpha.sig and manifest-v0.17.2-alpha.txt are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: Signature made Wed Aug 19 11:13:49 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.2-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.2-alpha

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-ViktorT-11-v0.17.2-alpha.sig.ots.

Assuming you have the OpenTimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-ViktorT-11-v0.17.2-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.2.md

This version of Lightning Terminal (LiT) includes lnd v0.21.2-beta and loop v0.34.0-beta.

Action required: Database Migration

The previous 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 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.2-beta, Taproot Assets Daemon v0.8.0, Loop v0.34.0-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.1-alpha that prevents upgrading LiT from litd v0.14.1-alpha to v0.17.1-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.1-alpha.sig and manifest-v0.17.1-alpha.txt are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: Signature made Fri Aug 14 01:50:11 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.1-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.1-alpha

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-ViktorT-11-v0.17.1-alpha.sig.ots.

Assuming you have the OpenTimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-ViktorT-11-v0.17.1-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.1.md

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

Database Migration

• IMPORTANT NOTE: If not explicitly configured, LiT will by default initiate the process of migrating existing bbolt database backends to sql on the startup of LiT. Once the SQL migration completes successfully the old bbolt database is tombstoned, meaning that the database becomes incompatible with LiT. This also means that you will no longer be able to downgrade LiT to a version prior to when SQL was supported, which was in this release (v0.17.0-alpha). Bbolt is now officially deprecated, and once support for bbolt is removed in a future release, the migration to SQL will become mandatory.

To choose which database backend to use, a new databasebackend config option has been added. For SQL database backends, SQLite (databasebackend=sqlite) or Postgres (databasebackend=postgres) are supported. If the config option is not set, the database backend defaults to SQLite. Users that explicitly want to continue using the legacy bbolt backend must therefore set databasebackend=bbolt before the SQL migration has been applied.

When the SQL migration process is initiated, users will be prompted to explicitly confirm the execution of the migration by inputting "yes" via stdin. For non-interactive startup flows, this prompt can be skipped by setting the auto-migrate-to-sql=true config flag or by setting the following environment variable: LIT_AUTO_MIGRATE_TO_SQL=true. If the prompt is skipped, the migration will be automatically confirmed and executed.

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.0-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: To avoid loss of funds**, it's imperative that you read the Operational Safety Guidelines before before using tapd on mainnet!

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

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.rc1. An existing SQL database can also not be used with any LiT version prior to v0.17.0-alpha.rc1.

There are no breaking changes between litd v0.14.1-alpha and v0.17.0-alpha.rc1 that prevents upgrading LiT from litd v0.14.1-alpha to v0.17.0-alpha.rc1.
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 if you ran litd from the master branch at any point and you run into the following error on startup:
ErrTypeForDecoding want (type: *uint8, length: 1), got (type: *uint8, length: 147)

Then you should revert to the version of litd you ran before, and execute the following commands on that old version before updating to this version:

1. Run lncli querymc > mission_control_backup.json to back up your mission control state.
2. Run lncli resetmc to clear the mission control state in the database.
3. Update lnd and lncli to the new version.
4. (optional) Use lncli loadmc --mcdatapath mission_control_backup.json to restore the backup. Note: This data will not persist across restarts.

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 added 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.rc1.sig and manifest-v0.17.0-alpha.rc1.txt are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: Signature made Tue Jun  9 22:10:31 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.rc1.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.rc1

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-ViktorT-11-v0.17.0-alpha.rc1.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-ViktorT-11-v0.17.0-alpha.rc1.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.0.md

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

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-ViktorT-11-v0.17.0-alpha.sig.ots.

Assuming you have the OpenTimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-ViktorT-11-v0.17.0-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.0.md