Summary

This patch fixes an issue with LWK's auto-consolidation.

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

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

You should see the following if the verification was successful:

gpg: Signature made Mon Dec 15 16:00:38 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <[email protected]>" [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 boltz-client-manifest-v2.12.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.12.2.tar.gz: OK

Summary

This patch includes some fixes for certain race conditions and improves the automated claim retries.

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

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

You should see the following if the verification was successful:

gpg: Signature made Mon Dec 15 16:00:38 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <[email protected]>" [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 boltz-client-manifest-v2.12.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.12.1.tar.gz: OK

Summary

This release marks the final removal of the GDK wallet library. Remaining legacy wallets will be migrated automatically if they used the default subaccount. Watch out for warnings in the logs or getinfo CLI command after upgrading setups with old wallets.

Highlights

• feat: deprecate gdk by @jackstar12 in #671
• refactor: wallet unique constrant by @jackstar12 in #672

Full Changelog: v2.11.3...v2.12.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://boltz.exchange/static/boltz.asc | gpg --import

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

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

You should see the following if the verification was successful:

gpg: Signature made Mon Dec 15 16:00:38 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <[email protected]>" [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 boltz-client-manifest-v2.12.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.12.0.tar.gz: OK

Summary

This patch improves the performance of instances with lots of liquid wallets.

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

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

You should see the following if the verification was successful:

gpg: Signature made Mon Dec 15 16:00:38 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <[email protected]>" [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 boltz-client-manifest-v2.11.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.11.3.tar.gz: OK

Summary

This patch updates lwk, bringing notable performance improvements to large wallets.

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

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

You should see the following if the verification was successful:

gpg: Signature made Mon Dec 15 16:00:38 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <[email protected]>" [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 boltz-client-manifest-v2.11.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.11.2.tar.gz: OK

Summary

This patch includes an important fix when connecting to backends with pairs unknown to the client.

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

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

You should see the following if the verification was successful:

gpg: Signature made Mon Dec 15 16:00:38 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <[email protected]>" [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 boltz-client-manifest-v2.11.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.11.1.tar.gz: OK

Summary

This release includes a new rpc and cli command for swap quotes and improves the flexibility of the refundswap command for handling rare edge cases.

Highlights

• feat: allow manual refund of explicit lockups for swaps by @jackstar12 in #619
• feat: GetSwapQuotes rpc by @jackstar12 in #624

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

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

You should see the following if the verification was successful:

gpg: Signature made Mon Dec 15 16:00:38 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <[email protected]>" [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 boltz-client-manifest-v2.11.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.11.0.tar.gz: OK

Full Changelog: v2.10.2...v2.11.0

Summary

This patch improves the reliability of the websocket for handling lots of incoming swap updates by increasing internal buffers.

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

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

You should see the following if the verification was successful:

gpg: Signature made Mon Dec 15 16:00:38 2025 CET
gpg:                   using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <[email protected]>" [
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 boltz-client-manifest-v2.10.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.10.2.tar.gz: OK

Summary

This patch includes a fix for the reverse swap claiming logic.

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

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

You should see the following if the verification was successful:

gpg: Signature made Mon Dec 15 16:00:38 2025 CET
gpg:                using RSA key 8918FFBFFB49E93EF256D930542A7F22A3BD9CB0
gpg: Good signature from "Boltz (Boltz signing key) <[email protected]>" [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 boltz-client-manifest-v2.10.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.10.1.tar.gz: OK

Summary

Starting with this release, new Bitcoin wallets are powered by BDK.

Highlights

• feat: bdk rust bindings by @jackstar12 in #566
• feat: add tenant remove command by @kilrau in #597

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

gpg --verify boltz-client-manifest-master.txt.sig boltz-client-manifest-master.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-master.txt

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

boltz-client-linux-amd64-master.tar.gz: OK