This release is not stable, please revert to v1.2.7 if you are seeing issues during startup
Binaries have been removed until #4052 is fixed and released in a hotfix
Release notes
This release is, once again, packed with bug fixes and improvements. Most notably, it checks for errors in local Bitcoin Core node configuration and reduces the intervals in which users can trigger a trade process refresh.
UI
- Improve wording for local BTC node reminder in
Settings > Network info - Display 2 decimal places for fiat trading fees
- Fix checkbox handling in
My Open Offers
Trading
- Reduce time until trade process refresh is possible: 1, 2
- Update owner address of offer to new hidden service files
- Add ARS as supported currency for MoneyGram
Wallet
Performance
Privacy
- Remove unused uid in fee provider service
- Fix incorrect deletion of hidden service directory when using --appDataDir
Configuration
Network
- Update URL for mempool.ninja blockchain explorer
- Fix nginx.conf for collectd so it only listens on 127.0.0.1
- Fix CoinMarketCap API issues: 1, 2, 3
- Moved node2.emzy.de to a new host
Monitor
Support
- Log delayed payout transaction bytes as soon as it's signed during trade initialization
- Dump delayed payout transactions of both pending and failed trades if flag is set
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.2.8.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.2.8.jar
The output need to match the value from the Bisq-1.2.8.jar.txt file.
Known issues with installation
macOS Catalina:
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.2.8.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.2.8 or later. You can verify the binary the same way as you do with the Bisq application.