v2.3.3

Summary

This patch fixes an issue when creating swaps with invoices created by another boltz swap.

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.3.3.txt.sig and boltz-client-manifest-v2.3.3.txt are in the current directory) with:

gpg --verify boltz-client-manifest-v2.3.3.txt.sig boltz-client-manifest-v2.3.3.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 <[email protected]>" [unknown]
gpg:                 aka "Michael <[email protected]>" [unknown]

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

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

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

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

v2.3.2

Summary

This patch fixes an issue with the wallet balance checks before swap creation.

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.3.2.txt.sig and boltz-client-manifest-v2.3.2.txt are in the current directory) with:

gpg --verify boltz-client-manifest-v2.3.2.txt.sig boltz-client-manifest-v2.3.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 <[email protected]>" [unknown]
gpg:                 aka "Michael <[email protected]>" [unknown]

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

sha256sum --ignore-missing -c boltz-client-manifest-v2.3.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.3.2.tar.gz: OK

v2.3.1

Summary

This patch changes the default mempool api endpoint for the liquid network.

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.3.1.txt.sig and boltz-client-manifest-v2.3.1.txt are in the current directory) with:

gpg --verify boltz-client-manifest-v2.3.1.txt.sig boltz-client-manifest-v2.3.1.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 <[email protected]>" [unknown]
gpg:                 aka "Michael <[email protected]>" [unknown]

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

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

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

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

v2.2.3

Summary

This patch changes the default mempool api endpoint for the liquid network.

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.3.txt.sig and boltz-client-manifest-v2.2.3.txt are in the current directory) with:

gpg --verify boltz-client-manifest-v2.2.3.txt.sig boltz-client-manifest-v2.2.3.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 <[email protected]>" [unknown]
gpg:                 aka "Michael <[email protected]>" [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.3.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.3.tar.gz: OK

v2.3.0 - Execute

Summary

This release includes a new ExecuteRecommendations rpc for manually approving autoswap recommendations.

Highlights

• feat: chain autoswap sweeps by @jackstar12 in #341
• feat: autoswap execute rpc by @jackstar12 in #342

Full Changelog: v2.2.1...v2.3.0

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.3.0.txt.sig and boltz-client-manifest-v2.3.0.txt are in the current directory) with:

gpg --verify boltz-client-manifest-v2.3.0.txt.sig boltz-client-manifest-v2.3.0.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 <[email protected]>" [unknown]
gpg:                 aka "Michael <[email protected]>" [unknown]

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

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

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

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

v2.2.2

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 <[email protected]>" [unknown]
gpg:                 aka "Michael <[email protected]>" [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

v2.2.1

Summary

This patch includes two fixes for the WalletSend rpc.

Highlights

• fix: dont allow lowball in WalletSend by @jackstar12 in #332
• fix: respect send_all rpc param in WalletSend by @jackstar12 in #333

Full Changelog: v2.2.0...v2.2.1

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.1.txt.sig and boltz-client-manifest-v2.2.1.txt are in the current directory) with:

gpg --verify boltz-client-manifest-v2.2.1.txt.sig boltz-client-manifest-v2.2.1.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 <[email protected]>" [unknown]
gpg:                 aka "Michael <[email protected]>" [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.1.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.1.tar.gz: OK

v2.2.0 - Offer accepted

Summary

This release introduced support for paying to bolt12 invoices via submarine swaps and Chain swaps with any amount (within our min/max).

Highlights

• feat: bolt12 support for submarine swaps by @jackstar12 in #309
• feat: amountless chain swaps by @jackstar12 in #291

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.0.txt.sig and boltz-client-manifest-v2.2.0.txt are in the current directory) with:

gpg --verify boltz-client-manifest-v2.2.0.txt.sig boltz-client-manifest-v2.2.0.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 <[email protected]>" [unknown]
gpg:                 aka "Michael <[email protected]>" [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.0.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.0.tar.gz: OK

v2.1.11 - Panic

Summary

This release includes a hot fix for a crash on client startup.

Highlights

• fix: check if chosenOutput is nil when looking for direct payments by @jackstar12 in #319

Full Changelog: v2.1.10...v2.1.11

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.1.11.txt.sig and boltz-client-manifest-v2.1.11.txt are in the current directory) with:

gpg --verify boltz-client-manifest-v2.1.11.txt.sig boltz-client-manifest-v2.1.11.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 <[email protected]>" [unknown]
gpg:                 aka "Michael <[email protected]>" [unknown]

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

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

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

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

v2.1.10 - LNURL

Summary

This release includes support LNURL and LN Addresses when creating swaps and some bug fixes.

Highlights

• feat: support creating swaps with lnurls and lnaddresses by @jackstar12 in #308
• fix: force reconnect if boltz ws doesnt respond by @jackstar12 in #317
• fix: handle multiple direct payments to same address correctly by @jackstar12 in #315

Full Changelog: v2.1.9...v2.1.10

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.1.10.txt.sig and boltz-client-manifest-v2.1.10.txt are in the current directory) with:

gpg --verify boltz-client-manifest-v2.1.10.txt.sig boltz-client-manifest-v2.1.10.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 <[email protected]>" [unknown]
gpg:                 aka "Michael <[email protected]>" [unknown]

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

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

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

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