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).
Improvements
- Clear payment account payload info from closed trades
- Allow dispute to be closed if trade has paid out
- Include penalty for exceeding transfer limits
- Show buyer/seller in terms of BTC
- Show signed payment account status when applicable in Trade & Dispute information screens
- Show proposal transaction ID with explore and copy icons
- Sign/Verify message for DAO bonded roles
- Obtain trade fee settings from filter
- Warn and prompt for password before showing wallet keys
- Add ability to copy popup text to clipboard
- Add support/help links on the UI
- Add filter option to lists
- Improve text and icon colors for disabled offers
- Remove references to Keybase and switch to Matrix
- Improve BSQ swap error messaging & DAO resync popup
Bug fixes
- Fix exception: heightOfLastBlock must match chainHeight
- Fix issue selecting specific BSQ UTXO for sending BSQ
- Fix error in failed trades view when trade contract is null
- Fix NullPointerException when editing a new payment account
- Fix unhandled exception when locale specifies unknown country/region code.
- Fix column sorting
- Fix sorting on bonded roles view
- Prevent reset offer values after switch to same currency payment account
- Filter out the BSQ swap payment method from dropdown on edit/duplicate offer
- Fix CSV export issue on open offers view
- Enable Tor bridges set in application settings
- Get payment method ID from offerPayload: 1, 2
- Disable roll over popups in combobox item renderers.
Development & Documentation
- API: Add API
gettradesmethod - API: Fix FeeService NullPointerException
- Update copyright string for Windows
- Update copyright string for macOS
- Cleanup: remove unused classes
- Improve instructions and wording
- Update hostname of BSQ explorer mempool.emzy.de
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.8.3.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.8.3-all.jar
The output need to match the value from the Bisq-1.8.3.jar.txt file.
There are three hashes within the Bisq-1.8.3.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.3 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.8.3.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:
A special thanks to our first time contributors:
As well as to everyone that helped with translations on Transifex.