Skip to content

v0.1.32-beta

Pre-release
Pre-release

Choose a tag to compare

@djkazic djkazic released this 08 Oct 15:06
3626c13

Release Notes

This release of lndinit contains a bug fix that improves usability when lndinit is configured to use litd's gRPC proxy.

LND has been upgraded to the latest RC, v0.20.0-beta.rc1.

Installation and configuration instructions can be found in the 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 kevin_lightning's key from keybase:

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

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

gpg --verify manifest-v0.1.32-beta.sig manifest-v0.1.32-beta.txt

You should see the following if the verification was successful:

gpg: assuming signed data in 'manifest-v0.1.32-beta.txt'
gpg: Signature made Wed Oct  8 10:55:56 2025 EDT
gpg:                using RSA key B1216AF49F6F0DBA1357F8AF511B7BDA931A770F
gpg:                issuer "kevincai96@gmail.com"
gpg: Good signature from "Kevin Cai <kevincai96@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.1.32-beta.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.32-beta

Verifying the Release Timestamp

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

ots verify manifest-v0.1.32-beta.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.1.26-beta...v0.1.32-beta