Repository navigation
Bisq Connect Trusted Node (Bisq2-api) 2.1.14.0
🔐 Security release notes
Bisq 2 Trusted Node 2.1.14.0 is a security release of the headless Bisq 2 node (the bisq2-api docker image, binaries in bisq-network packages) that Bisq Connect pairs with on Umbrel, StartOS and self-managed Docker hosts.
Update your node before 25 November 2026. From that date updated nodes no longer accept data signed only the old way, so a node still on 2.1.13 can miss offers and messages and its trades can stall.
- Bisq 2 API 2.1.14: the node runs the Bisq 2 security release: new storage signatures and owner-bound storage keys, stricter checks when offers are taken, separate Tor circuits per identity, pairing secrets stored only as hashes, and authentication on every WebSocket connection — Bisq 2 v2.1.14 notes
- Tor 0.4.9.14: the image's minimum Tor version is raised to the latest release from the Tor Project's own package repository
- No more secrets in the logs: the pairing code, onion keys and profile private keys no longer reach the node's console output, and this version hides the keys that earlier versions wrote to the log files in its data directory
Full changes: https://github.com/bisq-network/bisq2/releases/tag/v2.1.14 (bisq2 @ 52f9141 = v2.1.14 plus translation updates, branch for-mobile-based-on-2.1.14)
⚠️ Before you update
- Old logs contain private keys. Logs written by node versions up to 2.1.13 contain the node's onion private keys and the private keys of its user profiles. This version hides them in its own log files, but do not share older copies: container logs, log viewer exports or backups
- No downgrade. Going back to 2.1.13 after this update is not supported; it would require pairing every device again
- Fixed-price offers published through a 2.1.13 node are not shown on updated nodes; create them again after updating
Compatibility
- Bisq Connect 0.10.0 (current) works with 2.1.14.0 nodes without pairing again; it asks you to accept the updated terms once. The next Bisq Connect release will require a 2.1.14.0 node, so update the node first
- Pairing Bisq Connect with Bisq 2 Desktop? Update the desktop to v2.1.14
Rollout status
| Channel | How you get it | Tracking | Status |
|---|---|---|---|
| Umbrel App Store (recommended) | Update offered in the Umbrel App Store once merged | getumbrel/umbrel-apps#6203 | ✅ available now |
| Umbrel community store | Update offered in the Bisq Network community store | bisq2-umbrel#10 | ✅ available now |
| StartOS community registry | Update offered by StartOS once merged (Start9 publishes v2.1.14.0_0 automatically) |
Start9-Community/bisq2-startos#12 | ✅ available now |
| StartOS package mirror | Source mirror only, no user action | bisq2-startos#9 | ✅ available now |
| Docker | docker pull ghcr.io/bisq-network/bisq2-api:2.1.14.0 and restart |
— | ✅ available now |
📦 Images
| Image | Reference |
|---|---|
| Node | ghcr.io/bisq-network/bisq2-api:2.1.14.0@sha256:5b028dbe98353fae10d49d8d69f864a7ef9d294647d868c127f66c9f6a4f0a64 |
| Web UI sidecar (Umbrel) | ghcr.io/bisq-network/bisq2-api-web-ui:2.1.14.0@sha256:3e010e4ca8031d07c64a9b1459f603d5d2db6953edfddad95940c4a5fc68a950 |
Both images are multi-arch (linux/amd64, linux/arm64). Verified after publishing by inspecting the image layers: the installed package is tor 0.4.9.14-1~jammy+1 on both architectures. Build: release run.
What to do
- Umbrel: install the update from the App Store when it appears (or add the community store to get it earlier)
- StartOS: install the update from the Community Registry when it appears
- Docker: pull the new tag (digest above) and restart the container; your data directory is upgraded in place on first start, which can take a little longer than usual
- Open Bisq Connect, accept the updated terms, and confirm it reports the node on API 2.1.14; keep the app updated