v0.2.4-alpha

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 the keys that have signed this release if you haven't done so already:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 2E9666012186E2730EA47BEDE853DFADEAF2675E

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

gpg --verify manifest-jamaljsr-v0.2.4-alpha.sig manifest-v0.2.4-alpha.txt

You should see the following if the verification was successful:

gpg: Signature made Thu Mar 30 16:48:47 2023 EDT
gpg:                using RSA key 2E9666012186E2730EA47BEDE853DFADEAF2675E
gpg:                issuer "jamaljsr@protonmail.com"
gpg: Good signature from "Jamal James <jamaljsr@protonmail.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.2.4-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.2.4-alpha

What's Changed

• wasm: allow non-global scope callbacks by @jamaljsr in #72
• Bump lnd and golang versions by @guggero in #74

Full Changelog: v0.2.3-alpha...v0.2.4-alpha