Skip to content

Lightning Terminal v0.11.0-alpha
Compare
Choose a tag to compare
@ViktorTigerstrom ViktorTigerstrom released this 04 Oct 08:19
· 149 commits to master since this release
v0.11.0-alpha
This tag was signed with the committer’s verified signature.
ViktorTigerstrom Viktor Tigerström
GPG key ID: B984570980684DCC
Learn about vigilant mode.
8d7c53b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release Notes

This release of Lightning Terminal (LiT) updates the integrated LND daemon version to the latest v0.17.0-beta release, as well as updates the integrated Loop daemon to the latest patch release.

In this release of LiT, a new Status server was added, which enables users to disable the different integrated sub-servers and the integrated accounts sub-system in LiT through configuration. LiT will now also successfully start even if any of the sub-servers or sub-systems fails to start.

This release of LiT also enables the ability to link a new Autopilot session with an old session, as well as enabling the ability to specify feature configurations for an Autopilot session.

One important change to note for users running LiT through docker, is that due to the new status server feature, the startup process of LiT won’t error and end if a sub-server or sub-system fails to start. So any platforms that rely on docker to automatically restart the LiT container if the startup process ends due to the sub-servers or sub-system not having started yet, will now not restart the container as the start process won't exit.

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

This release packages LND v0.17.0-beta, Taproot Assets Daemon v0.2.3-alpha, Loop v0.26.3-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 ViktorTigerstrom's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 187F6ADD93AE3B0CF335AA6AB984570980684DCC

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

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

You should see the following if the verification was successful:

gpg: Signature made Tue Oct  3 21:26:36 2023 CEST
gpg:                using EDDSA key 187F6ADD93AE3B0CF335AA6AB984570980684DCC
gpg: Good signature from "Viktor Tigerström <vtigerstrom@gmail.com>"

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.11.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.11.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-v0.11.0-alpha.sig.ots.

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

ots verify manifest-v0.11.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.

Changelog (auto-generated)

What's Changed

New Contributors

Full Changelog: v0.10.5-alpha...v0.11.0-alpha

Contributors

guggero, itsrachelfish, and 4 other contributors
Assets 15