v1.5.2

A newer version is already available! Please don’t use this version anymore.

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

• Fix bsq to fiat calculation
• Use 30 days average USD/BSQ price for market cap

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

• Don't shut down seed in regtest mode if all connections lost

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.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.5.2.jar
The output need to match the value from the Bisq-1.5.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:

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<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)

Linux:

Hint for Debian users:...

v1.5.1

A newer version is already available! Please don’t use this version anymore.

This is a hotfix that fixes critical bugs that can occur during the trade process!

For a full list of changes please see milestone v1.5.1 for more details.

Here are the release notes from v1.5.0:

Release notes

This release finally brings SegWit to Bisq's trade protocol. It also implements fee optimizations enabled by SegWit, so mining fees for all BTC transactions are lower.

There are also some notable trading-related updates: you can now edit pricing and payment methods of your live offers; account limits have been simplified (and removed where unneeded); and 3 new payment methods were added (Australian PayID, TransferWise and Amazon gift cards).

The SegWit integration wouldn't have been possible without the anonymous sponsor who pre-funded the project, so big thanks to them! If you might be interested in pre-funding a specific feature, please contact us on Keybase in the #projects channel. Bisq is a critical element of the Bitcoin ecosystem and could really use your help.

DAO

• Use LegacyAddress instead of Address for BSQ
• Remove outliers when calculating BSQ rate
• Hide proposal delete button

UI

• Improve labeling of charts: 1, 2
• Cleanup user interface elements in Send Funds screen
• Add export to csv hyperlink (as button takes too much vertical space)

Trading

• Use SegWit for the trade protocol
• Simplify limits for signed and unsigned accounts
• Update Edit Offer to allow for change of market and payment method
• Add new payment method: Australian PayID
• Add new payment method: TransferWise
• Add new payment method: Amazon Gift Cards
• Fix bug with reading historical data

Wallet

• Add SegWit fee estimation: 1, 2
• Speed up restore from seed
• Allow user-defined block explorers
• Show current tx fee rate on main screen

Privacy

• Update netlayer references to Bisq repository

Network

• Remove HitBTC as a pricenode data provider
• Add new burningman address for delayed payout txs
• Reduce seednode default max connections to 20
• Show past deviation in monitor
• Clean up mailbox messages for closed trades
• Admin filter for auto-confirmation service addresses

API

• Implement 'canceloffer' api method
• Implement api methods 'keepfunds', 'withdrawfunds'
• Implement 'gettrade' api method
• Implement 'takeoffer' api method
• Implement 'confirmpaymentsent' api method
• Implement 'confirmpaymentreceived' api method
• Optionally print the json contract for a given trade id

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.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.5.1.jar
The output need to match the value from the Bisq-1.5.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.5.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.

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.5.1 or later. You can verify the binary the same way as you do with the Bisq application.

Credits

Thanks to everyone who directly contributed to this release:

• Bayernatoor
• cd2357
• chimp1984
• Christoph Atteneder
• deusmax
• Florian Reimair
• Stan
• James Cox
• Luis Aranguren
• mrosseel
• Oscar Guindzberg
• sqrrm
• wiz

A special thanks to our first time contributors:

• Luis Aranguren
• deusmax

As well as to everyone that helped with translations on Transifex.

v1.5.0

A newer version is already available! Please don’t use this version anymore.

Release notes

This release finally brings SegWit to Bisq's trade protocol. It also implements fee optimizations enabled by SegWit, so mining fees for all BTC transactions are lower.

There are also some notable trading-related updates: you can now edit pricing and payment methods of your live offers; account limits have been simplified (and removed where unneeded); and 3 new payment methods were added (Australian PayID, TransferWise and Amazon gift cards).

The SegWit integration wouldn't have been possible without the anonymous sponsor who pre-funded the project, so big thanks to them! If you might be interested in pre-funding a specific feature, please contact us on Keybase in the #projects channel. Bisq is a critical element of the Bitcoin ecosystem and could really use your help.

DAO

• Use LegacyAddress instead of Address for BSQ
• Remove outliers when calculating BSQ rate
• Hide proposal delete button

UI

• Improve labeling of charts: 1, 2
• Cleanup user interface elements in Send Funds screen
• Add export to csv hyperlink (as button takes too much vertical space)

Trading

• Use SegWit for the trade protocol
• Simplify limits for signed and unsigned accounts
• Update Edit Offer to allow for change of market and payment method
• Add new payment method: Australian PayID
• Add new payment method: TransferWise
• Add new payment method: Amazon Gift Cards
• Fix bug with reading historical data

Wallet

• Add SegWit fee estimation: 1, 2
• Speed up restore from seed
• Allow user-defined block explorers
• Show current tx fee rate on main screen

Privacy

• Update netlayer references to Bisq repository

Network

• Remove HitBTC as a pricenode data provider
• Add new burningman address for delayed payout txs
• Reduce seednode default max connections to 20
• Show past deviation in monitor
• Clean up mailbox messages for closed trades
• Admin filter for auto-confirmation service addresses

API

• Implement 'canceloffer' api method
• Implement api methods 'keepfunds', 'withdrawfunds'
• Implement 'gettrade' api method
• Implement 'takeoffer' api method
• Implement 'confirmpaymentsent' api method
• Implement 'confirmpaymentreceived' api method
• Optionally print the json contract for a given trade id

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.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.5.0.jar
The output need to match the value from the Bisq-1.5.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.5.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.

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.5.0 or later. You can verify the binary the same way as you do with the Bisq application.

Credits

Thanks to everyone who directly contributed to this release:

• Bayernatoor
• cd2357
• chimp1984
• Christoph Atteneder
• deusmax
• Florian Reimair
• Stan
• James Cox
• Luis Aranguren
• mrosseel
• Oscar Guindzberg
• sqrrm
• wiz

A special thanks to our first time contributors:

• Luis Aranguren
• deusmax

As well as to everyone that helped with translations on Transifex.

v1.4.2

A newer version is available! Please don’t use this version anymore.

Release notes

This release is packed with new features and improvements:

• Use SegWit addresses to fund and withdraw from your Bisq wallet

NOTE: Although it's now finally possible to transfer out of Bisq to Bech32 wallets, do not expect any fee savings just yet, because all Bisq trading transactions still happen against P2PKH addresses. This change will be shipped in one of the next releases.

• Startup time reduced further, especially on slow connections
• Improvements in the trade protocol to make trading more reliable
• Bug fixes, bug fixes, bug fixes...

UI

• Improve wording: 1, 2
• Show info popup if Bisq started under Qubes OS
• Remove short cut info for removed key handlers

Trading

• Show if seller has XMR autoconfirmation enabled: 1, 2
• XMR autoconfirmation should get amount from trade not offer
• Reactivate confirm button again in specific cases
• Display the calculated security deposit at each order entry

Wallet

• Fund/Withdraw BTC from/to SegWit addresses
• Set memo to transaction after transaction creation and not on broadcast success
• Fix bug with wallet seed restore and open offers

Reliability

• New trade statistics
• Remove address prefix for mailbox messages
• Trade protocol improvements: 1, 2
• Upgrade to bitcoinj 0.15.8
• Fix bug with missing remove of old filter when new filter is added

Privacy

• Use binaries from tor browser v10.0

Mediation/Arbitration

• Add signature to dispute result and various other improvements

Network

• Adding two torv3 seednodes, removing torv2 nodes
• Replace emzy's v2 seednodes with new v3 seednodes

API

• Add core support for registration of regtest dispute agents via API

Development

• Do not log full filter object in case of an invalid Filter
• Setting jvm option -Djdk.module.illegalAccess=deny
• Add flags to header to signal which dev setup is used

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.4.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.4.2.jar
The output need to match the value from the Bisq-1.4.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.4.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.

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.4.2 or later. You can verify the binary the same way as you do with the Bisq application.

v1.4.1

A newer pre-release version based on v1.4.1 fixing a wrong trade history entry is available! Please don’t use this version anymore.

Release notes

This release is packed with new features and improvements:

• Use SegWit addresses to fund and withdraw from your Bisq wallet

NOTE: Although it's now finally possible to transfer out of Bisq to Bech32 wallets, do not expect any fee savings just yet, because all Bisq trading transactions still happen against P2PKH addresses. This change will be shipped in one of the next releases.

• Startup time reduced further, especially on slow connections
• Improvements in the trade protocol to make trading more reliable
• Bug fixes, bug fixes, bug fixes...

UI

• Improve wording: 1, 2
• Show info popup if Bisq started under Qubes OS
• Remove short cut info for removed key handlers

Trading

• Show if seller has XMR autoconfirmation enabled: 1, 2
• XMR autoconfirmation should get amount from trade not offer
• Reactivate confirm button again in specific cases
• Display the calculated security deposit at each order entry

Wallet

• Fund/Withdraw BTC from/to SegWit addresses
• Set memo to transaction after transaction creation and not on broadcast success
• Fix bug with wallet seed restore and open offers

Reliability

• New trade statistics
• Remove address prefix for mailbox messages
• Trade protocol improvements: 1, 2
• Upgrade to bitcoinj 0.15.8
• Fix bug with missing remove of old filter when new filter is added

Privacy

• Use binaries from tor browser v10.0

Mediation/Arbitration

• Add signature to dispute result and various other improvements

Network

• Adding two torv3 seednodes, removing torv2 nodes
• Replace emzy's v2 seednodes with new v3 seednodes

API

• Add core support for registration of regtest dispute agents via API

Development

• Do not log full filter object in case of an invalid Filter
• Setting jvm option -Djdk.module.illegalAccess=deny
• Add flags to header to signal which dev setup is used

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.4.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.4.1.jar
The output need to match the value from the Bisq-1.4.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.4.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.

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.4.1 or later. You can verify the binary the same way as you do with the Bisq application.

v1.4.0

A newer pre-release version based on v1.4.0 fixing an issue with the trade statistics(1, 2) is available! Please don’t use this version anymore.

Release notes

This release is packed with new features and improvements:

• Use SegWit addresses to fund and withdraw from your Bisq wallet
• Startup time reduced further, especially on slow connections
• Improvements in the trade protocol to make trading more reliable
• Bug fixes, bug fixes, bug fixes...

UI

• Improve wording: 1, 2
• Show info popup if Bisq started under Qubes OS
• Remove short cut info for removed key handlers

Trading

• Show if seller has XMR autoconfirmation enabled: 1, 2
• XMR autoconfirmation should get amount from trade not offer
• Reactivate confirm button again in specific cases
• Display the calculated security deposit at each order entry

Wallet

• Fund/Withdraw BTC from/to SegWit addresses
• Set memo to transaction after transaction creation and not on broadcast success
• Fix bug with wallet seed restore and open offers

Reliability

• New trade statistics
• Remove address prefix for mailbox messages
• Trade protocol improvements: 1, 2
• Upgrade to bitcoinj 0.15.8
• Fix bug with missing remove of old filter when new filter is added

Privacy

• Use binaries from tor browser v10.0

Mediation/Arbitration

• Add signature to dispute result and various other improvements

Network

• Adding two torv3 seednodes, removing torv2 nodes
• Replace emzy's v2 seednodes with new v3 seednodes

API

• Add core support for registration of regtest dispute agents via API

Development

• Do not log full filter object in case of an invalid Filter
• Setting jvm option -Djdk.module.illegalAccess=deny
• Add flags to header to signal which dev setup is used

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.4.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.4.0.jar
The output need to match the value from the Bisq-1.4.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.4.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.

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.4.0 or later. You can verify the binary the same way as you do with the Bisq application.

v1.3.9

A newer version is already available! Please don’t use this version anymore.

Release notes

This release brings auto-confirmation for Monero trades, makes usernames required for Revolut payments (to reduce disputes, based on mediator feedback), and improves connectivity within the network. It also improves reliability, please update to this version to avoid network issues!

DAO

• Move merit and stake column to the right
• Tweak a few DAO bonded role names in strings file

UI

• Fix intermittent blank price cells in offer book view
• Improve warning message regarding insufficient BSQ
• Add more detailed network statistics
• Only show signing state if signing for payment method is required

Trading

• Add auto-confirm feature for Monero
• Add support for user name for Revolut accounts
• Add check for option trade for dispute cases
• Fix null pointer in case if selectedMarketPrice is null
• Reload dispute layout on reopen
• Improve dispute views
• Update GUI labels to reflect multiple rate providers
• Fix bug with all mobile notifications for disputes are sent at startup.
• Remove offer from takers offerbook after take offer is completed
• Remove 'monero:' prefix when adding a XMR account

Reliability

• Optimize application shutdown
• Increase timeouts: 1, 2
• Revert usage of caffeinate on OSX
• Make moving average code more safe

Network

• Filter improvements
• Bundle messages at broadcast
• Tweak seednode bitcoin.conf, remove timeout, separate testnet block
• Improve restarting of seednodes
• Reduce seednode maxconnections setting from 50 to 40 in bisq.env
• Add mempool.bisq.services explorer and mempool fee estimation provider
• Add mempool.ninja to pricenodes as 3rd mempool fee estimation backend
• Update all Pricenodes with new Tor V3 onions
• Add new Monero Explorer node77.monero.wiz.biz with onion
• Update old Bisq Explorer URLs with new Mempool Explorer URLs, tweak strings

Development

• Add option to use different css for dev mode

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.3.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.3.9.jar
The output need to match the value from the Bisq-1.3.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.3.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.

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.3.9 or later. You can verify the binary the same way as you do with the Bisq application.

v1.3.8

A newer pre-release version based on v1.3.8 making the moving average code more safe is available! Please don’t use this version anymore.

Release notes

This release brings auto-confirmation for Monero trades, makes usernames required for Revolut payments (to reduce disputes, based on mediator feedback), and improves connectivity within the network. It also improves reliability, please update to this version to avoid network issues!

DAO

• Move merit and stake column to the right
• Tweak a few DAO bonded role names in strings file

UI

• Fix intermittent blank price cells in offer book view
• Improve warning message regarding insufficient BSQ
• Add more detailed network statistics
• Only show signing state if signing for payment method is required

Trading

• Add auto-confirm feature for Monero
• Add support for user name for Revolut accounts
• Add check for option trade for dispute cases
• Fix null pointer in case if selectedMarketPrice is null
• Reload dispute layout on reopen
• Improve dispute views
• Update GUI labels to reflect multiple rate providers
• Fix bug with all mobile notifications for disputes are sent at startup.
• Remove offer from takers offerbook after take offer is completed
• Remove 'monero:' prefix when adding a XMR account

Reliability

• Optimize application shutdown
• Increase timeouts: 1, 2
• Revert usage of caffeinate on OSX

Network

• Filter improvements
• Bundle messages at broadcast
• Tweak seednode bitcoin.conf, remove timeout, separate testnet block
• Improve restarting of seednodes
• Reduce seednode maxconnections setting from 50 to 40 in bisq.env
• Add mempool.bisq.services explorer and mempool fee estimation provider
• Add mempool.ninja to pricenodes as 3rd mempool fee estimation backend
• Update all Pricenodes with new Tor V3 onions
• Add new Monero Explorer node77.monero.wiz.biz with onion
• Update old Bisq Explorer URLs with new Mempool Explorer URLs, tweak strings

Development

• Add option to use different css for dev mode

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.3.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.3.8.jar
The output need to match the value from the Bisq-1.3.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.3.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.3.8 or later. You can verify the binary the same way as you do with the Bisq application.

v1.3.7

A newer version is already available! Please don’t use this version anymore.

Release notes

This is primarily a bug-fix release that takes care of minor issues across the board.

DAO

• Maintain floor amount of 5.46 BSQ to prevent dust errors

UI

• Clean up TOR status icon
• Fix popup window ordering problem

Trading

• Fix altcoin instant account creation / deletion issues
• Tweak popup text and trade rules for USPMO payment method
• Improve input validation of delayed deposit tx
• Fix NullPointerException in transactions csv report

Wallet

• Change IP for local node connection to Loopback address
• Warn that seed phrase is not a data backup

Network

• Fix NullPointerException with external tor usage

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.3.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.3.7.jar
The output need to match the value from the Bisq-1.3.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.3.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.

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.3.7 or later. You can verify the binary the same way as you do with the Bisq application.

v1.3.6

A newer version is already available! Please don’t use this version anymore.

Release notes

In this release we focused on improving account signing, fee handling, and suggested deposit amounts. Also the mechanism to distribute BTC fees to April security incident victims is part of this release.

DAO

• Add validation for max voting-stake

UI

• Improve wording: 1, 2, 3
• Update dark mode to V2: 1, 2, 3

Trading

• Add functionality to distribute BTC fees to victims: 1, 2
• Improvements to suggested deposit percentage
• Signer send witness to signee
• Sign all payment accounts by the same name
• Fix taker use all BSQ for fee payment
• Create offer using the same tx fee specified at funding
• Increase price precision in Offer Book chart (altcoins)
• Add all available Revolut currencies
• Fix tor v3 address validation

Wallet

• Warn when restoring wallet seedwords without date

API

• Call core wallets service methods from CoreApi
• Add RPC method 'getoffers'
• Add RPC method 'createpaymentacct'
• Add RPC method 'getaddressbalance'

Network

• Update Bitcoin explorer URLs and Tor V3 onions for @wiz and @emzy
• Add V3 seednode devinv3r
• Add V3 seednode sn3emzy
• Add V3 seednodes wizseed3 and wizseed7, retire seednode ef5qnzx6znifo3df
• Update seednode/pricenode install scripts

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.3.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.3.6.jar
The output need to match the value from the Bisq-1.3.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.3.6.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.3.6 or later. You can verify the binary the same way as you do with the Bisq application.