v2.4.1

Summary

This patch updates boltz-client to its latest version.

Uploading to BTCPay

You can upload the BTCPayServer.Plugins.Boltz.btcpay file to your btcpay server by navigating to Plugins and scrolling all the way down to Upload Plugin.

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://boltz.exchange/static/boltz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming SHA256SUMS and SHA256SUMS.sig are in the current directory) with:

gpg --verify SHA256SUMS.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'boltz-client-manifest-v2.10.2.txt'
gpg: Signature made Wed Dec 17 23:38:35 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <admin@bol.tz>" [unknown]
Primary key fingerprint: 8918 FFBF FB49 E93E F256  D930 542A 7F22 A3BD 9CB0

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

sha256sum --ignore-missing -c SHA256SUMS

If your archive is valid, you should see the following output:

BTCPayServer.Plugins.Boltz.btcpay.json: OK
BTCPayServer.Plugins.Boltz.btcpay: OK

v2.4.0

Summary

This release marks final removal of the GDK wallet library. Remaining legacy wallets will be migrated automatically if they used the default subaccount. In practice, this might cause disruption for setups who've used the same wallet since a version before v2.2.2

Uploading to BTCPay

You can upload the BTCPayServer.Plugins.Boltz.btcpay file to your btcpay server by navigating to Plugins and scrolling all the way down to Upload Plugin.

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://boltz.exchange/static/boltz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming SHA256SUMS and SHA256SUMS.sig are in the current directory) with:

gpg --verify SHA256SUMS.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'boltz-client-manifest-v2.10.2.txt'
gpg: Signature made Wed Dec 17 23:38:35 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <admin@bol.tz>" [unknown]
Primary key fingerprint: 8918 FFBF FB49 E93E F256  D930 542A 7F22 A3BD 9CB0

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

sha256sum --ignore-missing -c SHA256SUMS

If your archive is valid, you should see the following output:

BTCPayServer.Plugins.Boltz.btcpay.json: OK
BTCPayServer.Plugins.Boltz.btcpay: OK

v2.3.4

Summary

This patch fixes an issue with the latest btcpay release.

Uploading to BTCPay

You can upload the BTCPayServer.Plugins.Boltz.btcpay file to your btcpay server by navigating to Plugins and scrolling all the way down to Upload Plugin.

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://boltz.exchange/static/boltz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming SHA256SUMS and SHA256SUMS.sig are in the current directory) with:

gpg --verify SHA256SUMS.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'boltz-client-manifest-v2.10.2.txt'
gpg: Signature made Wed Dec 17 23:38:35 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <admin@bol.tz>" [unknown]
Primary key fingerprint: 8918 FFBF FB49 E93E F256  D930 542A 7F22 A3BD 9CB0

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

sha256sum --ignore-missing -c SHA256SUMS

If your archive is valid, you should see the following output:

BTCPayServer.Plugins.Boltz.btcpay.json: OK
BTCPayServer.Plugins.Boltz.btcpay: OK

v2.3.3

Summary

This patch updates boltz-client, improving performance for instances with large liquid wallets and protection against wallet corruption.

Uploading to BTCPay

You can upload the BTCPayServer.Plugins.Boltz.btcpay file to your btcpay server by navigating to Plugins and scrolling all the way down to Upload Plugin.

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://boltz.exchange/static/boltz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming SHA256SUMS and SHA256SUMS.sig are in the current directory) with:

gpg --verify SHA256SUMS.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'boltz-client-manifest-v2.10.2.txt'
gpg: Signature made Wed Dec 17 23:38:35 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <admin@bol.tz>" [unknown]
Primary key fingerprint: 8918 FFBF FB49 E93E F256  D930 542A 7F22 A3BD 9CB0

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

sha256sum --ignore-missing -c SHA256SUMS

If your archive is valid, you should see the following output:

BTCPayServer.Plugins.Boltz.btcpay.json: OK
BTCPayServer.Plugins.Boltz.btcpay: OK

v2.3.1.1

Summary

This backport on v2.3.1 brings the latest changes of v2.3.3 for people who haven't upgraded to the latest btcpay.

Uploading to BTCPay

You can upload the BTCPayServer.Plugins.Boltz.btcpay file to your btcpay server by navigating to Plugins and scrolling all the way down to Upload Plugin.

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://boltz.exchange/static/boltz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming SHA256SUMS and SHA256SUMS.sig are in the current directory) with:

gpg --verify SHA256SUMS.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'boltz-client-manifest-v2.10.2.txt'
gpg: Signature made Wed Dec 17 23:38:35 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <admin@bol.tz>" [unknown]
Primary key fingerprint: 8918 FFBF FB49 E93E F256  D930 542A 7F22 A3BD 9CB0

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

sha256sum --ignore-missing -c SHA256SUMS

If your archive is valid, you should see the following output:

BTCPayServer.Plugins.Boltz.btcpay.json: OK
BTCPayServer.Plugins.Boltz.btcpay: OK

v2.3.2

Summary

This release ensure compatibility with the latest btcpay release v2.3.7.

Uploading to BTCPay

You can upload the BTCPayServer.Plugins.Boltz.btcpay file to your btcpay server by navigating to Plugins and scrolling all the way down to Upload Plugin.

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://boltz.exchange/static/boltz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming SHA256SUMS and SHA256SUMS.sig are in the current directory) with:

gpg --verify SHA256SUMS.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'boltz-client-manifest-v2.10.2.txt'
gpg: Signature made Wed Dec 17 23:38:35 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <admin@bol.tz>" [unknown]
Primary key fingerprint: 8918 FFBF FB49 E93E F256  D930 542A 7F22 A3BD 9CB0

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

sha256sum --ignore-missing -c SHA256SUMS

If your archive is valid, you should see the following output:

BTCPayServer.Plugins.Boltz.btcpay.json: OK
BTCPayServer.Plugins.Boltz.btcpay: OK

v2.3.1

Summary

This patch updates to the latest boltz-client version, bringing performance improvements to large liquid wallets.

Uploading to BTCPay

You can upload the BTCPayServer.Plugins.Boltz.btcpay file to your btcpay server by navigating to Plugins and scrolling all the way down to Upload Plugin.

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://boltz.exchange/static/boltz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming SHA256SUMS and SHA256SUMS.sig are in the current directory) with:

gpg --verify SHA256SUMS.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'boltz-client-manifest-v2.10.2.txt'
gpg: Signature made Wed Dec 17 23:38:35 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <admin@bol.tz>" [unknown]
Primary key fingerprint: 8918 FFBF FB49 E93E F256  D930 542A 7F22 A3BD 9CB0

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

sha256sum --ignore-missing -c SHA256SUMS

If your archive is valid, you should see the following output:

BTCPayServer.Plugins.Boltz.btcpay.json: OK
BTCPayServer.Plugins.Boltz.btcpay: OK

v2.3.0

Summary

This release marks the removal of the rebalance mode. Due to low usage and a lot of edge cases with the node connection we have decided to remove the feature from master. If you wish to keep using it, you can keep running on v2.2.22 or build the rebalance-mode git branch on your own which will still receive important patches in the near future or run boltz-client next to your lightning node manually.

Uploading to BTCPay

You can upload the BTCPayServer.Plugins.Boltz.btcpay file to your btcpay server by navigating to Plugins and scrolling all the way down to Upload Plugin.

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://boltz.exchange/static/boltz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming SHA256SUMS and SHA256SUMS.sig are in the current directory) with:

gpg --verify SHA256SUMS.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'boltz-client-manifest-v2.10.2.txt'
gpg: Signature made Wed Dec 17 23:38:35 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <admin@bol.tz>" [unknown]
Primary key fingerprint: 8918 FFBF FB49 E93E F256  D930 542A 7F22 A3BD 9CB0

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

sha256sum --ignore-missing -c SHA256SUMS

If your archive is valid, you should see the following output:

BTCPayServer.Plugins.Boltz.btcpay.json: OK
BTCPayServer.Plugins.Boltz.btcpay: OK

v2.2.22

Summary

This patch ensures compatibility of latest btcpay release v2.3.6-rc6.

Uploading to BTCPay

You can upload the BTCPayServer.Plugins.Boltz.btcpay file to your btcpay server by navigating to Plugins and scrolling all the way down to Upload Plugin.

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://boltz.exchange/static/boltz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming SHA256SUMS and SHA256SUMS.sig are in the current directory) with:

gpg --verify SHA256SUMS.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'boltz-client-manifest-v2.10.2.txt'
gpg: Signature made Wed Dec 17 23:38:35 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <admin@bol.tz>" [unknown]
Primary key fingerprint: 8918 FFBF FB49 E93E F256  D930 542A 7F22 A3BD 9CB0

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

sha256sum --ignore-missing -c SHA256SUMS

If your archive is valid, you should see the following output:

BTCPayServer.Plugins.Boltz.btcpay.json: OK
BTCPayServer.Plugins.Boltz.btcpay: OK

v2.2.21

Summary

This patch makes the plugin work on the newest BTCPay release v2.3.6

Uploading to BTCPay

You can upload the BTCPayServer.Plugins.Boltz.btcpay file to your btcpay server by navigating to Plugins and scrolling all the way down to Upload Plugin.

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://boltz.exchange/static/boltz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming SHA256SUMS and SHA256SUMS.sig are in the current directory) with:

gpg --verify SHA256SUMS.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'boltz-client-manifest-v2.10.2.txt'
gpg: Signature made Wed Dec 17 23:38:35 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <admin@bol.tz>" [unknown]
Primary key fingerprint: 8918 FFBF FB49 E93E F256  D930 542A 7F22 A3BD 9CB0

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

sha256sum --ignore-missing -c SHA256SUMS

If your archive is valid, you should see the following output:

BTCPayServer.Plugins.Boltz.btcpay.json: OK
BTCPayServer.Plugins.Boltz.btcpay: OK