A newer version is already available! Please don’t use this version anymore.
This is a hotfix that helps everyone participating in the DAO to determine the vote result for voting cycle 12. Additionally it also removes ghost offers from the offer book.
If you see conflicts with a seed node in the DAO > Network Monitor you will see a Resync DAO State button. Please click on that and restart. After that no conflicts with seed nodes should be displayed anymore.
- Improve permutation algorithm to avoid running into limit while trying to find majority hash
- Reject expired data
Here are the release notes from v1.3.2:
Release notes
This release is packed with bug fixes and improvements. Most notably, it improves the reliability of the wallet and uses Tor onion services version 3 for new data directories.
UI
- Add volume weighted average BSQ price
- Only use InputValidation when formatting voting stake
- Make prompt text for passwords readable in dark mode
- Size the offer book on window activation
- Sorting order of offers appropriately by min/max range
Trading
- Unfail trades if possible (reattach addresses)
- Add holder name for new Faster Payments accounts
- Replace the Get Support button with Open Trader Chat until trade period is over
- Add signed witness filter
- Improve handling of filtered offers and unsupported payment methods
Wallet
- Limit number of unconfirmed offers
- Prevent dust outputs from being created during the trade process
- Prevent dust outputs from being created during withdraw from wallet
Performance/Reliability
- Improve avoid standby feature
- Make UserThread::run* methods thread safe
- Make serialisation in FileManager::saveToFile thread-safe
- Added graceful shutdown hook
Privacy
Configuration
- Allow IPv6 connections to Bitcoin nodes
- Prevent incorrect usage of
--useLocalhostForP2Poption - Avoid startup failure when bannedSeedNodes arg is empty
- Limit system ram to 4GB
Network
- Replace a @wiz v2 seednode with a new v3 seednode
- Remove a @wiz bitcoin node to reduce total count to 16 nodes
- Add onion address for @robkaandorp's btcnode
Assets
No assets were added.
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-1.3.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/Java/Bisq-1.3.4.jar
The output need to match the value from the Bisq-1.3.4.jar.txt file.
Known issues with installation
macOS Catalina:
Bisq can't be opened because Apple cannot check it for malicious software
This happens the first time Bisq is run on macOS Catalina. It is because a new security feature in Catalina has newer requirements of how apps are packaged. We are working on ways to address this (see #3402 and #4196 for details).
Workaround: Right click on the installed Bisq app > Click Open (warning popup shown again, but with new button available) > Click Open
Bisq would like to receive keystrokes from any application.
Discussed in issue #3373, you will see a permission request in the latest macOS version that Bisq wants to receive keystrokes from any application. Unfortunately that is an issue for all Java applications that are run on Catalina right now. We are investigating already how to solve this issue and will fix in one of our next updates.
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-1.3.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.
Cleanup tool for saved trades that failed market price check
With this release we are also shipping a cleanup tool (Bisq-cleanup-trades*). It will remove corrupt trade entries added due to bug #2924. Install and run once, it will shut down automatically, then install version 1.3.4 or later. You can verify the binary the same way as you do with the Bisq application.