A newer version is already available! Please don’t use this version anymore.
Release notes
This release brings auto-confirmation for Monero trades, makes usernames required for Revolut payments (to reduce disputes, based on mediator feedback), and improves connectivity within the network. It also improves reliability, please update to this version to avoid network issues!
DAO
UI
- Fix intermittent blank price cells in offer book view
- Improve warning message regarding insufficient BSQ
- Add more detailed network statistics
- Only show signing state if signing for payment method is required
Trading
- Add auto-confirm feature for Monero
- Add support for user name for Revolut accounts
- Add check for option trade for dispute cases
- Fix null pointer in case if selectedMarketPrice is null
- Reload dispute layout on reopen
- Improve dispute views
- Update GUI labels to reflect multiple rate providers
- Fix bug with all mobile notifications for disputes are sent at startup.
- Remove offer from takers offerbook after take offer is completed
- Remove 'monero:' prefix when adding a XMR account
Reliability
- Optimize application shutdown
- Increase timeouts: 1, 2
- Revert usage of caffeinate on OSX
- Make moving average code more safe
Network
- Filter improvements
- Bundle messages at broadcast
- Tweak seednode bitcoin.conf, remove timeout, separate testnet block
- Improve restarting of seednodes
- Reduce seednode maxconnections setting from 50 to 40 in bisq.env
- Add mempool.bisq.services explorer and mempool fee estimation provider
- Add mempool.ninja to pricenodes as 3rd mempool fee estimation backend
- Update all Pricenodes with new Tor V3 onions
- Add new Monero Explorer node77.monero.wiz.biz with onion
- Update old Bisq Explorer URLs with new Mempool Explorer URLs, tweak strings
Development
Assets
No new assets.
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.9.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.9.jar
The output need to match the value from the Bisq-1.3.9.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.9.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.9 or later. You can verify the binary the same way as you do with the Bisq application.