github BoltzExchange/boltz-client v2.2.2

10 hours ago

Summary

This patch fixes an issue related to gdk.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. You'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/BoltzExchange/boltz-client/master/keys/michael.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming boltz-client-manifest-v2.2.2.txt.sig and boltz-client-manifest-v2.2.2.txt are in the current directory) with:

gpg --verify boltz-client-manifest-v2.2.2.txt.sig boltz-client-manifest-v2.2.2.txt

You should see the following if the verification was successful:

gpg: Signature made Mo 01 Jul 2024 00:40:51 CEST
gpg:                using RSA key C2640F630570F5EDEDE02DE684D249BA71685D46
gpg: Good signature from "Michael <me@michael1011.at>" [unknown]
gpg:                 aka "Michael <michael101101@me.com>" [unknown]

You should also verify that the hashes still match with the archive you've downloaded.

sha256sum --ignore-missing -c boltz-client-manifest-v2.2.2.txt

If your archive is valid, you should see the following output (depending on the archive you've downloaded):

boltz-client-linux-amd64-v2.2.2.tar.gz: OK

Don't miss a new boltz-client release

NewReleases is sending notifications on new releases.