Releases: bisq-network/bisq
v1.6.2
A newer version is already available! Please don’t use this version anymore.
This is a hotfix release that fixes an issue with SPV resync introduced in v1.6.0 and fixes a minor bug in the portfolio view when price nodes aren't available.
For more details please see https://github.com/bisq-network/bisq/milestone/56?closed=1
Here are the release notes from v1.6.0:
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
- Fix ClassCastError in portfolio history summary popup
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
- Allow default fee values in leniency checks
- 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
Privacy
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.2.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.2.jar
The output need to match the value from the Bisq-1.6.2.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.2.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:
- @BtcContributor:
- Fix Set Password text button
- Fix opening of proposal links in DAO on Windows
- [Fix dark mode readibility of specific texts](https://github.com/bisq-network/bisq/pu...
v1.6.1
A newer version is already available! Please don’t use this version anymore.
This is a follow-up release that allows default fee values in leniency checks, fixes an issue in the the new portfolio history popup and upgrades to the latest Tor version v0.4.5.7 that fixes two important denial-of-service bugs in earlier versions of Tor.
For more details please see https://github.com/bisq-network/bisq/milestone/54?closed=1
Here are the release notes from v1.6.0:
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.1.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.1.jar
The output need to match the value from the Bisq-1.6.1.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.1.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:
v1.6.0
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](https://transifex.com/bisq/bi...
v1.5.9
A newer version is already available! Please don’t use this version anymore.
This is a hotfix release that fixes an issue when trading messages are resent on application startup.
Here are the release notes from v1.5.8:
Release notes
This release improves DAO charts to make it easier to drill into the DAO economics, it ships improvements for Amazon eGift Cards, adds new SEPA countries and the possibility to try out pre-release versions without the need of manual downloads and verification (see settings)...and lots of bug fixes and improvements across the board.
DAO
UI
- Add colored decimal places with zeros for dark mode
- Fix stale trade statistics list view when new entries arrive
Trading
- Specify Amazon eGift Card country
- Add four SEPA payment account countries: AD, SM, VA, JE
- "Cash by Mail" instructions improvements
- Fix startup error: "You must have bootstrapped before adding data to the P2P network"
- Fix NullPointerException in trader chat when trade contract is not set
- Fix NullPointerException at offer entry when trading account is switched
- Prevent erroneous logging of 'SignaturePubKey in message does not match'
Wallet
- Check wallet is available and/or unlocked when creating an offer
- Obtain the minimum withdrawal fee from mempool.space
Reliability
- New Feature: Pre-release notifications
- Fix multiple request preliminary data calls
- Fix initialization ordering issue
Privacy
Mediation/Arbitration
- Refund agent payout to use withdrawal fee rate from settings
- Manual payout tool: prevent absurdly high fee payout
- Fix Mediator's name
Performance
Network
API
- Add api method 'stop'
- Api v1 Beta Test Guide
- Add core api method help docs
- Add apitest rolling offer simulation script
- Define gRPC api call rate constraints
- Fix method help typos
- Fix find pid on OSX
Development
- Remove unused BalanceWithConfirmationTextField
- Avoid reverse DNS lookup in BtcNodeConverterTest
- Fix log message when opening browser link
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.9.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.9.jar
The output need to match the value from the Bisq-1.5.9.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.9.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:
- @chimp1984
- @ripcurlx
- @ghubstan
- @huey735
- @jakub_cz
- @jmacxx
- @sqrrm
- @stejbac
- @bisqubutor
A special thanks to our first time contributor:
As well as to everyone that helped with translations on Transifex.
v1.5.8
A newer version is already available! Please don’t use this version anymore.
This is a follow-up release that obtains the minimum withdrawal fee from mempool.space to avoid transactions being rejected by the bitcoin network for having too low a fee.
Here are the release notes from v1.5.7:
Release notes
This release improves DAO charts to make it easier to drill into the DAO economics, it ships improvements for Amazon eGift Cards, adds new SEPA countries and the possibility to try out pre-release versions without the need of manual downloads and verification (see settings)...and lots of bug fixes and improvements across the board.
DAO
UI
- Add colored decimal places with zeros for dark mode
- Fix stale trade statistics list view when new entries arrive
Trading
- Specify Amazon eGift Card country
- Add four SEPA payment account countries: AD, SM, VA, JE
- "Cash by Mail" instructions improvements
- Fix startup error: "You must have bootstrapped before adding data to the P2P network"
- Fix NullPointerException in trader chat when trade contract is not set
- Fix NullPointerException at offer entry when trading account is switched
- Prevent erroneous logging of 'SignaturePubKey in message does not match'
Wallet
- Check wallet is available and/or unlocked when creating an offer
- Increase min withdrawal tx fee to 15 sats/vB
Reliability
- New Feature: Pre-release notifications
- Fix multiple request preliminary data calls
- Fix initialization ordering issue
Privacy
Mediation/Arbitration
- Refund agent payout to use withdrawal fee rate from settings
- Manual payout tool: prevent absurdly high fee payout
- Fix Mediator's name
Performance
Network
API
- Add api method 'stop'
- Api v1 Beta Test Guide
- Add core api method help docs
- Add apitest rolling offer simulation script
- Define gRPC api call rate constraints
- Fix method help typos
- Fix find pid on OSX
Development
- Remove unused BalanceWithConfirmationTextField
- Avoid reverse DNS lookup in BtcNodeConverterTest
- Fix log message when opening browser link
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.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.5.8.jar
The output need to match the value from the Bisq-1.5.8.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.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.
Credits
Thanks to everyone who directly contributed to this release:
- @chimp1984
- @ripcurlx
- @ghubstan
- @huey735
- @jakub_cz
- @jmacxx
- @sqrrm
- @stejbac
- @bisqubutor
A special thanks to our first time contributor:
As well as to everyone that helped with translations on Transifex.
v1.5.7
A newer version is already available! Please don’t use this version anymore.
Release notes
This release improves DAO charts to make it easier to drill into the DAO economics, it ships improvements for Amazon eGift Cards, adds new SEPA countries and the possibility to try out pre-release versions without the need of manual downloads and verification (see settings)...and lots of bug fixes and improvements across the board.
DAO
UI
- Add colored decimal places with zeros for dark mode
- Fix stale trade statistics list view when new entries arrive
Trading
- Specify Amazon eGift Card country
- Add four SEPA payment account countries: AD, SM, VA, JE
- "Cash by Mail" instructions improvements
- Fix startup error: "You must have bootstrapped before adding data to the P2P network"
- Fix NullPointerException in trader chat when trade contract is not set
- Fix NullPointerException at offer entry when trading account is switched
- Prevent erroneous logging of 'SignaturePubKey in message does not match'
Wallet
- Check wallet is available and/or unlocked when creating an offer
- Increase min withdrawal tx fee to 15 sats/vB
Reliability
- New Feature: Pre-release notifications
- Fix multiple request preliminary data calls
- Fix initialization ordering issue
Privacy
Mediation/Arbitration
- Refund agent payout to use withdrawal fee rate from settings
- Manual payout tool: prevent absurdly high fee payout
- Fix Mediator's name
Performance
Network
API
- Add api method 'stop'
- Api v1 Beta Test Guide
- Add core api method help docs
- Add apitest rolling offer simulation script
- Define gRPC api call rate constraints
- Fix method help typos
- Fix find pid on OSX
Development
- Remove unused BalanceWithConfirmationTextField
- Avoid reverse DNS lookup in BtcNodeConverterTest
- Fix log message when opening browser link
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.7.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.7.jar
The output need to match the value from the Bisq-1.5.7.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.7.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:
- @chimp1984
- @ripcurlx
- @ghubstan
- @huey735
- @jakub_cz
- @jmacxx
- @sqrrm
- @stejbac
- @bisqubutor
A special thanks to our first time contributor:
As well as to everyone that helped with translations on Transifex.
v1.5.6
A newer version is already available! Please don’t use this version anymore.
This is a hotfix that fixes a startup issue with limit offers.
Here are the release notes from v1.5.5:
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
-ignoreLocalBtcNode
startup 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.6.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.6.jar
The output need to match the value from the Bisq-1.5.6.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.6.deb
sudo tar Jxvf data.tar.xz
sudo cp -rp opt/Bisq /opt/
That instruction is not tested on many di...
v1.5.5
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
-ignoreLocalBtcNode
startup 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 contribut...
v1.5.4
A newer version is already available! Please don’t use this version anymore.
This is a hotfix that improves DoS protection.
For a full list of changes please see milestone v1.5.4 for more details.
Here are the release notes from v1.5.2:
Release notes
This release improves transaction handling in certain edge cases and contains multiple fixes making Bisq more reliable in general. There are also some notable UI updates for the payment accounts and offer book screens.
DAO
UI
- Sort payment methods by display string not by id
- Make sign age column sortable
- Improve UI/UX for account aging column in 'Offers' section of GUI
- Fix sorting of table columns in portfolio section
- Improve funds and portfolio screens
- Account management usability improvements
- Improve usage of available space in accounts section
- Improved Offer Book chart outlier filter
- Prevent annoying popup errors for unhandled systray exception.
- Fix warning about rejected transaction
- Improve startup info display
- Rename getsAll payout option string
- Fix private notification style issue in dark mode
Trading
- Handle unconfirmed deposit tx in pending trades
- Fix bug with maker fee tx at create offer
- Detect and handle invalid maker fee tx
- Detect missing deposit tx to allow moving to failed trades
- Allow take offer in case account age witness is not found and trade amount is small
- Add taker check for deposit amount
- Don't allow trade start if BitcoinJ is not fully synced
- Show price deviation in % for fixed price offers and BSQ
- Show price deviation in portfolio open offers and history view
- Improve TransferWise account wording and defaults currency selections
- Remove NGN (Nigerian Naira) as their central bank blocked Transferwise
- Add extra note for Amazon gift cards
- Add memo field at withdraw to external wallet screen after successful trade
- Create JSON files of actively traded crypto and fiat assets
Wallet
- Fix emergency payout
- Prompt for confirmation before initiating SPV resync
- Add encrypted wallet password prompt when sending funds from BSQ wallet
- Add wallet info view
Reliability
- Add tx broadcast to mempool explorer api
- Refactor http client
- Prevent that we write data at shutdown before we have read the data
- Improve shutdown routine
- Add 1 sec delay before calling exit
- Call completeHandler if services in store services is empty
Mediation/Arbitration
- Privacy improvements for manual payout
- Option to sign single account for market bootstrapping
- Allow sending private notifications from avatar icon at trade
- Add error log for dispute failure
Performance
- Various small performance improvements
- Cache results of isFiatCurrency and isCryptoCurrency
- Replace use of Collections to FXCollections in desktop
Network
- Revert TTL of mailbox messages to original value of 15 days.
- Improve filter
- Use data store diffs also for AccountAgeWitnesses
- Remove m52go btc node ip
- In seednode installer, don't run random shell script to install git lfs
API
- Add api method 'sendbtc'
- Add api method 'getpaymentacctform'
- Add api method 'getpaymentmethods'
- Add api method 'getbalance(s)'
- Add api method 'confirmpaymentreceived'
- Add api method 'confirmpaymentsent'
- Add api method 'takeoffer'
- Add api method 'getunusedbsqaddress': 1, 2
- Add tx fee rate api methods: gettxfeerate, settxfeerate, unsettxfeerate
- Shut down rpc service at app shut down routine
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.4.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.4.jar
The output need to match the value from the Bisq-1.5.4.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 ...
v1.5.3
A newer version is already available! Please don’t use this version anymore.
This is a hotfix that introduces DoS protection.
Here are the release notes from v1.5.2:
Release notes
This release improves transaction handling in certain edge cases and contains multiple fixes making Bisq more reliable in general. There are also some notable UI updates for the payment accounts and offer book screens.
DAO
UI
- Sort payment methods by display string not by id
- Make sign age column sortable
- Improve UI/UX for account aging column in 'Offers' section of GUI
- Fix sorting of table columns in portfolio section
- Improve funds and portfolio screens
- Account management usability improvements
- Improve usage of available space in accounts section
- Improved Offer Book chart outlier filter
- Prevent annoying popup errors for unhandled systray exception.
- Fix warning about rejected transaction
- Improve startup info display
- Rename getsAll payout option string
- Fix private notification style issue in dark mode
Trading
- Handle unconfirmed deposit tx in pending trades
- Fix bug with maker fee tx at create offer
- Detect and handle invalid maker fee tx
- Detect missing deposit tx to allow moving to failed trades
- Allow take offer in case account age witness is not found and trade amount is small
- Add taker check for deposit amount
- Don't allow trade start if BitcoinJ is not fully synced
- Show price deviation in % for fixed price offers and BSQ
- Show price deviation in portfolio open offers and history view
- Improve TransferWise account wording and defaults currency selections
- Remove NGN (Nigerian Naira) as their central bank blocked Transferwise
- Add extra note for Amazon gift cards
- Add memo field at withdraw to external wallet screen after successful trade
- Create JSON files of actively traded crypto and fiat assets
Wallet
- Fix emergency payout
- Prompt for confirmation before initiating SPV resync
- Add encrypted wallet password prompt when sending funds from BSQ wallet
- Add wallet info view
Reliability
- Add tx broadcast to mempool explorer api
- Refactor http client
- Prevent that we write data at shutdown before we have read the data
- Improve shutdown routine
- Add 1 sec delay before calling exit
- Call completeHandler if services in store services is empty
Mediation/Arbitration
- Privacy improvements for manual payout
- Option to sign single account for market bootstrapping
- Allow sending private notifications from avatar icon at trade
- Add error log for dispute failure
Performance
- Various small performance improvements
- Cache results of isFiatCurrency and isCryptoCurrency
- Replace use of Collections to FXCollections in desktop
Network
- Revert TTL of mailbox messages to original value of 15 days.
- Improve filter
- Use data store diffs also for AccountAgeWitnesses
- Remove m52go btc node ip
- In seednode installer, don't run random shell script to install git lfs
API
- Add api method 'sendbtc'
- Add api method 'getpaymentacctform'
- Add api method 'getpaymentmethods'
- Add api method 'getbalance(s)'
- Add api method 'confirmpaymentreceived'
- Add api method 'confirmpaymentsent'
- Add api method 'takeoffer'
- Add api method 'getunusedbsqaddress': 1, 2
- Add tx fee rate api methods: gettxfeerate, settxfeerate, unsettxfeerate
- Shut down rpc service at app shut down routine
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.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/Java/Bisq-1.5.3.jar
The output need to match the value from the Bisq-1.5.3.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:
The binary of this version is not signed by a code signing certificate right now as it was in previous versions. This is because of an expired certificate that wasn't renewed in-time. It will be signed on 28th of Dec with the newly received certificate and this note will be removed afterwards. The Windows binary was signed on Dec 27th and uploaded together with an updated signature file.
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<userna...