v1.9.8

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

This is a follow-up release that fixes an issue in v1.9.7 with the capacity of an internal queue.

See https://github.com/bisq-network/bisq/milestone/78?closed=1 for more details.

Here are the release notes from v1.9.7:

Release notes

This release is packed with improvements under the hood to improve resilience of the client and push further the decentralization of Bisq. Of course we have fixed lots of bugs across the board as well.

Improvements

• Distribute delayed payout handling: 1, 2
• Add user defined trade limits: 1, 2
• Don't ask for SEPA Instant payment when buyer has SEPA account
• Add prompt to confirm before shutting down
• Increase mouse-wheel vertical scrolling speed in long content views
• Include option for non-URI addresses in QR codes
• Add option to bundle all logs in home directory
• Change minimum payout at mediation from 2.5% to 5% of trade amount
• Improve the Support Tool UI
• Fix divide by zero errors in Trade history summary

Bug fixes

• Fix horizontal centering of overlays on Windows
• Fix loss of mailbox messages during SPV resync
• Fix incorrect wallet TX handling
• Fix NPE when dust TX is shown
• Handle exception properly when sending a message

Development & Documentation

• Improve Seednode monitoring: 1, 2
• Avoid sending repeated block related report data
• Fix NPE in seednode
• Limit getDataResponse size
• Handle HttpExceptions at block handler
• Improve threadpools at networknode
• Fix blocking call at send Dao hashes response
• Reduce Response size
• Increase timeouts from 3 to 4 min
• Remove connection:keep-alive header
• Update app signatures for v1.9.8
• Remove KanoczTomas Bitcoin node, because it is permanet offline
• Update sqrrm provided BTC onion addresses
• Fix FileTransferSession tests
• Introduce Gradle Version Catalog
• Update to Gradle 7.6
• Enforce Gradle dependency verification
• Reenable verbose dependency verification (failure report)
• Fix broken Gradle Dependency Verification
• Remove unused modules
• Minor inclusions in deploy & undeploy targets (Makefile)
• Deactivate shadowDistTar and shadowDistZip tasks
• Improve Dao node domain
• Bump actions/setup-java from 3.6.0 to 3.7.0
• Bump actions/setup-java from 3.5.1 to 3.6.0

New Assets

No new assets added.

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 (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.9.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/app/desktop-1.9.8-all.jar
The output need to match the value from the Bisq-1.9.8.jar.txt file.

There are three hashes within the Bisq-1.9.8.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 15.0.9 and the v1.9.8 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

API

Starting with v1.9.0 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.8.zip) and Bisq daemon (bisq-daemon-v1.9.8.zip) to use Bisq without touching the user interface.

Just download the archives and extract them locally. You have to run the daemon to access the local Bisq daemon API endpoints.

To run daemon.jar on Mainnet:

$ java -jar daemon.jar --apiPassword=becareful

If you just want to control your headless daemon within your terminal you have to run the Bisq cli as well.

Again just download the bisq-cli archive and extract it locally.

To call getversion from cli.jar

$ java -jar cli.jar --password=becareful getversion

You can use the Bisq API to access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades.

The Bisq API is based on the gRPC framework, and any supported gRPC language binding can be used to call Bisq API endpoints.

You'll find in-depth documentation and examples under following link: https://bisq-network.github.io/slate/#introduction

Bisq gRPC API reference documentation example source code is hosted on GitHub at https://github.com/bisq-network/bisq-api-reference. Java and Python developers interested in bot development may find this Intellij project useful for running the existing examples, and writing their own bots.

For additional developer support please join Development - Bisq v1 on Matrix.

Known issues with installation

macOS:

We removed notarization from our build pipeline because of of the risk of Apple certification revocation (see #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.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\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/bin/Bisq

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x .....

v1.9.7

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

Release notes

This release is packed with improvements under the hood to improve resilience of the client and push further the decentralization of Bisq. Of course we have fixed lots of bugs across the board as well.

Improvements

• Distribute delayed payout handling: 1, 2
• Add user defined trade limits: 1, 2
• Don't ask for SEPA Instant payment when buyer has SEPA account
• Add prompt to confirm before shutting down
• Increase mouse-wheel vertical scrolling speed in long content views
• Include option for non-URI addresses in QR codes
• Add option to bundle all logs in home directory
• Change minimum payout at mediation from 2.5% to 5% of trade amount
• Improve the Support Tool UI
• Fix divide by zero errors in Trade history summary

Bug fixes

• Fix horizontal centering of overlays on Windows
• Fix loss of mailbox messages during SPV resync
• Fix incorrect wallet TX handling
• Fix NPE when dust TX is shown
• Handle exception properly when sending a message

Development & Documentation

• Improve Seednode monitoring: 1, 2
• Avoid sending repeated block related report data
• Fix NPE in seednode
• Limit getDataResponse size
• Handle HttpExceptions at block handler
• Improve threadpools at networknode
• Fix blocking call at send Dao hashes response
• Reduce Response size
• Increase timeouts from 3 to 4 min
• Remove connection:keep-alive header
• Update app signatures for v1.9.7
• Remove KanoczTomas Bitcoin node, because it is permanet offline
• Update sqrrm provided BTC onion addresses
• Fix FileTransferSession tests
• Introduce Gradle Version Catalog
• Update to Gradle 7.6
• Enforce Gradle dependency verification
• Reenable verbose dependency verification (failure report)
• Fix broken Gradle Dependency Verification
• Remove unused modules
• Minor inclusions in deploy & undeploy targets (Makefile)
• Deactivate shadowDistTar and shadowDistZip tasks
• Improve Dao node domain
• Bump actions/setup-java from 3.6.0 to 3.7.0
• Bump actions/setup-java from 3.5.1 to 3.6.0

New Assets

No new assets added.

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 (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.9.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/app/desktop-1.9.7-all.jar
The output need to match the value from the Bisq-1.9.7.jar.txt file.

There are three hashes within the Bisq-1.9.7.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 15.0.9 and the v1.9.7 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

API

Starting with v1.9.0 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.7.zip) and Bisq daemon (bisq-daemon-v1.9.7.zip) to use Bisq without touching the user interface.

Just download the archives and extract them locally. You have to run the daemon to access the local Bisq daemon API endpoints.

To run daemon.jar on Mainnet:

$ java -jar daemon.jar --apiPassword=becareful

If you just want to control your headless daemon within your terminal you have to run the Bisq cli as well.

Again just download the bisq-cli archive and extract it locally.

To call getversion from cli.jar

$ java -jar cli.jar --password=becareful getversion

You can use the Bisq API to access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades.

The Bisq API is based on the gRPC framework, and any supported gRPC language binding can be used to call Bisq API endpoints.

You'll find in-depth documentation and examples under following link: https://bisq-network.github.io/slate/#introduction

Bisq gRPC API reference documentation example source code is hosted on GitHub at https://github.com/bisq-network/bisq-api-reference. Java and Python developers interested in bot development may find this Intellij project useful for running the existing examples, and writing their own bots.

For additional developer support please join Development - Bisq v1 on Matrix.

Known issues with installation

macOS:

We removed notarization from our build pipeline because of of the risk of Apple certification revocation (see #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.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\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/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-1.9.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. ...

v1.9.6

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

Release notes

This release improves the loading of initial data and Tor connectivity. We also removed macOS notarization and developer signing on Windows to increase privacy and censorship resistance. And of course, we squashed bugs across the board.

Improvements

• Improve initial data load
• Upgrade Tor version to v0.4.7.10
• Clarify wording on buy/sell button in Offer Book: 1, 2
• Warn at shutdown if Dispute message is pending
• Offers from a banned node should not be displayed
• Set the minimum payout at mediation to be 2.5% of trade amount
• Updating DAO->Governance menu to indicate vote possible

Bug fixes

• Fix bugs in BSQ Supply screen
• Fix issue with offers getting disabled for no apparent reason
• Refresh all avatars upon setting a peer's tag
• Prevent NPE in Open Proposals when last column is empty
• Prevent NPE when editing offer while not fully connected

Development & Documentation

• Not use platform specific binary signing and notarization
• Not use git lfs anymore
• API: Fix BSQ buyer's displayed trade fee for gettrade(s) methods
• API: Remove dead API test harness code
• Remove @c4talys7 seednodes and readd @wiz seednodes
• Remove gradle subproject :relay
• Adapt the documentation to match the current Tor upgrade process
• Bump actions/checkout from 3.0.2 to 3.1.0
• Bump actions/setup-java from 3.5.0 to 3.5.1
• Bump actions/setup-java from 3.4.1 to 3.5.0

New Assets

No new assets added.

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 (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.9.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/app/desktop-1.9.6-all.jar
The output need to match the value from the Bisq-1.9.6.jar.txt file.

There are three hashes within the Bisq-1.9.6.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 15.0.9 and the v1.9.6 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

API

Starting with v1.9.0 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.6.zip) and Bisq daemon (bisq-daemon-v1.9.6.zip) to use Bisq without touching the user interface.

Just download the archives and extract them locally. You have to run the daemon to access the local Bisq daemon API endpoints.

To run daemon.jar on Mainnet:

$ java -jar daemon.jar --apiPassword=becareful

If you just want to control your headless daemon within your terminal you have to run the Bisq cli as well.

Again just download the bisq-cli archive and extract it locally.

To call getversion from cli.jar

$ java -jar cli.jar --password=becareful getversion

You can use the Bisq API to access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades.

The Bisq API is based on the gRPC framework, and any supported gRPC language binding can be used to call Bisq API endpoints.

You'll find in-depth documentation and examples under following link: https://bisq-network.github.io/slate/#introduction

Bisq gRPC API reference documentation example source code is hosted on GitHub at https://github.com/bisq-network/bisq-api-reference. Java and Python developers interested in bot development may find this Intellij project useful for running the existing examples, and writing their own bots.

For additional developer support please join Development - Bisq v1 on Matrix.

Known issues with installation

macOS:

We removed notarization from our build pipeline because of of the risk of Apple certification revocation (see #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.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\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/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-1.9.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.

Credits

Thanks to everyone who directly contributed to this release:

• @Android-X13
• @chimp1984
• @Emzy
• @ghubstan
• @jmacxx
• @ripcurlx
• @xyzmaker123

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

v1.9.5

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

Release notes

This summer release introduces a new P2P status indicator, adds Bitcoin Core v23 compatibility, and (as always) makes many bug fixes and minor improvements across the board.

Improvements

• P2P network status indicator
• Prevent UI trading actions when there are no P2P connections
• Prepare Bisq for bitcoin-core v23 compatibility
• Possibility to copy addresses / transaction IDs
• Don't use all available funds by default when sending funds
• Show peer Info window only when left-clicking on avatar
• Allow mediated payout signature message to be re-sent
• Clear sensitive data from trade ProcessModel

Bug fixes

• Reset trigger price after switch to fixed price when editing an offer
• Improve clickable areas of toggle buttons in DAO charts view
• Fix NullPointerException when accessing DAO > BSQ Supply
• Fix ability to copy & paste QR code URL
• Fix NullPointerException in account name creation

Development & Documentation

• GetBlocksResponse lower chunk size (was 6000 now 4000)
• Remove 3 wiz seed nodes
• Add new seednodes from @jmacxx and @c4talys7
• Remove subproject daonode
• Update daonode
• Remove subproject inventory
• Set desktop version property in resources file
• Cleanup blockchain explorer URL code & add tests
• API: takeoffer - let user choose intended trade amount
• API: Update API test-guide and gRPC method docs
• Fix snake_case field names in protobuf file
• Set Tor logging to DEBUG level at startup
• Show last successful response time in inventory monitor
• Add tutorial to clone exclusively specific branch
• Bump actions/setup-java from 3.4.0 to 3.4.1
• Bump actions/setup-java from 3.3.0 to 3.4.0

New Assets

No new assets added.

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 (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.9.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/app/desktop-1.9.5-all.jar
The output need to match the value from the Bisq-1.9.5.jar.txt file.

There are three hashes within the Bisq-1.9.5.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 15.0.6 and the v1.9.5 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

API

Starting with v1.9.0 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.5.zip) and Bisq daemon (bisq-daemon-v1.9.5.zip) to use Bisq without touching the user interface.

Just download the archives and extract them locally. You have to run the daemon to access the local Bisq daemon API endpoints.

To run daemon.jar on Mainnet:

$ java -jar daemon.jar --apiPassword=becareful

If you just want to control your headless daemon within your terminal you have to run the Bisq cli as well.

Again just download the bisq-cli archive and extract it locally.

To call getversion from cli.jar

$ java -jar cli.jar --password=becareful getversion

You can use the Bisq API to access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades.

The Bisq API is based on the gRPC framework, and any supported gRPC language binding can be used to call Bisq API endpoints.

You'll find in-depth documentation and examples under following link: https://bisq-network.github.io/slate/#introduction

Bisq gRPC API reference documentation example source code is hosted on GitHub at https://github.com/bisq-network/bisq-api-reference. Java and Python developers interested in bot development may find this Intellij project useful for running the existing examples, and writing their own bots.

For additional developer support please join Development - Bisq v1 on Matrix.

Known issues with installation

Windows:

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

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

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

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

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq/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-1.9.5.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Credits

Thanks to everyone who directly contributed to this release:

• @Android-X13
• @chimp1984
• @Emzy
• @ghubstan
• @jmacxx
• @ripcurlx
• @w0000000t
• @wiz
• @xyzmaker123

A special thanks to our first time contributor:

• @Android-X13:
  • Fix/improve clickable areas of toggle buttons
  • Show Peer Info window only when left-clicking on avatar
  • Cleanup blockchain explorer URL code & add tests
  • Fix NPE when accessing DAO > BSQ SUPPLY

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

v1.9.4

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

This is a follow-up release that adds the latest Tor version (v0.4.7.8) to improve Tor connectivity.

See https://github.com/bisq-network/bisq/milestone/74?closed=1 for more details.

Here are the release notes from v1.9.3:

Release notes

This release improves XMR trade security by using subaddresses, improves Tor connectivity, and ships bug fixes and minor improvements across the board.

Improvements

• Create new XMR subaddress for each trade
• Improve XMR proof service
• Reset Tor directory when a new release is downloaded
• Adopt economyFee recommendation from Mempool rate provider
• Add chart series for total trade fees
• Show changes in BSQ Supply over time
• Prevent account creation for banned Revolut GBP sort code 040075
• Improve wording & appearance of trade shutdown dialog
• Prevent shutdown if trade is in process of being taken
• Mark user's own offers in Market -> Offer book
• Attempt self-ping 3 times before reporting error with connectivity

Bug fixes

• NPE when duplicate offer with deleted account
• Include payment screen ref text message & fix sizing issues
• Signed account must show signed age
• Australia PayID was not displaying payment info on buyer trade
• Refactor BSQ fee validation to handle multiple tx inputs
• Fix refresh issue with x-axis tick labels (Market/Trade charts)
• Transactions view: fix NPE in column sorting when Memo is empty
• Update matching account toggle state when tab is selected

Development & Documentation

• Seednode: Install tor from tor repository and add external tor as default
• Seednode: Update Java version for install script
• Seednode: Clean up tor files at seed node startup
• Pricenode: Add JVM flag ExitOnOutOfMemoryError
• Pricenode: Upgrade to XChange 5.0.13
• Pricenode: configurable exclusion by provider currency
• API: Block API attempt to swap BSQ with insufficient funds
• API: Add API method getavgbsqprice
• API: Add API method getnetwork
• API: Make API getoffers (altcoin) offer list order match UI
• API: Conditionally block API's send payment sent/rcvd msgs
• API: Remove legacy bitcoind txindex param from apitest harness
• API: Block API takeoffer attempt if !sufficient btc in wallet
• API: Fix API CLI gettrades bug: category param can be uppercase
• API: Fix API editoffer bug: set fixed-price=0 on margin offers
• Bisq 2: Use bisq2 rest infrastructure for daonode
• Bisq 2: Tiny daonode rest service with 1 endpoint
• Bump actions/setup-java from 3.2.0 to 3.3.0
• Bump actions/setup-java from 3.1.1 to 3.2.0

New Assets

No new assets added.

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 (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.9.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/app/desktop-1.9.4-all.jar
The output need to match the value from the Bisq-1.9.4.jar.txt file.

There are three hashes within the Bisq-1.9.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 15.0.6 and the v1.9.4 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

API

Starting with v1.9.0 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.4.zip) and Bisq daemon (bisq-daemon-v1.9.4.zip) to use Bisq without touching the user interface.

Just download the archives and extract them locally. You have to run the daemon to access the local Bisq daemon API endpoints.

To run daemon.jar on Mainnet:

$ java -jar daemon.jar --apiPassword=becareful

If you just want to control your headless daemon within your terminal you have to run the Bisq cli as well.

Again just download the bisq-cli archive and extract it locally.

To call getversion from cli.jar

$ java -jar cli.jar --password=becareful getversion

You can use the Bisq API to access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades.

The Bisq API is based on the gRPC framework, and any supported gRPC language binding can be used to call Bisq API endpoints.

You'll find in-depth documentation and examples under following link: https://bisq-network.github.io/slate/#introduction

Bisq gRPC API reference documentation example source code is hosted on GitHub at https://github.com/bisq-network/bisq-api-reference. Java and Python developers interested in bot development may find this Intellij project useful for running the existing examples, and writing their own bots.

For additional developer support please join Development - Bisq v1 on Matrix.

Known issues with installation

Windows:

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

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

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

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

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq/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-1.9.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.

Credits

Thanks to everyone who directly contributed to this release:

• @alkum
• @chimp1984
• @Emzy
• @ghubstan
• @jmacxx
• @ripcurlx
• @xyzmaker123

A special thanks to our first time contributors:

• @alkum: Pricenode: Add JVM flag ExitOnOutOfMemoryError

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

v1.9.3

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

Release notes

This release improves XMR trade security by using subaddresses, improves Tor connectivity, and ships bug fixes and minor improvements across the board.

Improvements

• Create new XMR subaddress for each trade
• Improve XMR proof service
• Reset Tor directory when a new release is downloaded
• Adopt economyFee recommendation from Mempool rate provider
• Add chart series for total trade fees
• Show changes in BSQ Supply over time
• Prevent account creation for banned Revolut GBP sort code 040075
• Improve wording & appearance of trade shutdown dialog
• Prevent shutdown if trade is in process of being taken
• Mark user's own offers in Market -> Offer book
• Attempt self-ping 3 times before reporting error with connectivity

Bug fixes

• NPE when duplicate offer with deleted account
• Include payment screen ref text message & fix sizing issues
• Signed account must show signed age
• Australia PayID was not displaying payment info on buyer trade
• Refactor BSQ fee validation to handle multiple tx inputs
• Fix refresh issue with x-axis tick labels (Market/Trade charts)
• Transactions view: fix NPE in column sorting when Memo is empty
• Update matching account toggle state when tab is selected

Development & Documentation

• Seednode: Install tor from tor repository and add external tor as default
• Seednode: Update Java version for install script
• Seednode: Clean up tor files at seed node startup
• Pricenode: Add JVM flag ExitOnOutOfMemoryError
• Pricenode: Upgrade to XChange 5.0.13
• Pricenode: configurable exclusion by provider currency
• API: Block API attempt to swap BSQ with insufficient funds
• API: Add API method getavgbsqprice
• API: Add API method getnetwork
• API: Make API getoffers (altcoin) offer list order match UI
• API: Conditionally block API's send payment sent/rcvd msgs
• API: Remove legacy bitcoind txindex param from apitest harness
• API: Block API takeoffer attempt if !sufficient btc in wallet
• API: Fix API CLI gettrades bug: category param can be uppercase
• API: Fix API editoffer bug: set fixed-price=0 on margin offers
• Bisq 2: Use bisq2 rest infrastructure for daonode
• Bisq 2: Tiny daonode rest service with 1 endpoint
• Bump actions/setup-java from 3.2.0 to 3.3.0
• Bump actions/setup-java from 3.1.1 to 3.2.0

New Assets

No new assets added.

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 (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.9.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/app/desktop-1.9.3-all.jar
The output need to match the value from the Bisq-1.9.3.jar.txt file.

There are three hashes within the Bisq-1.9.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 15.0.6 and the v1.9.3 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

API

Starting with v1.9.0 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.3.zip) and Bisq daemon (bisq-daemon-v1.9.3.zip) to use Bisq without touching the user interface.

Just download the archives and extract them locally. You have to run the daemon to access the local Bisq daemon API endpoints.

To run daemon.jar on Mainnet:

$ java -jar daemon.jar --apiPassword=becareful

If you just want to control your headless daemon within your terminal you have to run the Bisq cli as well.

Again just download the bisq-cli archive and extract it locally.

To call getversion from cli.jar

$ java -jar cli.jar --password=becareful getversion

You can use the Bisq API to access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades.

The Bisq API is based on the gRPC framework, and any supported gRPC language binding can be used to call Bisq API endpoints.

You'll find in-depth documentation and examples under following link: https://bisq-network.github.io/slate/#introduction

Bisq gRPC API reference documentation example source code is hosted on GitHub at https://github.com/bisq-network/bisq-api-reference. Java and Python developers interested in bot development may find this Intellij project useful for running the existing examples, and writing their own bots.

For additional developer support please join Development - Bisq v1 on Matrix.

Known issues with installation

Windows:

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

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

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

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

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq/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-1.9.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.

Credits

Thanks to everyone who directly contributed to this release:

• @Devils-Knight
• @ghubstan
• @jmacxx
• @MarnixCroes
• @ripcurlx
• @xyzmaker123

A special thanks to our first time contributors:

• @Devils-Knight : Fix permissions for build.yml

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

v1.9.2

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

This is a hotfix release that adds the latest Tor version (v0.4.7.7) on top of v1.9.1 to improve connectivity caused by an ongoing DDoS attack on the Tor network.

For more details please see https://github.com/bisq-network/bisq/milestone/72.

Here are the release notes from v1.9.1:

Release notes

If you ever wanted to integrate Bisq into your project and/or to automate your most common use cases, now is the time to do it! This release ships an official API: a daemon (GRPC API endpoints) and a CLI. Please see the API section below for more details.

Aside from an API, we have simplified Bisq's navigation to make it easier to find what you are looking for:

• If you want to buy Bitcoin with EUR, just go to Buy > Bitcoin and select your preferred payment method
• If you want to buy BSQ, just go to Buy > BSQ

This approach gets rid of several intervening and (sometimes unintuitive) steps, so we hope it makes Bisq less mind-bending for new users.

And of course there are lots of bug fixes and improvements across the board.

Improvements

• Improve navigation structure
• Check failed trades for sensitive data purge
• Clarify that CBM / F2F not be used to advertise websites or contact info
• Clarify DAO status shown when in sync & peers have conflicts
• Editable account names
• IBAN validation for SEPA account
• Separate transaction details in funds views
• Dispute subsystem enhancements
• Add inbound Tor connectivity test
• Support Bitcoin Core v22 RPC for JSON export
• Add popup reminder to inform users of trading rules

Bug fixes

• Prevent multiple payout screens when agent repeat clicks on close ticket
• Prevent UI freeze in BSQ dashboard view
• Show correct buy BSQ state on activation for take offer
• Update trigger price validation
• Update currency related fields after switch of payment account
• Trigger price truncation of prompt text
• Fix corrupted MaxTradePeriod when offer payment method changed
• Fix the avatar trade count tag to include BSQ Swap trades
• Fix localization issue when accessing directories and JAR resource paths
• Fix fee request throttling
• Fix update number of open offers on change

Development & Documentation

• Add logo to README
• Fix permissions for build.yml
• API: Create API cli and daemon releases as zip archives
• API: Send pretty payment details to API clients
• API: Exclude persistedAccountName from API payment acct json forms
• API: Bug-fix for incorrect BsqSwap's OfferInfo.isActivated value
• API: Send meaningful io.grpc.Status.Code to gRPC clients
• API: Move get (cryptocurrency) offer filter to daemon
• API: Fix 3 misleading .proto TradeInfo field names
• API: Convert grpc.proto field names to snake_case
• API: Remove GetTradeStatistics service from grpc.proto
• API: Continue documenting grpc.proto for API reference site
• API: Clarify meaning of API/Offer related % fields
• API: Change TradeInfo proto's tradePrice & tradeVolume fields to string
• API: Change API OfferInfo volume/minVolume proto fields to string
• API: Change API grpc.proto triggerPrice field to string
• API: Change API's OfferInfo proto's price field to string
• API: Prepare API Offers .proto defs for significant changes
• API: Fix BSQ swap description of BTC price for 1 BSQ
• Bump actions/checkout from 3.0.0 to 3.0.1
• Bump actions/checkout from 2.4.0 to 3
• Bump actions/setup-java from 3.1.0 to 3.1.1
• Bump actions/setup-java from 2.5.0 to 3

New Assets

No new assets were added.

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 (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.9.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/app/desktop-1.9.2-all.jar
The output need to match the value from the Bisq-1.9.2.jar.txt file.

There are three hashes within the Bisq-1.9.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 15.0.6 and the v1.9.2 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

API

Starting with v1.9.0 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.2.zip) and Bisq daemon (bisq-daemon-v1.9.2.zip) to use Bisq without touching the user interface.

Just download the archives and extract them locally. You have to run the daemon to access the local Bisq daemon API endpoints.

To run daemon.jar on Mainnet:

$ java -jar daemon.jar --apiPassword=becareful

If you just want to control your headless daemon within your terminal you have to run the Bisq cli as well.

Again just download the bisq-cli archive and extract it locally.

To call getversion from cli.jar

$ java -jar cli.jar --password=becareful getversion

You can use the Bisq API to access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades.

The Bisq API is based on the gRPC framework, and any supported gRPC language binding can be used to call Bisq API endpoints.

You'll find in-depth documentation and examples under following link: https://bisq-network.github.io/slate/#introduction

Bisq gRPC API reference documentation example source code is hosted on GitHub at https://github.com/bisq-network/bisq-api-reference. Java and Python developers interested in bot development may find this Intellij project useful for running the existing examples, and writing their own bots.

For additional developer support please join Development - Bisq v1 on Matrix.

Known issues with installation

Windows:

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

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

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

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

v1.9.1

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

This is a follow-up release that fixes a null pointer exception when resolving a mediation with custom payout, fixes an API issue with AustrialianPayId and improves fee transaction validation.

See https://github.com/bisq-network/bisq/milestone/70?closed=1 for more details.

Here are the release notes from v1.9.0:

Release notes

If you ever wanted to integrate Bisq into your project and/or to automate your most common use cases, now is the time to do it! This release ships an official API: a daemon (GRPC API endpoints) and a CLI. Please see the API section below for more details.

Aside from an API, we have simplified Bisq's navigation to make it easier to find what you are looking for:

• If you want to buy Bitcoin with EUR, just go to Buy > Bitcoin and select your preferred payment method
• If you want to buy BSQ, just go to Buy > BSQ

This approach gets rid of several intervening and (sometimes unintuitive) steps, so we hope it makes Bisq less mind-bending for new users.

And of course there are lots of bug fixes and improvements across the board.

Improvements

• Improve navigation structure
• Check failed trades for sensitive data purge
• Clarify that CBM / F2F not be used to advertise websites or contact info
• Clarify DAO status shown when in sync & peers have conflicts
• Editable account names
• IBAN validation for SEPA account
• Separate transaction details in funds views
• Dispute subsystem enhancements
• Add inbound Tor connectivity test
• Support Bitcoin Core v22 RPC for JSON export
• Add popup reminder to inform users of trading rules

Bug fixes

• Prevent multiple payout screens when agent repeat clicks on close ticket
• Prevent UI freeze in BSQ dashboard view
• Show correct buy BSQ state on activation for take offer
• Update trigger price validation
• Update currency related fields after switch of payment account
• Trigger price truncation of prompt text
• Fix corrupted MaxTradePeriod when offer payment method changed
• Fix the avatar trade count tag to include BSQ Swap trades
• Fix localization issue when accessing directories and JAR resource paths
• Fix fee request throttling
• Fix update number of open offers on change

Development & Documentation

• Add logo to README
• Fix permissions for build.yml
• API: Create API cli and daemon releases as zip archives
• API: Send pretty payment details to API clients
• API: Exclude persistedAccountName from API payment acct json forms
• API: Bug-fix for incorrect BsqSwap's OfferInfo.isActivated value
• API: Send meaningful io.grpc.Status.Code to gRPC clients
• API: Move get (cryptocurrency) offer filter to daemon
• API: Fix 3 misleading .proto TradeInfo field names
• API: Convert grpc.proto field names to snake_case
• API: Remove GetTradeStatistics service from grpc.proto
• API: Continue documenting grpc.proto for API reference site
• API: Clarify meaning of API/Offer related % fields
• API: Change TradeInfo proto's tradePrice & tradeVolume fields to string
• API: Change API OfferInfo volume/minVolume proto fields to string
• API: Change API grpc.proto triggerPrice field to string
• API: Change API's OfferInfo proto's price field to string
• API: Prepare API Offers .proto defs for significant changes
• API: Fix BSQ swap description of BTC price for 1 BSQ
• Bump actions/checkout from 3.0.0 to 3.0.1
• Bump actions/checkout from 2.4.0 to 3
• Bump actions/setup-java from 3.1.0 to 3.1.1
• Bump actions/setup-java from 2.5.0 to 3

New Assets

No new assets were added.

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 (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.9.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/app/desktop-1.9.1-all.jar
The output need to match the value from the Bisq-1.9.1.jar.txt file.

There are three hashes within the Bisq-1.9.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 15.0.6 and the v1.9.1 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

API

Starting with v1.9.1 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.1.zip) and Bisq daemon (bisq-daemon-v1.9.1.zip) to use Bisq without touching the user interface.

Just download the archives and extract them locally. You have to run the daemon to access the local Bisq daemon API endpoints.

To run daemon.jar on Mainnet:

$ java -jar daemon.jar --apiPassword=becareful

If you just want to control your headless daemon within your terminal you have to run the Bisq cli as well.

Again just download the bisq-cli archive and extract it locally.

To call getversion from cli.jar

$ java -jar cli.jar --password=becareful getversion

You can use the Bisq API to access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades.

The Bisq API is based on the gRPC framework, and any supported gRPC language binding can be used to call Bisq API endpoints.

You'll find in-depth documentation and examples under following link: https://bisq-network.github.io/slate/#introduction

Bisq gRPC API reference documentation example source code is hosted on GitHub at https://github.com/bisq-network/bisq-api-reference. Java and Python developers interested in bot development may find this Intellij project useful for running the existing examples, and writing their own bots.

For additional developer support please join Development - Bisq v1 on Matrix.

Known issues with installation

Windows:

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

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

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

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

v1.9.0

Release notes

If you ever wanted to integrate Bisq into your project and/or to automate your most common use cases, now is the time to do it! This release ships an official API: a daemon (GRPC API endpoints) and a CLI. Please see the API section below for more details.

Aside from an API, we have simplified Bisq's navigation to make it easier to find what you are looking for:

• If you want to buy Bitcoin with EUR, just go to Buy > Bitcoin and select your preferred payment method
• If you want to buy BSQ, just go to Buy > BSQ

This approach gets rid of several intervening and (sometimes unintuitive) steps, so we hope it makes Bisq less mind-bending for new users.

And of course there are lots of bug fixes and improvements across the board.

Improvements

• Improve navigation structure
• Check failed trades for sensitive data purge
• Clarify that CBM / F2F not be used to advertise websites or contact info
• Clarify DAO status shown when in sync & peers have conflicts
• Editable account names
• IBAN validation for SEPA account
• Separate transaction details in funds views
• Dispute subsystem enhancements
• Add inbound Tor connectivity test
• Support Bitcoin Core v22 RPC for JSON export
• Add popup reminder to inform users of trading rules

Bug fixes

• Prevent multiple payout screens when agent repeat clicks on close ticket
• Prevent UI freeze in BSQ dashboard view
• Show correct buy BSQ state on activation for take offer
• Update trigger price validation
• Update currency related fields after switch of payment account
• Trigger price truncation of prompt text
• Fix corrupted MaxTradePeriod when offer payment method changed
• Fix the avatar trade count tag to include BSQ Swap trades
• Fix localization issue when accessing directories and JAR resource paths
• Fix fee request throttling
• Fix update number of open offers on change

Development & Documentation

• Add logo to README
• Fix permissions for build.yml
• API: Create API cli and daemon releases as zip archives
• API: Send pretty payment details to API clients
• API: Exclude persistedAccountName from API payment acct json forms
• API: Bug-fix for incorrect BsqSwap's OfferInfo.isActivated value
• API: Send meaningful io.grpc.Status.Code to gRPC clients
• API: Move get (cryptocurrency) offer filter to daemon
• API: Fix 3 misleading .proto TradeInfo field names
• API: Convert grpc.proto field names to snake_case
• API: Remove GetTradeStatistics service from grpc.proto
• API: Continue documenting grpc.proto for API reference site
• API: Clarify meaning of API/Offer related % fields
• API: Change TradeInfo proto's tradePrice & tradeVolume fields to string
• API: Change API OfferInfo volume/minVolume proto fields to string
• API: Change API grpc.proto triggerPrice field to string
• API: Change API's OfferInfo proto's price field to string
• API: Prepare API Offers .proto defs for significant changes
• API: Fix BSQ swap description of BTC price for 1 BSQ
• Bump actions/checkout from 3.0.0 to 3.0.1
• Bump actions/checkout from 2.4.0 to 3
• Bump actions/setup-java from 3.1.0 to 3.1.1
• Bump actions/setup-java from 2.5.0 to 3

New Assets

No new assets were added.

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 (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.9.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/app/desktop-1.9.0-all.jar
The output need to match the value from the Bisq-1.9.0.jar.txt file.

There are three hashes within the Bisq-1.9.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 15.0.6 and the v1.9.0 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

API

Starting with v1.9.0 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.0.zip) and Bisq daemon (bisq-daemon-v1.9.0.zip) to use Bisq without touching the user interface.

Just download the archives and extract them locally. You have to run the daemon to access the local Bisq daemon API endpoints.

To run daemon.jar on Mainnet:

$ java -jar daemon.jar --apiPassword=becareful

If you just want to control your headless daemon within your terminal you have to run the Bisq cli as well.

Again just download the bisq-cli archive and extract it locally.

To call getversion from cli.jar

$ java -jar cli.jar --password=becareful getversion

You can use the Bisq API to access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades.

The Bisq API is based on the gRPC framework, and any supported gRPC language binding can be used to call Bisq API endpoints.

You'll find in-depth documentation and examples under following link: https://bisq-network.github.io/slate/#introduction

For additional developer support please join Development - Bisq v1 on Matrix.

Known issues with installation

Windows:

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

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

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

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

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq/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-1.9.0.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Credits

Thanks to everyone who directly contributed to this release:

• @Devils-Knight
• @ghubstan
• @jmacxx
• @MarnixCroes
• @ripcurlx
• @xyzmaker123

A s...

v1.8.4

This is a follow-up release that fixes the news badge on Settings for existing Bisq users and handles an additional case where the DAO needs resync.

See https://github.com/bisq-network/bisq/milestone/69?closed=1 for more details.

Here are the release notes from v1.8.3:

Release notes

This release improves privacy by automatically deleting past trade data, improves the UI in many places, and fixes bugs across the board (as always).

Improvements

• Clear payment account payload info from closed trades
• Allow dispute to be closed if trade has paid out
• Include penalty for exceeding transfer limits
• Show buyer/seller in terms of BTC
• Show signed payment account status when applicable in Trade & Dispute information screens
• Show proposal transaction ID with explore and copy icons
• Sign/Verify message for DAO bonded roles
• Obtain trade fee settings from filter
• Warn and prompt for password before showing wallet keys
• Add ability to copy popup text to clipboard
• Add support/help links on the UI
• Add filter option to lists
• Improve text and icon colors for disabled offers
• Remove references to Keybase and switch to Matrix
• Improve BSQ swap error messaging & DAO resync popup

Bug fixes

• Fix exception: heightOfLastBlock must match chainHeight
• Fix issue selecting specific BSQ UTXO for sending BSQ
• Fix error in failed trades view when trade contract is null
• Fix NullPointerException when editing a new payment account
• Fix unhandled exception when locale specifies unknown country/region code.
• Fix column sorting
• Fix sorting on bonded roles view
• Prevent reset offer values after switch to same currency payment account
• Filter out the BSQ swap payment method from dropdown on edit/duplicate offer
• Fix CSV export issue on open offers view
• Enable Tor bridges set in application settings
• Get payment method ID from offerPayload: 1, 2
• Disable roll over popups in combobox item renderers.

Development & Documentation

• API: Add API gettrades method
• API: Fix FeeService NullPointerException
• Update copyright string for Windows
• Update copyright string for macOS
• Cleanup: remove unused classes
• Improve instructions and wording
• Update hostname of BSQ explorer mempool.emzy.de

New Assets

No new assets were added.

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 (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.8.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/app/desktop-1.8.4-all.jar
The output need to match the value from the Bisq-1.8.4.jar.txt file.

There are three hashes within the Bisq-1.8.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 15.0.5 and the v1.8.4 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

Known issues with installation

Windows:

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

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

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

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

Linux:

Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq/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-1.8.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.

Credits

Thanks to everyone who directly contributed to this release:

• @Emzy
• @ghubstan
• @jmacxx
• @MarnixCroes
• @MwithM
• @ripcurlx
• @sqrrm
• @w0000000t
• @wiz
• @xyzmaker123

A special thanks to our first time contributors:

• @MarnixCroes: Update Apple plist copyright notice

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