A newer version is already available! Please don’t use this version anymore.
Release notes
This release ships the official beta release for the Bisq API! It has been tested on mainnet, but is still in beta, so please be careful.
Other highlights: absolute minimum deposits have now been lowered from 0.006 BTC to 0.001 BTC. Maker and taker fee transactions are now verified via mempool.space to reduce trade issues, and mediation and arbitration were improved as well. And as always, there are many bug fixes and refinements.
Also important: this release ships part of 1 of 2 for BSQ SegWit implementation. It prepares the network for handling SegWit BSQ transactions (activation block is 680300, around 2021/04/25 -- all full nodes should update to 1.6.0 before that time). Shortly after this activation point, the wallet code (#5109) will be merged into master for testing so that the full BSQ SegWit update is shipped in the following release.
DAO
UI
- Update commands for mediator/refund agent registration
- Fix copy of BankName value + BranchId/BankId
- Changes "Verify result" to "Check signature"
- Fix dark mode readability of specific texts
- Fix Set Password text button
- Fix key shortcut documentation when using CMD+Y
- Replace Slack with Keybase
- Fix opening of proposal links in DAO on Windows
- Fix length check text on manual payout tool
Trading
- Lower min deposit to 0.001 BTC
- Add pop-up warning for trading with risky payment methods
- Verify maker & taker fee transactions via Mempool lookup
- Fee validation leniency using old DAO param values
- Improve portfolio history
- Add NGN as a default currency
- Add pay from BSQ wallet button
- Prevent trading when not connected to the Bitcoin network
- Fix Multiple Warnings on Enable All Offers
Wallet
Reliability
Mediation/Arbitration
- Improve chat functionality of mediation/arbitration: 1, 2
- Improve mediation tools / logging
API
- Add long running api tests
- Improve takeoffer error handing
- Disambiguate payment acct json form's "country" field
- Improve apitest docs
- Document test harness dispute agent registration
- Avoid null pointer exception due to null fee while wrapping tx in TxInfo
- Prevent creation of new offers with incompatible payment accounts
- Fix CLI number opt validation, improve server-not-up msg
- Fix call rate metering interceptor bug
- Fix API startup's wallet.init failure when wallet is encrypted
- Improve gRPC server error logging
- Display buyer's cost in api's gettrade output
- Refactor apitest cases to use GrpcClient
- Refactor grpc stub boilerplate from CliMain to GrpcClient
- Adjust api to new minimum fee per vbyte
- Add CLI testing bot to :apitest
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.6.0.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.6.0.jar
The output need to match the value from the Bisq-1.6.0.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.6.0.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:
- @BtcContributor
- @cd2357
- @chimp1984
- @ripcurlx
- @ghubstan
- @huey735
- @JaredBoone
- @jmacxx
- @wallclockbuilder
- @sqrrm
- @stejbac
A special thanks to our first time contributor:
As well as to everyone that helped with translations on Transifex.