NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #2438 by repository stars
Latest stable
v0.17.10
Last release 17 days ago
05 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 5 of 5 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
562 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
CVE-2026-98432 is a use-after-free in the Linux kernel's IPv4 TCP stack. It is not specific to MPTCP, but the demonstrated remote exploit requires an…
New in this version of Lightning Terminal (LiT) : lnd v0.21.6-beta, taproot-assets v0.8.8, loop v0.35.2-beta, pool v0.7.2-beta and faraday v0.2.20-alpha
NOTE: There was no v0.17.9 release, as lnd v0.21.6-beta was shipped after v0.17.9 had already been tagged, leading to the decision to go straight to v0.17.10 containing lnd v0.21.6-beta.
CVE-2026-98432 is a use-after-free in the Linux kernel's IPv4 TCP stack. It is not specific to MPTCP, but the demonstrated remote exploit requires an MPTCP listener, which Go 1.24+ enables by default. This release disables MPTCP listeners in lnd by default, which closes the demonstrated exploit path through lnd. It is a mitigation, not a fix: the kernel patch is the only fix.
Linux operators should:
sudo sysctl -w net.mptcp.enabled=0), since other services on the machine are not covered by this release.If you cannot upgrade yet, start your existing binary with the environment variable GODEBUG=multipathtcp=0, which turns off Go's default MPTCP listeners. Do not set GODEBUG=multipathtcp=1 to re-enable MPTCP until your kernel is patched. The Go team's discussion of the issue is at golang/go#82717.
See the lnd release notes for the full instructions, including Docker and firewall guidance. Windows and macOS are not affected.
| Component | Version or source revision |
|---|---|
| LND | v0.21.6-beta |
| Loop | v0.35.2-beta |
| Pool | v0.7.2-beta |
| Faraday | v0.2.20-alpha |
| Taproot Assets | v0.8.8 |
Users upgrading from v0.16.1 or earlier must review the
v0.17.0 migration notes
before starting LiT. The first startup with a SQL backend requires explicit
confirmation. For noninteractive deployments, set auto-migrate-to-sql=true
in lit.conf or LIT_AUTO_MIGRATE_TO_SQL=true in the environment. To defer
migration, set databasebackend=bbolt before migration runs. Once migration
completes, the old bbolt database is tombstoned, and a downgrade to a version
before v0.17.0-alpha is unsupported.
Import the release signing key from
https://github.com/lightningnetwork/lnd/blob/master/scripts/keys/ViktorT-11.asc
and verify its fingerprint is
C20A78516A0944900EBFCA29961CC8259AE675D4 . Alternatively, you can
also import ViktorT-11's key from the ubuntu key server:
gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys C20A78516A0944900EBFCA29961CC8259AE675D4
gpg --verify manifest-ViktorT-11-v0.17.10.sig manifest-v0.17.10.txt
shasum -a 256 <downloaded-archive>
git verify-tag v0.17.10
Compare the computed archive hash with its entry in
manifest-v0.17.10.txt. The timestamp proofs
can be verified with:
ots verify manifest-v0.17.10.txt.ots
ots verify manifest-ViktorT-11-v0.17.10.sig.ots
Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s).
The release binaries are compiled with go1.27.3,
which is required by verifiers to arrive at the same ones. They
include the following build tags: litd, autopilotrpc,
signrpc, walletrpc, chainrpc, invoicesrpc,
watchtowerrpc, neutrinorpc, monitoring, peersrpc,
kvdb_postgres, kvdb_etcd and kvdb_sqlite. Note that these
are already included in the release script, so they do not need
to be provided.
The make docker-release tag=<tag> command can be used to
rebuild with the same flags used for the release. If one wishes
to build for only a single platform, then
make docker-release tag=<tag> sys=<OS-ARCH> can be used.
To verify the litd and litcli binaries inside the docker
images against the reproducible release binaries, the manifest
file can be used: extract the image, compute the SHA-256 hash
of the contained binary with shasum -a 256 <filename> and
compare it with the corresponding entry in
manifest-v0.17.10.txt.
https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.10.md
Your coding agent can read these notes before it upgrades. Set up the MCP server →
lightning-terminal v0.17.9
lightning-terminal v0.17.9
Nothing published for this version
Nothing published for this version
In this release, we rebuild Lightning Terminal and its bundled daemons with Go 1.27.3 to address CVE-2026-111943 . Go's crypto/x509 verifier now rejec…
In this release, we rebuild Lightning Terminal and its bundled daemons with Go
1.27.3 to address CVE-2026-111943.
Go's crypto/x509 verifier now rejects certificate chains containing a specific
set of intermediate certificates due to security concerns around their
operation. We recommend that all users upgrade.
This release also fixes integrated sub-server shutdown and SQL error matching,
and updates the bundled LND, Loop, Pool, and Faraday dependencies.
error only through their pointer types,See the release-specific notes
and full changes since v0.17.7.
| Component | Version or source revision |
|---|---|
| LND | v0.21.5-beta.rc1 |
| Loop | 333ed1efccdd |
| Pool | 262af739b741 |
| Faraday | b547baea0f95 |
| Taproot Assets | v0.8.6, unchanged |
Loop, Pool, and Faraday are pinned to public source commits rather than new
standalone release tags. The exact module versions are recorded in
go.mod.
Back up your databases before upgrading. There is no new LiT database schema
migration relative to v0.17.7, and LND v0.21.5-beta.rc1 adds no database
migrations. The bundled Loop update does include a
SQL migration
that adds on-chain cost fields to static-address deposits. Loop applies this
migration when it starts and looks up costs for existing deposits after
upgrading.
Instant Out API callers must now set max_swap_fee_sat; requests that omit
the fee cap are rejected. An explicit zero cap is valid. Review the bundled
Loop v0.35.1 notes
and subsequent Loop changes
for the remaining swap fixes and API changes included in this source revision.
Users upgrading from v0.16.1 or earlier must review the
v0.17.0 migration notes
before starting LiT. The first startup with a SQL backend requires explicit
confirmation. For noninteractive deployments, set auto-migrate-to-sql=true
in lit.conf or LIT_AUTO_MIGRATE_TO_SQL=true in the environment. To defer
migration, set databasebackend=bbolt before migration runs. Once migration
completes, the old bbolt database is tombstoned, and a downgrade to a version
before v0.17.0-alpha is unsupported.
If you use Taproot Assets channels, follow the
Taproot Assets operational safety guidelines
and arrange a controlled update of affected nodes.
Download the archive for your platform, manifest-v0.17.8.txt, and
manifest-roasbeef-v0.17.8.sig from this release. The detached PGP signature
authenticates the manifest, which contains the SHA-256 hashes of the release
archives and binaries.
Download the release signing key
and check that its primary fingerprint is
A5B61896952D9FDA83BC054CDC42612E89237182 before importing it:
gpg --show-keys --with-fingerprint roasbeef.asc
gpg --import roasbeef.asc
gpg --verify manifest-roasbeef-v0.17.8.sig manifest-v0.17.8.txt
shasum -a 256 <downloaded-archive>Compare the archive hash with its entry in manifest-v0.17.8.txt.
OpenTimestamps proofs are attached for both the manifest and its signature:
ots verify manifest-v0.17.8.txt.ots
ots verify manifest-roasbeef-v0.17.8.sig.otsBitcoin confirmation is required to verify the timestamp attestation. If a
proof reports pending confirmation, retry after the confirmations arrive.
The release binaries are compiled with Go 1.27.3. Use the same toolchain to
reproduce them. The release script includes the litd, autopilotrpc,
signrpc, walletrpc, chainrpc, invoicesrpc, watchtowerrpc,
neutrinorpc, monitoring, peersrpc, kvdb_postgres, kvdb_etcd, and
kvdb_sqlite build tags.
make docker-release tag=v0.17.8To build a single platform, add sys=<OS-ARCH> to the command. Compare the
resulting binary hashes with the entries in manifest-v0.17.8.txt.
To verify the litd and litcli binaries in a Docker image, extract the
binaries, compute their SHA-256 hashes with shasum -a 256 <filename>, and
compare them with the corresponding entries in manifest-v0.17.8.txt.
Nothing published for this version
Nothing published for this version
This release bundles Taproot Assets v0.8.6 and changes the default Loop mode on regtest and simnet to disable . The signed v0.17.7 tag points to commi
This release bundles Taproot Assets v0.8.6 and changes the default Loop mode on regtest and simnet to disable. The signed v0.17.7 tag points to commit 8976aa881d427cc50c4c3b67956e7a271caa6b54.
The integrated versions are lnd v0.21.4-beta, Loop v0.35.0-beta, Pool v0.7.1-beta, Faraday v0.2.19-alpha, and Taproot Assets v0.8.6.
See the full v0.17.7 release notes.
Users upgrading from v0.16.1 or earlier should review the v0.17.0 migration notes before starting LiT. The first startup with a SQL backend requires explicit confirmation. For noninteractive deployments, set auto-migrate-to-sql=true in lit.conf or LIT_AUTO_MIGRATE_TO_SQL=true in the environment. To defer migration, set databasebackend=bbolt before migration runs. Once migration completes, the old bbolt database is tombstoned and a downgrade to a version before v0.17.0-alpha is unsupported.
If Taproot Assets channels are in use, follow the Taproot Assets operational safety guidelines and arrange a controlled update of affected nodes.
Verify the signed tag with git verify-tag v0.17.7. Download manifest-v0.17.7.txt and the archive for your platform. Run shasum -a 256 <archive> and compare the result with the archive's entry in the manifest. The archives are built with Go 1.26.8 and can be rebuilt with make docker-release tag=v0.17.7; add sys=<OS-ARCH> to build one platform.
Before publishing, the release manager should sign manifest-v0.17.7.txt with the release key and attach manifest-roasbeef-v0.17.7.sig. Import the release public key and check its fingerprint is A5B61896952D9FDA83BC054CDC42612E89237182. Timestamp both files with OpenTimestamps and attach their .ots proofs. Once attached, verify them with:
gpg --verify manifest-roasbeef-v0.17.7.sig manifest-v0.17.7.txt
ots verify manifest-v0.17.7.txt.ots
ots verify manifest-roasbeef-v0.17.7.sig.ots
Leonhard Weese and Olaoluwa Osuntokun.
Breaking changes (from v0.14.x to v0.17.x)
New in this version of Lightning Terminal (LiT) : taproot-assets v0.8.5 and lnd v0.21.4-beta
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.4-beta, Taproot Assets Daemon v0.8.5, Loop v0.35.0-beta, Pool v0.7.1-beta and Faraday v0.2.19-alpha.
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.
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.
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.
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 litd v0.17.6 that prevents upgrading LiT from litd v0.14.1-alpha to litd v0.17.6.
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.
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.
lnd remote modeWhen 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.
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 roasbeef's key:
curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
roasbeef's key has the following fingerprint:
pub ed25519 2024-10-21 [SC]
A5B61896952D9FDA83BC054CDC42612E89237182
uid Olaoluwa Osuntokun <laolu32@gmail.com>
Once you have his PGP key you can verify the release (assuming manifest-roasbeef-v0.17.6.sig and manifest-v0.17.6.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.17.6.sig manifest-v0.17.6.txt
You should see the following if the verification was successful:
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@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.6.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.6
We have also timestamped the manifest file with OpenTimeStamps along with its signature. The following files are included along with the rest of our release artifacts: manifest-v0.17.6.txt.ots and manifest-roasbeef-v0.17.6.sig.ots.
Assuming you have the OpenTimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-v0.17.6.txt.ots
ots verify manifest-roasbeef-v0.17.6.sig.ots
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Breaking changes (from v0.14.x to v0.17.x)
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.
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.
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.
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.
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.
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.
lnd remote modeWhen 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.
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
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.
Nothing published for this version
Breaking changes (from v0.14.x to v0.17.x)
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.
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.
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.
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.
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.
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.
lnd remote modeWhen 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.
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
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.
Nothing published for this version
Breaking changes (from v0.14.x to v0.17.x)
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.
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.
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.
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.
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.
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.
lnd remote modeWhen 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.
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
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.
lightning-terminal v0.17.2-alpha-docker
lightning-terminal v0.17.2-alpha-docker
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Breaking changes (from v0.14.x to v0.17.x)
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.
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.
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.
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.
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.
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.
lnd remote modeWhen 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.
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
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.
Nothing published for this version
Nothing published for this version
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 yo…
This version of Lightning Terminal (LiT) includes lnd v0.21.2-beta and loop v0.34.0-beta.
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.
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.
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.
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.
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.
lnd remote modeWhen 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.
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
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.
https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.1.md
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
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 l…
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.
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.
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:
lncli querymc > mission_control_backup.json to back up your mission control state.lncli resetmc to clear the mission control state in the database.lnd and lncli to the new version.lncli loadmc --mcdatapath mission_control_backup.json to restore the backup. Note: This data will not persist across restarts.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.
lnd remote modeWhen 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.
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
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.
https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.0.md
Lightning Terminal v0.17.0-alpha.rc1 Pre-release
Pre-release
Compare
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 yo…
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.
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.
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.
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.
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.
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.
lnd remote modeWhen 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.
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
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.
https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.17.0.md
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.