Bisq v1.8.4 released

This is a follow-up release that fixes the news badge on Settings for existing Bisq users and handles an additional case where the DAO needs resync.

See v1.8.4 Milestone · GitHub for more details.

Here are the release notes from v1.8.3:

Release notes

This release improves privacy by automatically deleting past trade data, improves the UI in many places, and fixes bugs across the board (as always).


Bug fixes

Development & Documentation

New Assets

No new assets were added.


For a detailed description on how to verify your Bisq installer please have a look at our wiki: Downloading and installing - Bisq Wiki

Url of the signing key (Christoph Atteneder):
Full fingerprint: CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B

Import the key:
curl | gpg --import
GPG prints a confusion warning: “This key is not certified with a trusted signature!” - See How to verify an imported GPG key - Server Fault for background information what it means.

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.8.4.dmg)

Verify jar file inside binary:
You can verify on OSX the jar file with:
shasum -a256 [PATH TO BISQ APP]/
The output need to match the value from the Bisq-1.8.4.jar.txt file.

There are three hashes within the Bisq-1.8.4.jar.txt file (macOS, Windows, Linux).
If you want to reproduce and verify the hash of the jar file locally, you need to do so on Windows or Linux using Java 15.0.5 and the v1.8.4 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

Known issues with installation


There is a known issue with Anti Virus software. We got several reports from users running into different problems. Either the AV software blocks Bisq or Tor, delete files in the data directory [2] or app directory [1]) or cause such a long delay at startup that Tor gets terminated and a file remains locked which can cause that Bisq cannot be started afterwards. To resolve that you need to restart Windows then the lock get released. We are working on solutions to fix those issues.

If you use Crypto currencies on your Windows system be aware that Windows is much more vulnerable to malware than Linux or OSX. Consider to use a dedicated non-Windows system when dealing with cryptocurrencies.

[1] Application directory (contains application installation files):

[2] Data directory (contains all Bisq data including wallet):
C:\Users<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)


Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq/bin/Bisq

If your Linux distro does not support .deb files please follow this instruction:

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.8.4.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

That instruction is not tested on many different distros. If you encounter problems please report it in a Github issue so we can improve it.


Thanks to everyone who directly contributed to this release:

A special thanks to our first time contributors:

As well as to everyone that helped with translations on Transifex.