This release of Lightning Terminal (LiT) includes updates the integrated Taproot-assets (v0.4.1-alpha) and Loop (v0.28.6-beta) versions.
The minimum compatible version of lnd in remote mode has now been bumped to v0.17.1-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.18.2-beta, Taproot Assets Daemon v0.4.1-alpha, Loop v0.28.6-beta, Pool v0.6.5-beta and Faraday v0.2.13-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

The configuration value (taproot-assets.universe.public-access) and command line flag (--taproot-assets.universe.public-access) now needs a value and is no longer a boolean. The value now controls whether the node's universe database can be accessed over RPC and either read (value r) or written to (value w) or both (value rw).
So existing nodes with the configuration file value taproot-assets.universe.public-access=true need to change the value to taproot-assets.universe.public-access=rw. Users specifying the command line flag --taproot-assets.universe.public-access just need to append a value, for example --taproot-assets.universe.public-access=rw.

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.17.1-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.

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 ellemouton's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 26984CB69EB8C4A26196F7A4D7D916376026F177

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

gpg --verify manifest-v0.13.3-alpha.sig manifest-v0.13.3-alpha.txt

You should see the following if the verification was successful:

gpg: Signature made Fri Jul 26 11:24:28 2024 SAST
gpg:                using RSA key 26984CB69EB8C4A26196F7A4D7D916376026F177
gpg: Good signature from "Elle Mouton <elle.mouton@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.13.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.13.3-alpha