What changed, and why it matters
This commit only changes the local development/testing setup for LNbits. It pins the Boltz service used in CI/regtest from the floating 'latest' Docker tag to a specific version (v3.12.1), and updates the matching test configuration file. There is no change to production LNbits code, no user-facing fix, and no disclosed security issue.
No security response is needed. Treat as a routine CI/maintenance change. If reviewing supply-chain posture, note that pinning CI images is good practice but does not address a known vulnerability.
Security signals we found
Pinning a dependency image tag from 'latest' to a specific version is a supply-chain/reproducibility hardening practice, but it is not evidence of an exploited vulnerability.
No production code, wallet logic, API, or authentication code is modified.
No security advisory, CVE, bug bounty attribution, or vulnerability description is present in the commit or title.
Evidence from the diff
The diff updates docker/regtest/docker-compose.yml to use boltz/boltz:v3.12.1 instead of boltz/boltz:latest, and adjusts docker/regtest/data/boltz/boltz.conf to match that version’s expected settings (adds [swap] deferredClaimSymbols, removes isLegacy flags, adds feeFloor). These files are part of the local regtest/CI environment, not the runtime LNbits application. The change improves CI reproducibility and prevents unexpected breakage from upstream Boltz updates, but it does not patch a vulnerability in LNbits itself.
Changed components
docker/regtest/docker-compose.ymldocker/regtest/data/boltz/boltz.confInspect captured patch +6 / −3
diff --git a/docker/regtest/data/boltz/boltz.conf b/docker/regtest/data/boltz/boltz.conf
index 6a3ef7c..471612f 100644
--- a/docker/regtest/data/boltz/boltz.conf
+++ b/docker/regtest/data/boltz/boltz.conf
@@ -26,8 +26,10 @@ password = "boltz"
host = "0.0.0.0"
port = 9005
+[swap]
+deferredClaimSymbols = ["BTC", "L-BTC"]
+
[[pairs]]
-isLegacy = true
base = "BTC"
quote = "BTC"
rate = 1
@@ -44,7 +46,6 @@ minSwapAmount = 50_000
swapTaproot = 10080
[[pairs]]
-isLegacy = true
base = "L-BTC"
quote = "BTC"
fee = 0.25
@@ -83,6 +84,7 @@ maxZeroConfAmount = 0
zmqpubrawblock = "tcp://bitcoind:29001"
port = 18_443
cookie = "/root/.bitcoin/regtest/.cookie"
+ feeFloor = 0.2
wallet = "lnbits"
@@ -101,6 +103,7 @@ maxSwapAmount = 40_294_967
minSwapAmount = 10_000
maxZeroConfAmount = 40_294_967
+
[liquid.chain]
host = "elementsd"
port = 18884
diff --git a/docker/regtest/docker-compose.yml b/docker/regtest/docker-compose.yml
index f328f1d..703085d 100644
--- a/docker/regtest/docker-compose.yml
+++ b/docker/regtest/docker-compose.yml
@@ -28,7 +28,7 @@ services:
- lnd-2
- boltz-postgres
restart: always
- image: boltz/boltz:latest
+ image: boltz/boltz:v3.12.1
ports:
- 9000:9000
entrypoint: "sh -c 'sleep 30; /boltz-backend/bin/boltzd'"
Why this scored 18/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.