A newer version is already available! Please don’t use this version anymore.
Release notes
ATTENTION: This release changes the trade protocol.
DO NOT specify trade ID or any other value in the 'reason for payment' field.
LEAVE IT BLANK.
If it is mandatory for your payment service add a dash character ('-') or coordinate with your counterparty over trader chat to agree on a reason for payment.
This change reduces the chances that certain payment accounts get flagged.
Please see #2869 for more details on this change.
This release introduces the option to create limit offers to be able to deactivate an offer if a certain price limit is reached. It also introduces cash-by-mail as a new payment method. In addition to multiple minor UI changes, we squashed lots of bugs and improved reliability and performance of the app across the board.
DAO
- Add CSV export to BSQ transaction view
- Move BSQ price in USD at first row
- Add indication of last GH CR issue
- Fix request amount bounds in ReimbursementValidator
UI
- Add toggle for displaying volume in trade statistics chart in USD
- Add toggle for hiding not takable offers
- Add a 'payment method details' screen
- Improve trade fee display at create and take offer screens and popups
- Disable CPU-intensive animations
- Improve popup text in case a local node is detected
- Keep main navigation items left aligned
- Reword "trade started" popup messages per suggestion
- Update translations and fix a broken German translation
- Show stacktrace in error popup at view exceptions
- Fix missing apostrophe in Withdrawal view
- Remove redundant popup when cancelling an offer
Trading
- Change rule for 'reason for payment' field to not use trade ID but leave it empty
- Deactivate open offer if trigger price is reached
- Add payment method "Cash by mail"
- Change trade period for TransferWise from 1 day to 4 days
- Add option to hide non supported payment methods
- Select show-all currencies if TransferWise is selected
Wallet
- Show a confirmation of successfully sending BTC or BSQ from wallet
- Improve path text on wallet info screen
- Fix broken
-ignoreLocalBtcNodestartup option
Reliability
- Persist and republish mailbox messages
- Request only non-seed nodes if no seed nodes are available
- Access concrete data stores
- Improve offer publishing
- Improve getBlocks request handling
- Improve CleanupMailboxMessages
- Fix premature disconnections from seeds
Mediation/Arbitration
Performance
- Persist failed attempts of decrypting mailbox messages
- Cache signature verification results
- Cache results in account witness domain
Network
- Add 4 old v2 seed nodes
- Add option to prevent periodic shutdown for seed nodes
- Add filter support on network level
- Improve cleanup tor dir at seeds
- Avoid resync from genesis in case of dao state issues
- Update inventory code
API
- Add new api methods 'getmyoffers' and 'getmyoffer'
- Add new api method 'sendbtc'
- Add new api method 'gettransaction'
- Add optional txFeeRate parameter to api 'sendbsq'
- Support tx memo field for btc withdrawals from api
- Add protection tools
- Integrate new protection tools into api's offer & trade services
- Prevent excessive api calls
- Use posix-style CLI opts, provide method help
- Add api trade simulation scripts
- Pass hash to bitcoind blocknotify script
- Stub out support for OpenOffer's triggerPrice in api
- Use Bisq's UserThread.executor in gRPC server
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.5.5.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.5.5.jar
The output need to match the value from the Bisq-1.5.5.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.5.5.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.