Skip to content

Lightning Terminal v0.5.0-alpha
Compare
Choose a tag to compare
@Roasbeef Roasbeef released this 21 Jun 22:17
· 1038 commits to master since this release
v0.5.0-alpha
9a4d739

Release Notes

This release of Lightning Terminal (LiT) includes some minor bug fixes, and updates the version of lnd package in the integrated mode to the latest version (v0.13.0).

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.0-alpha, and Faraday v0.2.6-alpha.

Installation and configuration instructions can be found in the README.

Changelog

  1. Update lnd related dependancies to latest major releases.
  2. Add link in README to more detailed installation instructions.
  3. Pool UI: bug fix to ensure input numbers isn't being truncated
  4. A new issue template has been added for the project.
  5. The Go standard library is now used to embed the static assets instead of statik.
  6. The default admin macaroon location should now be working again.

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

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

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

gpg --verify manifest-roasbeef-v0.5.0-alpha.sig manifest-v0.5.0-alpha.txt

You should see the following if the verification was successful:

gpg: Signature made Mon Jun 21 15:14:50 2021 PDT
gpg:                using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@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.4.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.0-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-roasbeef-v0.5.0-alpha.sig.ots.

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

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

Contributors (Alphabetical Order)

Jamal James
Justin O'Brien
Olaoluwa Osuntokun
Oliver Gugger
keblek

Assets 17
Loading