Lightning Terminal v0.10.5-alpha
ellemouton
Elle
Release Notes
This release of Lightning Terminal (LiT) includes an update to the integrated Loop version along with a small UI update use the correct unit for Loop Out swap deadlines.
We'll be continuously working to improve the user experience based on feedback from the community.
This release packages LND v0.16.4-beta, Taproot Assets Daemon v0.2.3-alpha, Loop v0.26.2-beta, Pool v0.6.4-beta and Faraday v0.2.11-alpha.
NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.16.0-beta.
Installation and configuration instructions can be found in the README.
Required changes when running in lnd remote mode (lnd-mode=remote)
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 his PGP key you can verify the release (assuming manifest-v0.10.5-alpha.sig and manifest-v0.10.5-alpha.txt are in the current directory) with:
gpg --verify manifest-v0.10.5-alpha.sig manifest-v0.10.5-alpha.txt
You should see the following if the verification was successful:
gpg: Signature made Tue Aug 8 18:17:56 2023 SAST
gpg: using RSA key 26984CB69EB8C4A26196F7A4D7D916376026F177
gpg: Good signature from "Elle Mouton <[email protected]>" [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.10.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.10.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-v0.10.5-alpha.sig.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:
ots verify manifest-v0.10.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.