From 8fcd7175c6275235b122fab436013bc26ea0d0c0 Mon Sep 17 00:00:00 2001 From: rodvar <1040902+rodvar@users.noreply.github.com> Date: Fri, 6 Nov 2026 13:52:20 +1100 Subject: [PATCH] Update Bisq 2 Node 2.1.15.0 (#6315) Co-authored-by: bisq-mobile-ci --- bisq2-node/docker-compose.yml | 4 ++-- bisq2-node/umbrel-app.yml | 18 +++++++----------- 2 files changed, 9 insertions(+), 13 deletions(-) diff --git a/bisq2-node/docker-compose.yml b/bisq2-node/docker-compose.yml index c72804503..ff8e51463 100644 --- a/bisq2-node/docker-compose.yml +++ b/bisq2-node/docker-compose.yml @@ -16,7 +16,7 @@ services: APP_PORT: 8091 server: - image: ghcr.io/bisq-network/bisq2-api:2.1.14.1@sha256:7ce32c42543a0241796952155706aaa7c66c48160299ae773775f8c05adb7982 + image: ghcr.io/bisq-network/bisq2-api:2.1.15.0@sha256:a92a692dc374e2645aba37bdade2d9c8ab042a010f0e0c7147b7ea540337c312 restart: on-failure stop_grace_period: 1m mem_limit: 2g @@ -24,7 +24,7 @@ services: - ${APP_DATA_DIR}/data:/data web: - image: ghcr.io/bisq-network/bisq2-api-web-ui:2.1.14.1@sha256:6c26e77b22b9328759c2c93581dc826e106e95bca9814ce9f3198aab9aa49c8e + image: ghcr.io/bisq-network/bisq2-api-web-ui:2.1.15.0@sha256:f2ede0b24183e37f97773da7b1f95c61779cffac11ffebb069b33b5018fe91f3 restart: on-failure network_mode: "service:server" volumes: diff --git a/bisq2-node/umbrel-app.yml b/bisq2-node/umbrel-app.yml index 86bb31b19..e53da9bb0 100644 --- a/bisq2-node/umbrel-app.yml +++ b/bisq2-node/umbrel-app.yml @@ -4,7 +4,7 @@ storage: dataRoot: data category: bitcoin name: Bisq 2 Node -version: "2.1.14.1" +version: "2.1.15.0" tagline: Run your own Bisq 2 node for private Bitcoin trading description: >- Bisq Connect lets you buy and sell Bitcoin peer-to-peer from your phone. This @@ -37,22 +37,18 @@ defaultPassword: "" submitter: rodvar submission: https://github.com/getumbrel/umbrel-apps/pull/5850 releaseNotes: >- - **No action needed.** Bisq Connect stays paired. + **Security update. Update now to keep trading.** A Bisq security alert requires version 2.1.15 or newer for trading. Until this node is updated, Bisq Connect cannot take offers through it and asks you to have the node upgraded, and offers published through it cannot be taken. Bisq Connect stays paired and needs no update. - This maintenance update keeps the node on Bisq 2 API 2.1.14 and brings fixes for Bisq Connect. + This update moves the node to Bisq 2 API 2.1.15. - - **Banned account data:** The node can now check a seller's payment account data against the banned list, so the next Bisq Connect release can warn you not to pay a seller whose account data is banned and cancel the trade for your protection. + - **Tor:** The node now runs the Tor bundled with Bisq (Tor 0.4.9.15) inside a sandbox, instead of a Tor package installed in the image. The sandbox keeps a compromised Tor away from the node's files and keys. - - **Offerbook:** Offers from banned or ignored makers, and sell offers whose maker lacks the reputation for the amount, are no longer listed, and the offer counts match the list. - - - **Restarts:** If the node fails to start, it now exits so it is restarted automatically instead of running without the API. A pairing code left over from an earlier run is deleted at startup. - - - **Trades:** Cancelling or rejecting a trade no longer waits for the trade chat message to be delivered. + - **Hardening:** Oversized responses from the network are refused instead of using unbounded memory, and file cleanup no longer follows links. - It also includes storage pruning and performance fixes. + Bisq 2 release: https://github.com/bisq-network/bisq2/releases/tag/v2.1.15 - Full changes: https://github.com/bisq-network/bisq2/compare/52f9141...7f68c09 (bisq2 @ 7f68c09) + Full changes: https://github.com/bisq-network/bisq2/compare/7f68c09...cfe8ab2 (bisq2 @ cfe8ab2)