A newer version is already available! Please don’t use this version anymore.
Release notes
This release enables you to connect to a Bitcoin Core node with a Tor v3 address.
Tor v2 addresses will not be supported after October 15th, so please update your Bitcoin and Bisq nodes ASAP.
This version also introduces three new payment methods: SWIFT, Paysera, and Paxum. As always, there are many additional bug fixes and minor improvements across the board as well.
Improvements
- Add bitcoinj Tor v3 support
- Update to BTC node Tor v3 onions
- Add SWIFT payment method
- Add Payment Methods: Paysera and Paxum
- Allow user to initiate arbitration once locktime has expired
- Update @leo816's onion address
- Improve japanese bank branch validation
- Reduce # of hash calculations in UI OfferBook view
Bug fixes
Development & Documentation
- Override/disable gRPC call rate meters in test harness driver
- Add new api method
editoffer: 1, 2, 3
New Assets
No new assets were added.
Verification
For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file
Url of the signing key (Christoph Atteneder): https://bisq.network/pubkey/29CDFD3B.asc
Full fingerprint: CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B
Import the key:
curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import
GPG prints a confusion warning: "This key is not certified with a trusted signature!" - See https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key 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.7.4.dmg)
Verify jar file inside binary:
You can verify on OSX the jar file with:
shasum -a256 [PATH TO BISQ APP]/Bisq.app/Contents/app/desktop-1.7.4-all.jar
The output need to match the value from the Bisq-1.7.4.jar.txt file.
There are three hashes within the Bisq-1.7.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 11.0.10 and the v1.7.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
Windows:
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):
C:\Users<username>\AppData\Local\Bisq
[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)
Linux:
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.7.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.
Credits
Thanks to everyone who directly contributed to this release:
As well as to everyone that helped with translations on Transifex.