v2.1.2

Changes

• Optimized reputation system
  • The following changes improve security and enhance the trading experience:
    • Trade limits are now tied directly to the seller's reputation score.
    • Reputation earned through burning or bonding BSQ will now double over first year.
    • Reputation requirements have been relaxed (eliminated) for trades up to 25 USD.
    • The minimum required reputation score has been removed.
  • See the newly updated reputation wiki page for further details.
• Consolidated chat rooms
  • Based on user feedback, chats have been streamlined into fewer areas as follows:
    • Bisq Easy > Offerbook chat
    • Bisq Easy > My open trades counterparty chats
    • Support > Assistance tab
    • Chat > Discussion tab
    • Chat > Private chats tab
  • Messages from removed chats have been migrated to these new areas as appropriate.
• Fixed notification issues
• Fixed application version in user profile

See all 200+ changes in this release

Installation

See verification and installation instructions

Troubleshoot these common installation problems:

• macOS: App is damaged and cannot be opened
  • run sudo xattr -rd com.apple.quarantine /Applications/Bisq2.app in a terminal
  • open Bisq2 again
• Windows SmartScreen Warning: Windows protected your PC
  • Click the More info button when prompted
  • Click the Run anyway button when prompted

Caution

The Bisq 2 application was renamed in v2.1.0 from Bisq 2 (with a space) to Bisq2. If you are currently running v2.0.9 or earlier, you should manually delete or uninstall the old Bisq 2 application after installing this version. Doing this avoids potential data directory corruption that can occur if you accidentally run the older Bisq 2 application at some point in the future. Note that your existing Bisq 2 data directory must NOT be deleted; only the outdated Bisq 2 application should be removed or uninstalled.

v2.1.1

Superseded by https://github.com/bisq-network/bisq2/releases/tag/v2.1.2

The gpg key in the app contained the expired key [1] and would cause failure in the verification when using the in-app download and verification tool. To avoid that problem at the next update we dropped that version.
As the previous versions also contain the new expired key, the 2.1.2 version is signed by the secondary release manager to avoid that the in-app download and verification tool fails. See release notes at v2.1.2.

[1] Fixed with addaf76

v2.1.0

New to Bisq 2?

Watch the video about Bisq 2 and the overall roadmap at: https://bisq.network/blog/bisq-2-now-in-beta/
For more detail information see: https://bisq.wiki/Bisq_2

ATTENTION: The Bisq 2 application has been renamed from Bisq 2 (with a space) to Bisq2. When you install the new version the old Bisq 2 application remains in place and should be manually deleted or uninstalled to avoid to be used accidentally which would cause database corruption. Note, that the data directory must NOT be deleted, only the application.

Release notes

✨ New features

• Support of Lightning network⚡ as an additional Bitcoin settlement method.
• QR code scanner is included to ease input of addresses and LN invoices.

🔧 Improvements

• Chats have been upgraded with new additions, such as reactions.
• Use real user activity as "liveness"state indicator to see if your peer is online.
• Use user's selected language for trade log messages.

🐛 Bug Fixes

• Improvement of Tor startup.
• Whonix support.
• Fixed all the known issues related to notifications.

See all pull requests merged into that release.

Verification

For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file

Url of the signing key (Alejandro García): https://bisq.network/pubkey/E222AA02.asc
Full fingerprint: B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02

Import the key:
curl https://bisq.network/pubkey/E222AA02.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-2.0.4.dmg)

Known issues with installation

MacOS:

We removed notarization from our build pipeline because of of the risk of Apple certification revocation (see bisq-network/bisq#6341). Unfortunately this will require extra steps when installing Bisq on macOS.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section If you want to open an app that hasn’t been notarized or is from an unidentified developer

If you are running already macOS Ventura (13.0+) you need to do following to be able to start Bisq:

Enter following command in Apple Terminal:

sudo xattr -rd com.apple.quarantine /Applications/Bisq2.app

Hit enter and you will be prompted to enter your password to be able to execute the command as super user.
After running this successfully you should be able to start Bisq as always.

Windows:

We removed the developer code signing because of the same reason as with Apple.
For Windows you just have to ignore the warning after you have verified the installation file yourself and proceed with the installation.

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\Bisq2

[2] Data directory (contains all Bisq data):
C:\Users<username>\AppData\Roaming\Bisq2

Linux:

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

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-2.0.4.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq2 /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.

v2.0.4

Watch the video about Bisq 2 and the overall roadmap at: https://bisq.network/blog/bisq-2-now-in-beta/
For more detail information see: https://bisq.wiki/Bisq_2

Release notes

✨ New features

• Add list view to Offerbook
  
• Offerbook list and markets list are collapsable for minimized layout
  
• Add green and yellow dot indicators for user profiles recently "seen" online (using the republish date of their user profiles - thus only showing that their app is running) and add "Last seen" info at user profile tooltip. Green for last 3 hours, Yellow 3-6 hours. User profiles are re-published every 3 hours, this information is used to derive the "last seen" state.
• Last seen column, search filter and export to csv feature to user profile table at reputation UI
  
• Add support for custom bisq.conf file in data directory (see detail info)

🔧 Improvements

• Fix startup issues with tor
• Various tor improvements
• Add support for running on Whonix
• Various improvements for network stability and connectivity
• Various improvements in peer management
• Improve inventory requests at startup (requesting missing network data)
• Persist backup directory
• Add import UI to signed witness popup

🐛 Bug Fixes

• Fix bug with importing Bisq 1 account age for reputation
• Various bug fixes at trade process
• Various bug fixes in network code

See all pull requests merged into that release.

Verification

For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file

Url of the signing key (Alejandro García): https://bisq.network/pubkey/E222AA02.asc
Full fingerprint: B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02

Import the key:
curl https://bisq.network/pubkey/E222AA02.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-2.0.4.dmg)

Verify jar file inside binary:
You can verify on OSX the jar file with:
shasum -a256 [PATH TO BISQ APP]/Bisq\ 2.app/Contents/app/desktop-2.0.4-all.jar
The output need to match the value from the Bisq-2.0.4.jar.txt file.

There are three hashes within the Bisq-2.0.4.jar.txt file (macOS, Windows, Linux).
If you want to reproduce and verify the hash of the jar file locally, you need to do so on Windows or Linux using Java 17 and the v2.0.4 release tag.

Known issues with installation

macOS:

We removed notarization from our build pipeline because of of the risk of Apple certification revocation (see bisq-network/bisq#6341). Unfortunately this will require extra steps when installing Bisq on macOS.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section If you want to open an app that hasn’t been notarized or is from an unidentified developer

If you are running already macOS Ventura (13.0+) you need to do following to be able to start Bisq:

Enter following command in Apple Terminal:

sudo xattr -rd com.apple.quarantine /Applications/Bisq\ 2.app

Hit enter and you will be prompted to enter your password to be able to execute the command as super user.
After running this successfully you should be able to start Bisq as always.

Windows:

We removed the developer code signing because of the same reason as with Apple.
For Windows you just have to ignore the warning after you have verified the installation file yourself and proceed with the installation.

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\Bisq2

[2] Data directory (contains all Bisq data):
C:\Users<username>\AppData\Roaming\Bisq2

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq2/bin/Bisq\ 2

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-2.0.4.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq2 /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.

v2.0.3

Watch the video about Bisq 2 and the overall roadmap at: https://bisq.network/blog/bisq-2-now-in-beta/
For more detail information see: https://bisq.wiki/Bisq_2

Release notes

✨ New features

• Buyers making offers now decide the trade price! If the seller sets a new price when taking your offer (because they are still running old software), then you can decide whether to proceed or reject/cancel the trade (with no violation of trade rules in this case).
• If you haven't noticed, you can add your most-used markets as favourites ⭐️! Do that by clicking on the empty star when hovering on a market.

🔧 Improvements

• Reputation is now consistent and your stars will only go up as you burn/lock more BSQ. More changes in this area to come soon!
• We have also worked in the overall network stability and connectivity.

🐛 Bug Fixes

• We have worked 💪 very hard to fix all the bugs you have reported (and more) on Github and in the chats. Please keep your feedback coming 📢!
• System notifications have been improved on Windows, so if you had disabled them because they were too noisy - turn them on again and let us know your remarks.

See https://github.com/bisq-network/bisq2/pulls?q=is%3Apr+is%3Aclosed+milestone%3A%222.0.3%22 for all pull requests merged into that release.

Verification

For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file

Url of the signing key (Alejandro García): https://bisq.network/pubkey/E222AA02.asc
Full fingerprint: B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02

Import the key:
curl https://bisq.network/pubkey/E222AA02.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-2.0.3.dmg)

Verify jar file inside binary:
You can verify on OSX the jar file with:
shasum -a256 [PATH TO BISQ APP]/Bisq\ 2.app/Contents/app/desktop-2.0.3-all.jar
The output need to match the value from the Bisq-2.0.3.jar.txt file.

There are three hashes within the Bisq-2.0.3.jar.txt file (macOS, Windows, Linux).
If you want to reproduce and verify the hash of the jar file locally, you need to do so on Windows or Linux using Java 17 and the v2.0.3 release tag.

Known issues with installation

macOS:

We removed notarization from our build pipeline because of of the risk of Apple certification revocation (see bisq-network/bisq#6341). Unfortunately this will require extra steps when installing Bisq on macOS.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section If you want to open an app that hasn’t been notarized or is from an unidentified developer

If you are running already macOS Ventura (13.0+) you need to do following to be able to start Bisq:

Enter following command in Apple Terminal:

sudo xattr -rd com.apple.quarantine /Applications/Bisq\ 2.app

Hit enter and you will be prompted to enter your password to be able to execute the command as super user.
After running this successfully you should be able to start Bisq as always.

Windows:

We removed the developer code signing because of the same reason as with Apple.
For Windows you just have to ignore the warning after you have verified the installation file yourself and proceed with the installation.

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\Bisq2

[2] Data directory (contains all Bisq data):
C:\Users<username>\AppData\Roaming\Bisq2

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq2/bin/Bisq\ 2

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-2.0.3.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq2 /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.

v2.0.2

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

Watch the video about Bisq 2 and the overall roadmap at: https://bisq.network/blog/bisq-2-now-in-beta/
For more detail information see: https://bisq.wiki/Bisq_2

Release notes

See https://github.com/bisq-network/bisq2/pulls?q=is%3Apr+is%3Aclosed+milestone%3A%222.0.3%22 for all pull requests merged into that release.

Verification

For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file

Url of the signing key (Alejandro García): https://bisq.network/pubkey/E222AA02.asc
Full fingerprint: B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02

Import the key:
curl https://bisq.network/pubkey/E222AA02.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-2.0.2.dmg)

Verify jar file inside binary:
You can verify on OSX the jar file with:
shasum -a256 [PATH TO BISQ APP]/Bisq\ 2.app/Contents/app/desktop-2.0.2-all.jar
The output need to match the value from the Bisq-2.0.2.jar.txt file.

There are three hashes within the Bisq-2.0.2.jar.txt file (macOS, Windows, Linux).
If you want to reproduce and verify the hash of the jar file locally, you need to do so on Windows or Linux using Java 17 and the v2.0.2 release tag.

Known issues with installation

macOS:

We removed notarization from our build pipeline because of of the risk of Apple certification revocation (see bisq-network/bisq#6341). Unfortunately this will require extra steps when installing Bisq on macOS.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section If you want to open an app that hasn’t been notarized or is from an unidentified developer

If you are running already macOS Ventura (13.0+) you need to do following to be able to start Bisq:

Enter following command in Apple Terminal:

sudo xattr -rd com.apple.quarantine /Applications/Bisq\ 2.app

Hit enter and you will be prompted to enter your password to be able to execute the command as super user.
After running this successfully you should be able to start Bisq as always.

Windows:

We removed the developer code signing because of the same reason as with Apple.
For Windows you just have to ignore the warning after you have verified the installation file yourself and proceed with the installation.

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\Bisq2

[2] Data directory (contains all Bisq data):
C:\Users<username>\AppData\Roaming\Bisq2

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq2/bin/Bisq\ 2

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-2.0.2.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq2 /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.

v2.0.1

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

Bisq 2 is the successor to the original Bisq (Bisq v1). It has been developed from the ground up to allow for multiple trade protocols to be accessed via a single decentralized exchange platform.

For more information see: https://bisq.wiki/Bisq_2

Verification

For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file

Url of the signing key (Alejandro García): https://bisq.network/pubkey/E222AA02.asc
Full fingerprint: B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02

Import the key:
curl https://bisq.network/pubkey/E222AA02.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-2.0.1.dmg)

Verify jar file inside binary:
You can verify on OSX the jar file with:
shasum -a256 [PATH TO BISQ APP]/Bisq\ 2.app/Contents/app/desktop-2.0.1-all.jar
The output need to match the value from the Bisq-2.0.1.jar.txt file.

There are three hashes within the Bisq-2.0.1.jar.txt file (macOS, Windows, Linux).
If you want to reproduce and verify the hash of the jar file locally, you need to do so on Windows or Linux using Java 17 and the v2.0.1 release tag.

Known issues with installation

macOS:

We removed notarization from our build pipeline because of of the risk of Apple certification revocation (see bisq-network/bisq#6341). Unfortunately this will require extra steps when installing Bisq on macOS.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section If you want to open an app that hasn’t been notarized or is from an unidentified developer

If you are running already macOS Ventura (13.0+) you need to do following to be able to start Bisq:

enter following command in Apple Terminal sudo xattr -rd com.apple.quarantine /Applications/Bisq\ 2.app
hit enter and you will be prompted to enter your password to be able to execute the command as super user
After running this successfully you should be able to start Bisq as always.

Windows:

We removed the developer code signing because of the same reason as with Apple.
For Windows you just have to ignore the warning after you have verified the installation file yourself and proceed with the installation.

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\Bisq2

[2] Data directory (contains all Bisq data including wallet):
C:\Users<username>\AppData\Roaming\Bisq2\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/bisq2/bin/Bisq\ 2

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-2.0.1.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq2 /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.

v2.0.0

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

Bisq 2 is the successor to the original Bisq (Bisq v1). It has been developed from the ground up to allow for multiple trade protocols to be accessed via a single decentralized exchange platform.

For more information see: https://bisq.wiki/Bisq_2

Verification

For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file

Url of the signing key (Alejandro García): https://bisq.network/pubkey/E222AA02.asc
Full fingerprint: B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02

Import the key:
curl https://bisq.network/pubkey/E222AA02.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-2.0.0.dmg)

Verify jar file inside binary:
You can verify on OSX the jar file with:
shasum -a256 [PATH TO BISQ APP]/Bisq\ 2.app/Contents/app/desktop-2.0.0-all.jar
The output need to match the value from the Bisq-2.0.0.jar.txt file.

There are three hashes within the Bisq-2.0.0.jar.txt file (macOS, Windows, Linux).
If you want to reproduce and verify the hash of the jar file locally, you need to do so on Windows or Linux using Java 17 and the v2.0.0 release tag.

Known issues with installation

macOS:

We removed notarization from our build pipeline because of of the risk of Apple certification revocation (see bisq-network/bisq#6341). Unfortunately this will require extra steps when installing Bisq on macOS.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section If you want to open an app that hasn’t been notarized or is from an unidentified developer

If you are running already macOS Ventura (13.0+) you need to do following to be able to start Bisq:

enter following command in Apple Terminal sudo xattr -rd com.apple.quarantine /Applications/Bisq\ 2.app
hit enter and you will be prompted to enter your password to be able to execute the command as super user
After running this successfully you should be able to start Bisq as always.

Windows:

We removed the developer code signing because of the same reason as with Apple.
For Windows you just have to ignore the warning after you have verified the installation file yourself and proceed with the installation.

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\Bisq2

[2] Data directory (contains all Bisq data including wallet):
C:\Users<username>\AppData\Roaming\Bisq2\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/bin/Bisq

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-2.0.0.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq2 /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.

v0.0.7 [test-release]

This is just a test release for communication and testing purposes.
DO NOT use this release and connect your Bitcoin Mainnet wallet!

v0.0.6 [dev-release]

This is just a developer release for communication and testing purposes.
DO NOT use this release and connect your Bitcoin Mainnet wallet!