A newer version is already available! Please don’t use this version anymore.
Release notes
This release is not only a bug fix release following v0.9.0 (Windows installation issues, switching between BTC networks not working,...), but contains also lots of improvements as well. Thanks to everyone who started testing of the Bisq DAO on Testnet already!
As we have updated to Java 10 and Oracle has dropped support for 32 bit Operating systems we cannot provide 32 bit binaries anymore.
Bisq DAO (on Testnet)
- Fix selection of BTC testnet in Settings
- Fix reorg issues
- Improve handling of reorgs
- Handle RPC errors
- UI improvements in Voting screen
- Fix validatation of display fields in proposal display
- Use animation for vote button
- Use uppercase in submenu items
Trading
- Decrease the price tolerance window in offers
- Remove testnet and regtest for DASH and LTC
- Remove BCH
- Show rounded trade volume in contracts
Payment methods
UI
- Improve startup time by updating checkpoint files
- Left align table columns to improve readability
- Refine various UI strings
- Bug fix: Close window without triggering action on ESC
- Bug fix: Views are sometimes not updated when switching quickly between sub sections
- Bug fix: Prevent duplicate popup windows
- Bug fix: Update validation of volume when percentage price is set
Privacy/Security
Development
- Consolidate install_java.sh scripts
- Update install_java.bat
- Bug fix: Surgical fix to default command line parameters
Installation
Assets
- Removed Bitcoin Cash (BCH) based on stakeholder voting
Verification
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-0.9.1.dmg)
Verify jar file inside binary:
You can verify on OSX the jar file with:
shasum -a256 [PATH TO BISQ APP]/Bisq.app/Contents/Java/Bisq-0.9.1.jar
The output need to match the value from the Bisq-0.9.1.jar.txt file.
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/Bisq
If your Linux distro does not support .deb files please follow this instruction:
cd ~/Downloads
mkdir tmp
cd tmp
ar x ../Bisq-64bit-0.9.1.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.