Skip to content

v2.0.4
Compare
Choose a tag to compare
@alejandrogarcia83 alejandrogarcia83 released this 24 May 03:55
· 2163 commits to main since this release
v2.0.4
This tag was signed with the committer’s verified signature. The key has expired.
alejandrogarcia83 Alejandro García
GPG key ID: F806F422E222AA02
Expired
Learn about vigilant mode.
163eb82
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

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
    Screenshot 2024-05-24 at 15 51 17
  • Offerbook list and markets list are collapsable for minimized layout
    Screenshot 2024-05-24 at 16 05 07
  • 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
    Screenshot 2024-05-24 at 15 51 39
  • 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.

Assets 14
Loading