Latest Release

Release notes
Note: v1.9.21 is a hotfix for pre-release v1.9.20.
Improvements

Add 3 new bitcoin nodes
Updated dao datastores to speedup and improve resyncs
The burning man accounting sync got faster because we sort the blocks linearly. Before each time a block was added Bisq had to scan the list of blocks for duplicated and the last block.
Show a warning when a user tries to burn BSQ with a pre-image that contains leading or trailing spaces.
The backup zip file compession got faster and more reliable.

Bug fixes

Trading

An edge-case lead to failed trades where both traders couldn't agree on the correct burning man selection height. Now it works as it should.
Enforce the version check when an offer gets taken. Before we checked it at every step and users on older version couldn't mark a payment as sent or confirm it.


Add --useFullModeDaoMonitor to seednode setups. Without this option full nodes won't compute all dao hashes themselves.
The mediaton payout screen reflects the trade limit current now.
XMR subaddress

The XMR subaddress popup was shown to every user when they navigated to the payment account section. Now, we only show the popup when the user creates an XMR account or they have an existing non-subaddress account.
Fixed broken link to XMR subaddress documentation page


API

The PaymentAccountForm excludes the extraData field in PaymentAccounts now. Before this caused issues creating payment accounts.
We fixed a bug where the edit offer parser used the fixed price when a trigger price was used.



See all changes at https://github.com/bisq-network/bisq/milestone/88?closed=1 .
To verify this release please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file
API
Starting with v1.9.0 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.21.zip) and Bisq daemon (bisq-daemon-v1.9.21.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:
bash
$ 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
bash
$ 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 https://github.com/bisq-network/bisq/discussions/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\\AppData\Local\Bisq
[2] Data directory (contains all Bisq data including wallet):
C:\Users\\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.21.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:
- @alvasw
- @devinbileck
- @HenrikJannsen
- @petryshkaCODE
- @runbtc
- @stejbac
- @suddenwhipvapor
- @thecockatiel
As well as to everyone that helped with translations on Transifex.