Skip to content

Bisq Connect Trusted Node (Bisq2-api) 2.1.13.0

Choose a tag to compare

View all tags
@rodvar rodvar released this 28 Sep 10:28
trusted-node_2.1.13.0
c80be18
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

🔐 Security release notes

Bisq 2 Trusted Node 2.1.13.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.

We recommend all node operators update as soon as possible, then make sure Bisq Connect is up to date.

  • Tor security upgrade to 0.4.9.13: the node's Tor daemon now includes the Tor Project's emergency security releases of 8 and 23 September 2026 (0.4.9.12 and 0.4.9.13), closing a series of high-severity issues affecting clients, onion services and relays — Tor advisory
  • Tor straight from the Tor Project: the image now installs tor from the Tor Project's own package repository with a fail-closed minimum-version gate, instead of the distribution package that lagged behind. Future Tor security releases reach the node image within days
  • Bisq 2 API 2.1.13: the node runs the Bisq 2 release that Bisq marks as required to continue trading — Bisq 2 v2.1.13 notes
  • umbrelOS 2.0 storage management: the Umbrel App Store package supports moving the node's data to another drive

Full changes: bisq-network/bisq2@v2.1.13...3e07b59 (bisq2 @ 3e07b59, branch for-mobile-based-on-2.1.13)

Compatibility

  • Bisq Connect 0.10.0 (current) pairs with both 2.1.12.x and 2.1.13.0 nodes. The next Bisq Connect release will require a 2.1.13.0 node, so update the node first
  • Bisq Easy 0.14.1 (Android, embedded node) already ships these Tor fixes — no action needed
  • Pairing Bisq Connect with Bisq 2 Desktop? Update the desktop to v2.1.13

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#6133 ⏳ awaiting Umbrel review
Umbrel community store Update offered in the Bisq Network community store bisq2-umbrel#9 ⏳ pending merge
StartOS community registry Update offered by StartOS once Start9 tags v2.1.13.0_0 Start9-Community/bisq2-startos#7 ⏳ awaiting Start9 review + tag
StartOS package mirror Source mirror only, no user action bisq2-startos#6 ⏳ pending merge
Docker docker pull ghcr.io/bisq-network/bisq2-api:2.1.13.0 and restart — ✅ available now

📦 Images

Image Reference
Node ghcr.io/bisq-network/bisq2-api:2.1.13.0@sha256:caeebd10b6e232ea8567941e4c6594b4000b5771c9e53cef25cf9b9766d5570d
Web UI sidecar (Umbrel) ghcr.io/bisq-network/bisq2-api-web-ui:2.1.13.0@sha256:9f818767031aeef0ae6018dfd1c02dd0fad392207013e4a6b6a12f6161f6fd27

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.13-1~jammy+1 on both architectures. Build: release run.

What to do

  1. Umbrel: install the update from the App Store when it appears (or add the community store to get it earlier)
  2. StartOS: install the update from the Community Registry when it appears
  3. Docker: pull the new tag (digest above) and restart the container; your data directory is unchanged
  4. Open Bisq Connect and confirm it reports the node on API 2.1.13; keep the app updated
Assets 2
Loading