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.

v1.3.5

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

Release notes

This release is again packed with bug fixes and improvements. We focused in this release especially on improvements for power traders.

DAO

• BondsView: Fix sorting of columns: 1, 2
• Fix proof-of-burn signing for password protected wallets
• Improve proof of burn layout

UI

• Improve dust limit error messaging
• OfferBook: Show min-max range for amount and volume
• Fix address validation for whitespace after comma
• Secondary sort order for offer book
• Display "Payment Method" column in Open Offers view
• Fix Trader Chat row selection and unread message count
• More readable tables and lists: Alternate row background colors

Trading

• When accepting an offer do not round the BTC amount outside range
• Editing an offer should not allow the BTC amount to be changed
• Display correct trade and tx fees in CSV export
• Fix trade withdraw to external wallet step 4
• Opening a take/create offers closes previously opened tab

Wallet

• Fix QR code display of offer funding amount:1, 2
• Add memo field to withdrawal transaction

API

• Add RPC wallet protection endpoints

Development

• Bugfixes related to switch statements

Network

• Switch to more accurate fee estimation endpoint
• Extend FeeRateService to support multiple API endpoints
• Increase BSQ explorer TMPFS allocation to 2GB for growing datastore
• Update IPs and onions for wiz Bitcoin nodes

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.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.3.5.jar
The output need to match the value from the Bisq-1.3.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.3.5.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

That instruction is not tested on many different distros. If you encounter problems please report it in a Github issue so we can improve it.

Cleanup tool for saved trades that failed market price check

With this release we are also shipping a cleanup tool (Bisq-cleanup-trades*). It will remove corrupt trade entries added due to bug #2924. Install and run once, it will shut down automatically, then install version 1.3.5 or later. You can verify the binary the same way as you do with the Bisq application.

v1.3.4

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

This is a hotfix that helps everyone participating in the DAO to determine the vote result for voting cycle 12. Additionally it also removes ghost offers from the offer book.

If you see conflicts with a seed node in the DAO > Network Monitor you will see a Resync DAO State button. Please click on that and restart. After that no conflicts with seed nodes should be displayed anymore.

• Improve permutation algorithm to avoid running into limit while trying to find majority hash
• Reject expired data

Here are the release notes from v1.3.2:

Release notes

This release is packed with bug fixes and improvements. Most notably, it improves the reliability of the wallet and uses Tor onion services version 3 for new data directories.

UI

• Add volume weighted average BSQ price
• Only use InputValidation when formatting voting stake
• Make prompt text for passwords readable in dark mode
• Size the offer book on window activation
• Sorting order of offers appropriately by min/max range

Trading

• Unfail trades if possible (reattach addresses)
• Add holder name for new Faster Payments accounts
• Replace the Get Support button with Open Trader Chat until trade period is over
• Add signed witness filter
• Improve handling of filtered offers and unsupported payment methods

Wallet

• Limit number of unconfirmed offers
• Prevent dust outputs from being created during the trade process
• Prevent dust outputs from being created during withdraw from wallet

Performance/Reliability

• Improve avoid standby feature
• Make UserThread::run* methods thread safe
• Make serialisation in FileManager::saveToFile thread-safe
• Added graceful shutdown hook

Privacy

• Upgrade to Tor 0.4.2.6 (using v3 addresses for new data directories)

Configuration

• Allow IPv6 connections to Bitcoin nodes
• Prevent incorrect usage of --useLocalhostForP2P option
• Avoid startup failure when bannedSeedNodes arg is empty
• Limit system ram to 4GB

Network

• Replace a @wiz v2 seednode with a new v3 seednode
• Remove a @wiz bitcoin node to reduce total count to 16 nodes
• Add onion address for @robkaandorp's btcnode

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.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.3.4.jar
The output need to match the value from the Bisq-1.3.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 files please follow this instruction:

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.3.4.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.4 or later. You can verify the binary the same way as you do with the Bisq application.

v1.3.3

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

This is a hotfix that helps everyone participating in the DAO to determine the vote result for voting cycle 12.

If you see conflicts with a seed node in the DAO > Network Monitor you will see a Resync DAO State button. Please click on that and restart. After that no conflicts with seed nodes should be displayed anymore.

• Improve permutation algorithm to avoid running into limit while trying to find majority hash

Here are the release notes from v1.3.2:

Release notes

This release is packed with bug fixes and improvements. Most notably, it improves the reliability of the wallet and uses Tor onion services version 3 for new data directories.

UI

• Add volume weighted average BSQ price
• Only use InputValidation when formatting voting stake
• Make prompt text for passwords readable in dark mode
• Size the offer book on window activation
• Sorting order of offers appropriately by min/max range

Trading

• Unfail trades if possible (reattach addresses)
• Add holder name for new Faster Payments accounts
• Replace the Get Support button with Open Trader Chat until trade period is over
• Add signed witness filter
• Improve handling of filtered offers and unsupported payment methods

Wallet

• Limit number of unconfirmed offers
• Prevent dust outputs from being created during the trade process
• Prevent dust outputs from being created during withdraw from wallet

Performance/Reliability

• Improve avoid standby feature
• Make UserThread::run* methods thread safe
• Make serialisation in FileManager::saveToFile thread-safe
• Added graceful shutdown hook

Privacy

• Upgrade to Tor 0.4.2.6 (using v3 addresses for new data directories)

Configuration

• Allow IPv6 connections to Bitcoin nodes
• Prevent incorrect usage of --useLocalhostForP2P option
• Avoid startup failure when bannedSeedNodes arg is empty
• Limit system ram to 4GB

Network

• Replace a @wiz v2 seednode with a new v3 seednode
• Remove a @wiz bitcoin node to reduce total count to 16 nodes
• Add onion address for @robkaandorp's btcnode

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.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.3.3.jar
The output need to match the value from the Bisq-1.3.3.jar.txt file.

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

Discussed in issue #3373, you will see a permission request in the latest macOS version that Bisq wants to receive keystrokes from any application. Unfortunately that is an issue for all Java applications that are run on Catalina right now. We are investigating already how to solve this issue and will fix in one of our next updates.

Windows:

There is a known issue with Anti Virus software. We got several reports from users running into different problems. Either the AV software blocks Bisq or Tor, delete files in the data directory [2] or app directory [1]) or cause such a long delay at startup that Tor gets terminated and a file remains locked which can cause that Bisq cannot be started afterwards. To resolve that you need to restart Windows then the lock get released. We are working on solutions to fix those issues.

If you use Crypto currencies on your Windows system be aware that Windows is much more vulnerable to malware than Linux or OSX. Consider to use a dedicated non-Windows system when dealing with cryptocurrencies.

[1] Application directory (contains application installation files):
C:\Users<username>\AppData\Local\Bisq

[2] Data directory (contains all Bisq data including wallet):
C:\Users<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/Bisq/Bisq

If your Linux distro does not support .deb files please follow this instruction:

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.3.3.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.3 or later. You can verify the binary the same way as you do with the Bisq application.

v1.3.2

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

Release notes

This release is packed with bug fixes and improvements. Most notably, it improves the reliability of the wallet and uses Tor onion services version 3 for new data directories.

UI

• Add volume weighted average BSQ price
• Only use InputValidation when formatting voting stake
• Make prompt text for passwords readable in dark mode
• Size the offer book on window activation
• Sorting order of offers appropriately by min/max range

Trading

• Unfail trades if possible (reattach addresses)
• Add holder name for new Faster Payments accounts
• Replace the Get Support button with Open Trader Chat until trade period is over
• Add signed witness filter
• Improve handling of filtered offers and unsupported payment methods

Wallet

• Limit number of unconfirmed offers
• Prevent dust outputs from being created during the trade process
• Prevent dust outputs from being created during withdraw from wallet

Performance/Reliability

• Improve avoid standby feature
• Make UserThread::run* methods thread safe
• Make serialisation in FileManager::saveToFile thread-safe
• Added graceful shutdown hook

Privacy

• Upgrade to Tor 0.4.2.6 (using v3 addresses for new data directories)

Configuration

• Allow IPv6 connections to Bitcoin nodes
• Prevent incorrect usage of --useLocalhostForP2P option
• Avoid startup failure when bannedSeedNodes arg is empty
• Limit system ram to 4GB

Network

• Replace a @wiz v2 seednode with a new v3 seednode
• Remove a @wiz bitcoin node to reduce total count to 16 nodes
• Add onion address for @robkaandorp's btcnode

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.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.3.2.jar
The output need to match the value from the Bisq-1.3.2.jar.txt file.

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

Discussed in issue #3373, you will see a permission request in the latest macOS version that Bisq wants to receive keystrokes from any application. Unfortunately that is an issue for all Java applications that are run on Catalina right now. We are investigating already how to solve this issue and will fix in one of our next updates.

Windows:

There is a known issue with Anti Virus software. We got several reports from users running into different problems. Either the AV software blocks Bisq or Tor, delete files in the data directory [2] or app directory [1]) or cause such a long delay at startup that Tor gets terminated and a file remains locked which can cause that Bisq cannot be started afterwards. To resolve that you need to restart Windows then the lock get released. We are working on solutions to fix those issues.

If you use Crypto currencies on your Windows system be aware that Windows is much more vulnerable to malware than Linux or OSX. Consider to use a dedicated non-Windows system when dealing with cryptocurrencies.

[1] Application directory (contains application installation files):
C:\Users<username>\AppData\Local\Bisq

[2] Data directory (contains all Bisq data including wallet):
C:\Users<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/Bisq/Bisq

If your Linux distro does not support .deb files please follow this instruction:

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.3.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.3.2 or later. You can verify the binary the same way as you do with the Bisq application.

v1.3.1

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

This is a hotfix that improves delayed deposit transaction verification and fixes a bug that marks valid trades as failed trades.

• Fix issue with connected transaction output

Here are the release notes from v1.3.0:

Release notes

This release is, once again, packed with bug fixes and improvements. Most notably, it reduces the intervals in which users can trigger a trade process refresh.

UI

• Improve wording for local BTC node reminder in Settings > Network info
• Display 2 decimal places for fiat trading fees
• Fix checkbox handling in My Open Offers

Trading

• Reduce time until trade process refresh is possible: 1, 2
• Update owner address of offer to new hidden service files
• Add ARS as supported currency for MoneyGram

Performance

• Speed up DAO state monitor view load

Privacy

• Remove unused uid in fee provider service
• Fix incorrect deletion of hidden service directory when using --appDataDir

Configuration

• Avoid startup failure when appDataDir is a symbolic link
• Accept empty config values

Network

• Update URL for mempool.ninja blockchain explorer
• Fix nginx.conf for collectd so it only listens on 127.0.0.1
• Fix CoinMarketCap API issues: 1, 2, 3
• Moved node2.emzy.de to a new host

Monitor

• Added monitoring install scripts

Support

• Log delayed payout transaction bytes as soon as it's signed during trade initialization
• Dump delayed payout transactions of both pending and failed trades if flag is set

Assets

No assets were added.

Verification

Url of the signing key (Christoph Atteneder): https://bisq.network/pubkey/29CDFD3B.asc
Full fingerprint: CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B

Import the key:
curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import
GPG prints a confusion warning: "This key is not certified with a trusted signature!" - See https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means.

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.3.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.3.1.jar
The output need to match the value from the Bisq-1.3.1.jar.txt file.

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

Discussed in issue #3373, you will see a permission request in the latest macOS version that Bisq wants to receive keystrokes from any application. Unfortunately that is an issue for all Java applications that are run on Catalina right now. We are investigating already how to solve this issue and will fix in one of our next updates.

Windows:

There is a known issue with Anti Virus software. We got several reports from users running into different problems. Either the AV software blocks Bisq or Tor, delete files in the data directory [2] or app directory [1]) or cause such a long delay at startup that Tor gets terminated and a file remains locked which can cause that Bisq cannot be started afterwards. To resolve that you need to restart Windows then the lock get released. We are working on solutions to fix those issues.

If you use Crypto currencies on your Windows system be aware that Windows is much more vulnerable to malware than Linux or OSX. Consider to use a dedicated non-Windows system when dealing with cryptocurrencies.

[1] Application directory (contains application installation files):
C:\Users<username>\AppData\Local\Bisq

[2] Data directory (contains all Bisq data including wallet):
C:\Users<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/Bisq/Bisq

If your Linux distro does not support .deb files please follow this instruction:

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.3.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.3.1 or later. You can verify the binary the same way as you do with the Bisq application.

v1.3.0

A newer version is already available! Please don’t use this version anymore.
Binaries have been removed as this release is superseded by v1.3.1

This is a hot fix release fixing a critical security vulnerability in the trade protocol.

• #4134
• #4137
• #4140

Here are the release notes from v1.2.9:

Release notes

This release is, once again, packed with bug fixes and improvements. Most notably, it reduces the intervals in which users can trigger a trade process refresh.

UI

• Improve wording for local BTC node reminder in Settings > Network info
• Display 2 decimal places for fiat trading fees
• Fix checkbox handling in My Open Offers

Trading

• Reduce time until trade process refresh is possible: 1, 2
• Update owner address of offer to new hidden service files
• Add ARS as supported currency for MoneyGram

Performance

• Speed up DAO state monitor view load

Privacy

• Remove unused uid in fee provider service
• Fix incorrect deletion of hidden service directory when using --appDataDir

Configuration

• Avoid startup failure when appDataDir is a symbolic link
• Accept empty config values

Network

• Update URL for mempool.ninja blockchain explorer
• Fix nginx.conf for collectd so it only listens on 127.0.0.1
• Fix CoinMarketCap API issues: 1, 2, 3
• Moved node2.emzy.de to a new host

Monitor

• Added monitoring install scripts

Support

• Log delayed payout transaction bytes as soon as it's signed during trade initialization
• Dump delayed payout transactions of both pending and failed trades if flag is set

Assets

No assets were added.

Verification

Url of the signing key (Christoph Atteneder): https://bisq.network/pubkey/29CDFD3B.asc
Full fingerprint: CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B

Import the key:
curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import
GPG prints a confusion warning: "This key is not certified with a trusted signature!" - See https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means.

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.3.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.3.0.jar
The output need to match the value from the Bisq-1.3.0.jar.txt file.

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

Discussed in issue #3373, you will see a permission request in the latest macOS version that Bisq wants to receive keystrokes from any application. Unfortunately that is an issue for all Java applications that are run on Catalina right now. We are investigating already how to solve this issue and will fix in one of our next updates.

Windows:

There is a known issue with Anti Virus software. We got several reports from users running into different problems. Either the AV software blocks Bisq or Tor, delete files in the data directory [2] or app directory [1]) or cause such a long delay at startup that Tor gets terminated and a file remains locked which can cause that Bisq cannot be started afterwards. To resolve that you need to restart Windows then the lock get released. We are working on solutions to fix those issues.

If you use Crypto currencies on your Windows system be aware that Windows is much more vulnerable to malware than Linux or OSX. Consider to use a dedicated non-Windows system when dealing with cryptocurrencies.

[1] Application directory (contains application installation files):
C:\Users<username>\AppData\Local\Bisq

[2] Data directory (contains all Bisq data including wallet):
C:\Users<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/Bisq/Bisq

If your Linux distro does not support .deb files please follow this instruction:

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.3.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.3.0 or later. You can verify the binary the same way as you do with the Bisq application.

v1.2.9

A newer version is already available! Please don’t use this version anymore.
Binaries have been removed as this release is superseded by v1.3.0

This is a hot fix release reverting the local Bitcoin Core node configuration check as it caused startup issues on very specific OS setups.

Here are the release notes from v1.2.8:

Release notes

This release is, once again, packed with bug fixes and improvements. Most notably, it reduces the intervals in which users can trigger a trade process refresh.

UI

• Improve wording for local BTC node reminder in Settings > Network info
• Display 2 decimal places for fiat trading fees
• Fix checkbox handling in My Open Offers

Trading

• Reduce time until trade process refresh is possible: 1, 2
• Update owner address of offer to new hidden service files
• Add ARS as supported currency for MoneyGram

Performance

• Speed up DAO state monitor view load

Privacy

• Remove unused uid in fee provider service
• Fix incorrect deletion of hidden service directory when using --appDataDir

Configuration

• Avoid startup failure when appDataDir is a symbolic link
• Accept empty config values

Network

• Update URL for mempool.ninja blockchain explorer
• Fix nginx.conf for collectd so it only listens on 127.0.0.1
• Fix CoinMarketCap API issues: 1, 2, 3
• Moved node2.emzy.de to a new host

Monitor

• Added monitoring install scripts

Support

• Log delayed payout transaction bytes as soon as it's signed during trade initialization
• Dump delayed payout transactions of both pending and failed trades if flag is set

Assets

No assets were added.

Verification

Url of the signing key (Christoph Atteneder): https://bisq.network/pubkey/29CDFD3B.asc
Full fingerprint: CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B

Import the key:
curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import
GPG prints a confusion warning: "This key is not certified with a trusted signature!" - See https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means.

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.2.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.2.9.jar
The output need to match the value from the Bisq-1.2.9.jar.txt file.

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

Discussed in issue #3373, you will see a permission request in the latest macOS version that Bisq wants to receive keystrokes from any application. Unfortunately that is an issue for all Java applications that are run on Catalina right now. We are investigating already how to solve this issue and will fix in one of our next updates.

Windows:

There is a known issue with Anti Virus software. We got several reports from users running into different problems. Either the AV software blocks Bisq or Tor, delete files in the data directory [2] or app directory [1]) or cause such a long delay at startup that Tor gets terminated and a file remains locked which can cause that Bisq cannot be started afterwards. To resolve that you need to restart Windows then the lock get released. We are working on solutions to fix those issues.

If you use Crypto currencies on your Windows system be aware that Windows is much more vulnerable to malware than Linux or OSX. Consider to use a dedicated non-Windows system when dealing with cryptocurrencies.

[1] Application directory (contains application installation files):
C:\Users<username>\AppData\Local\Bisq

[2] Data directory (contains all Bisq data including wallet):
C:\Users<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/Bisq/Bisq

If your Linux distro does not support .deb files please follow this instruction:

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.2.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.2.9 or later. You can verify the binary the same way as you do with the Bisq application.