Skip to content

Lightning Terminal v0.5.1-alpha
Compare
Choose a tag to compare
@guggero guggero released this 21 Sep 14:34
· 994 commits to master since this release
v0.5.1-alpha
This tag was signed with the committer’s verified signature.
guggero Oliver Gugger
GPG key ID: 8E4256593F177720
Learn about vigilant mode.
5cdec77
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) includes some minor bug fixes.

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

This release packages LND v0.13.0-beta, Loop v0.14.1-beta, Pool v0.5.1-alpha, and Faraday v0.2.6-alpha.

Installation and configuration instructions can be found in the README.

Changelog

  1. Fix logging and default macaroon path issue.
  2. Pool UI: add UI for registering a sidecar ticket.
  3. Pool UI: display fee estimates in the order form.
  4. Update frontend dependencies: #224 and #248.
  5. Use docker to generate proto files.
  6. Use JS strings for uint64 gRPC fields to avoid rounding or collision errors.
  7. Add MIT license.
  8. Increase default connection timeouts to lnd.
  9. Update compatibility matrix in README.

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.5.1-alpha.sig and manifest-v0.5.1-alpha.txt are in the current directory) with:

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

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:

cat manifest-v0.5.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.5.1-alpha

Verifying the Release Timestamp

From this new version onwards we'll also now 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.5.1-alpha.sig.ots.

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

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

Contributors (Alphabetical Order)

Graham Krizek
Jamal James
Oliver Gugger

Assets 16
Loading