A newer version is already available! Please don’t use this version anymore.
This is a hotfix release mainly covering following issue:
DAO data store wasn't properly synchronized (again)
Here are the release notes from v1.1.3:
Release notes
This is a bug fix and network improvement release. You'll see faster startup and synchronization times and it includes lots of smaller bug fixes and improvements as well.
DAO
- Handling of revealing of late votes
- Limit BSQ validator to 10M BSQ
- Display changed param value at proposal time
- Handle null tx for unconfirmed BSQ change output
- Don't dump blockchain data during initial parsing
- Limit number of blocks sent in GetBlocksResponse
- Fixes for initial block sync
UI
Trading
- Fix acknowledgement message for available offers
- Use tempTradingPeerNodeAddress if the trade doesn't have a trading peer set yet
- Fix offer editing for low volume offers
- Fix missing payment info on SEPA Instant trades
- Exclude non executed BSQ trade
Wallet
- Update BitcoinJ checkpoint files
- Wait for initialized wallet before processing dispute msgs
- Add option to ignore local bitcoin node
Network
Monitoring
Development
Assets
Added four new asset: Genesis (GENX), Know Your Developer (KYD), Myce (YCE), Starwels (USDH)
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.1.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.1.5.jar
The output need to match the value from the Bisq-1.1.5.jar.txt file.
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/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.1.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.
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.1.5 or later. You can verify the binary the same way as you do with the Bisq application.