Release Notes

This is the first major release of Lightning Terminal (LiT)!

This release focuses on improving the user experience of managing your node's channel liquidity using Lightning Loop. You can visualize the current balance of your open channels, with color-coded status indicators to alert you of channels that require your attention. Use Loop In and Loop Out to transfer your Bitcoin balance between the Lightning Network and the on-chain Bitcoin network.

Lightning Terminal is our first application leveraging our new Grand Unified Binary (GrUB) architecture. There is a single executable daemon which contains LiT, LND, Loop, and Faraday all in one. This approach substantially reduces the infrastructure overhead necessary when running each of these daemons separately. This release packages LND v0.10.3-beta, Loop v0.6.5-beta, and Faraday v0.2.0-alpha.

Installation and configuration instructions can be found in the README. Also check out the Walthrough document to learn about all of the current functionality included in this release.

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 guggero's key from keybase:

curl https://keybase.io/guggero/pgp_keys.asc | gpg --import

Once you have his PGP key you can verify the release (assuming manifest-v0.1.0-alpha.txt.asc is in the current directory) with:

gpg --verify manifest-v0.1.0-alpha.txt.asc

You should see the following if the verification was successful:

gpg: Signature made Mi 29 Jul 2020 14:59:19 CEST
gpg:                using RSA key 6E01EEC9656903B0542B8F1003DB6322267C373B
gpg: Good signature from "Oliver Gugger <gugger@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 (which are

cat manifest-v0.1.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.1.0-alpha

Contributors (Alphabetical Order)

Alex Bosworth
Jamal James
Olaoluwa Osuntokun
Oliver Gugger