v1.2.8

This release is not stable, please revert to v1.2.7 if you are seeing issues during startup
Binaries have been removed until #4052 is fixed and released in a hotfix

Release notes

This release is, once again, packed with bug fixes and improvements. Most notably, it checks for errors in local Bitcoin Core node configuration and reduces the intervals in which users can trigger a trade process refresh.

UI

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

Trading

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

Wallet

• Add local Bitcoin node configuration detection

Performance

• Speed up DAO state monitor view load

Privacy

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

Configuration

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

Network

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

Monitor

• Added monitoring install scripts

Support

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

Assets

No assets were added.

Verification

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

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.2.8.dmg)

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

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

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

Windows:

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

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

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

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

Linux:

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

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.2.8.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Cleanup tool for saved trades that failed market price check

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

v1.2.7

This is a hotfix release covering following issue:

• App freezes with blurred background on startup when launched on macOS Mojave or older.

Here are the release notes from v1.2.6:

Release notes

This release is packed with performance improvements and bug fixes. Most notably, this version introduces an option to refresh the trade process if it gets stuck during payment confirmation and adds Liquid Bitcoin (L-BTC) as a new asset.

DAO

• Add new BSQ issued v. burnt chart
• Improve readability of the daily burnt BSQ chart

UI

• Don't show decimals for rounded fiat amounts: 1, 2
• Fix account age format when ending in 1
• Fix incorrect display of delete button next to open proposals
• Fix popup message about trade limits
• Use macOS app Info.plist setting for automatic light/dark title bar
• Remove "beta" label from Dark Theme slider switch text

Trading

• Trade process refresh option if trade is stuck

Performance

• Prevent memory leak in CandleStickChart & VolumeChart
• Fix potential resource leak in AvoidStandbyModeService

Privacy

• Remove unused uid in price feed service

Network

• Temporarily deactivate public network option
• Remove Bitcoin Core nodes not operated by Bisq btcnode team members

Support

• Add signing debug logs
• Dump delayed payout transaction hashes to local file

Assets

One new asset was added: Liquid Bitcoin (L-BTC)

Verification

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

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.2.7.dmg)

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

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

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

Windows:

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

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

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

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

Linux:

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

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.2.7.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Cleanup tool for saved trades that failed market price check

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

v1.2.6

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

Release notes

This release is packed with performance improvements and bug fixes. Most notably, this version introduces an option to refresh the trade process if it gets stuck during payment confirmation and adds Liquid Bitcoin (L-BTC) as a new asset.

DAO

• Add new BSQ issued v. burnt chart
• Improve readability of the daily burnt BSQ chart

UI

• Don't show decimals for rounded fiat amounts: 1, 2
• Fix account age format when ending in 1
• Fix incorrect display of delete button next to open proposals
• Fix popup message about trade limits
• Use macOS app Info.plist setting for automatic light/dark title bar
• Remove "beta" label from Dark Theme slider switch text

Trading

• Trade process refresh option if trade is stuck

Performance

• Prevent memory leak in CandleStickChart & VolumeChart
• Fix potential resource leak in AvoidStandbyModeService

Privacy

• Remove unused uid in price feed service

Network

• Temporarily deactivate public network option
• Remove Bitcoin Core nodes not operated by Bisq btcnode team members

Support

• Add signing debug logs
• Dump delayed payout transaction hashes to local file

Assets

One new asset was added: Liquid Bitcoin (L-BTC)

Verification

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

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.2.6.dmg)

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

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

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

Windows:

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

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

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

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

Linux:

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

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.2.6.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Cleanup tool for saved trades that failed market price check

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

v1.2.5

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

Release notes

This release is packed with performance improvements and bug fixes. To discourage future-style trades and minimize mediation cases, this update also increases minimum security deposits.

DAO

• Add two new columns to vote result
• Make all DAO screen tables resize to max. screen height

UI

• Show the correct sign state icon for accounts that are able to sign
• Display minimum limit if used during trade
• Add report feature for disputes
• Fix bank account number label for Swedish language
• Improve trade limit error message
• Fix dark mode issues: 1, 2, 3, 4
• Display language switch warning based on supported languages by mediators and refund agents
• Rename "Spread" tab to a more general "Details"
• Fix double presence of the word "days"
• Fix closed state handling for mediation cases

Trading

• Increase security deposits
• Only move trades to failed trades if the reject message is critical
• Not allow bitcoinj to autoconnect to localhost when localhost was not detected by client
• Only accept phone number for new Revolut accounts

Performance

• Speed up DAO vote and BSQ Transactions screen
• Speed up trades charts view load
• Fix temp file path memory leak

Wallet

• Improve handling of spv resync edge case
• Validate wallet date when restoring from seed

Network

• Added four new BSQ explorers: 1, 2
• Add random BSQ explorer selection: 1, 2
• Upgrade mempool.space to full block explorer
• Re-enable mbm6ffx6j5ygi2ck.onion btcnode operated by @KanoczTomas
• Temporarily disable z33nukt7ngik3cpe btcnode due to failing service checks
• Update seed node install script: 1, 2, 3

Build

• Add developer code signing for Windows binary

Assets

No new assets where added.

Verification

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

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.2.5.dmg)

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

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

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

Windows:

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

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

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

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

Linux:

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

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.2.5.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Cleanup tool for saved trades that failed market price check

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

v1.2.4

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

Release notes

This release is packed with bug fixes and improvements. It improves mailbox handling when a trading peer or arbitrator/mediator is offline, shows account age for high-risk payment methods in the UI, and should improve the trade process robustness in general.

DAO

• Only show accepted bonded roles in bond view

UI

• Text improvements: 1, 2, 3, 4, 5, 6
• Fix malformed trade chat & dispute speech bubbles
• Replace arbitration link in terms and conditions
• Use correct language tags for script and regional language variants
• Add traditional Chinese

Trading

• Re-introduce account age to payment methods with high chargeback risk
• Improve account signing security
• Fix possiblePaymentAccounts.isEmpty() bug when trying to take an offer with a MIN/MAX range
• Update trading instruction for XMR (Monero)
• Fix problem with MoneyGram account creation
• Fix bug that new payment accounts for specific payment methods couldn't be removed without restart
• Prevent taking of offers with unequal bank account types (excl. SEPA)
• Added check for empty fields for general bank accounts and MoneyBeam on creation
• Added check for empty fields in PopMoney, Uphold, Revolut and Zelle accounts on creation
• Use 2of2 multisig deposit transaction version for manual payout
• Not use 0 BTC outputs
• Fix problem of trades with mediated payout end up in failed trades

Performance

• Fix resource leak caused by not cleaning up unused threads

Network

• Fix cases where removal of mailbox message wasn't possible: 1, 2
• Properly remove expire entries on disconnect
• Fix bug of unnecessary syncing of temporary proposal payloads

Installation

• Check for special characters in installation path on Windows that prevented the app to start

Development

• Fix failing test when there are spaces in the project path
• Upgrade Gradle wrapper to version 5.6.4
• Upgrade Gradle Shadow plugin from 4.0.2 to 5.2.0
• Upgrade JavaFX to 11.0.2

Build

• Improve version parsing for Windows

Assets

No new assets where added.

Verification

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

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.2.4.dmg)

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

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

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

Windows:

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

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

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

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

Linux:

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

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.2.4.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Cleanup tool for saved trades that failed market price check

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

v1.2.3

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

Release notes

This version improves the handling of failed trades and offers, loads the trade statistics on startup again and includes many more minor bug fixes and improvements.

DAO

• Fix proposal table hide when switching to another screen and back

UI

• Remove donation link
• Fix invalid comparators
• Fix BTC valuation popups
• Remove duplicate word in user agreement
• Select default markets view when last navigation no longer exists

Trading

• Fix initial trading statistics retrieval
• Improve handling of failed trades and offers
• Only show approval icon for signer accounts
• Fix account signing state for peer info window

Wallet

• Check for dust after subtracting fee, not before

Network

• Limit max. nr. of PersistableNetworkPayload and ProtectedStorageEntries
• Update seednode config to increase resource limits

Development

• Use @Getter annotation for appDataDir
• Create getListProperty
• Change type of ignoreLocalBtcNode to boolean

Assets

Added one new asset: LBRY Credits (LBC)

Verification

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

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.2.3.dmg)

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

Known issues with installation

macOS Catalina:

Bisq would like to receive keystrokes from any application.

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

Windows:

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

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

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

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

Linux:

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

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.2.3.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Cleanup tool for saved trades that failed market price check

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

v1.2.2

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

This is a hotfix release mainly covering following issue:

• Add new trade statistics capability (network improvement)

Here are the release notes from v1.2.1:

Release notes

Bisq v1.2 ships several significant updates. A new trade protocol moves to 2-of-2 multisig escrows for deposit funds, dispute resolution is overhauled to be more private and scalable, and account signing removes 0.01 BTC buying limits for risky payment methods in major markets.

If you are updating from a previous version of Bisq, please make sure to do the following before updating to v1.2:

• complete all trades
• complete all disputes
• disable open offers (at "Portfolio/My Open Offers")

Updating to v1.2 with unfinished trades and disputes will require an arbitrator to intervene and manually make payouts. Downgrading back to v1.1.7 to rectify the situation will not be possible, so please double-check before updating.

DAO

• Apply rule to not allow BSQ outputs after BTC output for regular txs
• Fix bug with not updating vote result table at vote result block
• Fix vote results view

UI

• Translation improvements 1
• Translate name of Japan Bank Transfer for non-Japanese users

Trading

• Fix incorrect display of account signing status: 1, 2
• Remove unnecessary restriction for sell offers
• New trade protocol: 1, 2, 2, 3, 4, 5, 6, 7, 8, 9, 10,
• Account signing: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26
• Add mediator prefix to trade statistics
• Add combo block explorer for Blockstream.info + Mempool.space
• Increase minimum TX fee to 2 sats/vByte
• Not show payment account details for blocked offers
• Clean up trade statistics from duplicate entries
• Format maker fee for BTC and BSQ correctly
• Improve mediation result popup handling

Wallet

• Show connected Bitcoin network peer info

Assets

Added 8 new assets: Animecoin (ANI), CTSCoin (CTSC), Donu (DONU), Faircoin (FAIR), Krypton (ZOD), ndau (XND), NoteBlockchain (NTBC), uPlexa (UPX)

Removed two assets: Byte (GBYTE), Neos (NEOS)

Verification

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

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.2.2.dmg)

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

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/Bisq

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.2.2.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Cleanup tool for saved trades that failed market price check

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

v1.2.1

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

This is a hotfix release mainly covering following issues:

• Fix incorrect display of account signing status: 1, 2
• Remove unnecessary restriction for sell offers

Here are the release notes from v1.2.0:

Release notes

Bisq v1.2 ships several significant updates. A new trade protocol moves to 2-of-2 multisig escrows for deposit funds, dispute resolution is overhauled to be more private and scalable, and account signing removes 0.01 BTC buying limits for risky payment methods in major markets.

If you are updating from a previous version of Bisq, please make sure to do the following before updating to v1.2:

• complete all trades
• complete all disputes
• disable open offers (at "Portfolio/My Open Offers")

Updating to v1.2 with unfinished trades and disputes will require an arbitrator to intervene and manually make payouts. Downgrading back to v1.1.7 to rectify the situation will not be possible, so please double-check before updating.

DAO

• Apply rule to not allow BSQ outputs after BTC output for regular txs
• Fix bug with not updating vote result table at vote result block
• Fix vote results view

UI

• Translation improvements 1
• Translate name of Japan Bank Transfer for non-Japanese users

Trading

• New trade protocol: 1, 2, 2, 3, 4, 5, 6, 7, 8, 9, 10,
• Account signing: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26
• Add mediator prefix to trade statistics
• Add combo block explorer for Blockstream.info + Mempool.space
• Increase minimum TX fee to 2 sats/vByte
• Not show payment account details for blocked offers
• Clean up trade statistics from duplicate entries
• Format maker fee for BTC and BSQ correctly
• Improve mediation result popup handling

Wallet

• Show connected Bitcoin network peer info

Assets

Added 7 new assets: Animecoin (ANI), CTSCoin (CTSC), Donu (DONU), Faircoin (FAIR), ndau (XND), NoteBlockchain (NTBC), uPlexa (UPX)

Removed two assets: Byte (GBYTE), Neos (NEOS)

Verification

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

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.2.1.dmg)

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

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/Bisq

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.2.1.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Cleanup tool for saved trades that failed market price check

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

v1.2.0

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

Release notes

Bisq v1.2 ships several significant updates. A new trade protocol moves to 2-of-2 multisig escrows for deposit funds, dispute resolution is overhauled to be more private and scalable, and account signing removes 0.01 BTC buying limits for risky payment methods in major markets.

If you are updating from a previous version of Bisq, please make sure to do the following before updating to v1.2:

• complete all trades
• complete all disputes
• disable open offers (at "Portfolio/My Open Offers")

Updating to v1.2 with unfinished trades and disputes will require an arbitrator to intervene and manually make payouts. Downgrading back to v1.1.7 to rectify the situation will not be possible, so please double-check before updating.

DAO

• Apply rule to not allow BSQ outputs after BTC output for regular txs
• Fix bug with not updating vote result table at vote result block
• Fix vote results view

UI

• Translation improvements 1
• Translate name of Japan Bank Transfer for non-Japanese users

Trading

• New trade protocol: 1, 2, 2, 3, 4, 5, 6, 7, 8, 9, 10,
• Account signing: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26
• Add mediator prefix to trade statistics
• Add combo block explorer for Blockstream.info + Mempool.space
• Increase minimum TX fee to 2 sats/vByte
• Not show payment account details for blocked offers
• Clean up trade statistics from duplicate entries
• Format maker fee for BTC and BSQ correctly
• Improve mediation result popup handling

Wallet

• Show connected Bitcoin network peer info

Assets

Added 7 new assets: Animecoin (ANI), CTSCoin (CTSC), Donu (DONU), Faircoin (FAIR), ndau (XND), NoteBlockchain (NTBC), uPlexa (UPX)

Removed two assets: Byte (GBYTE), Neos (NEOS)

Verification

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

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.2.0.dmg)

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

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/Bisq

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

cd ~/Downloads  
mkdir tmp  
cd tmp   
ar x ../Bisq-64bit-1.2.0.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Cleanup tool for saved trades that failed market price check

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

v1.1.7

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

This is a hotfix release mainly covering following issue:

• Fix missing handler for mediator mailbox messages

Here are the release notes from v1.1.6:

Release notes

This version includes important improvements which require that all traders update for compatibility reasons.
Trader chat enables users to have direct encrypted communication during the trade to resolve minor problems.
Mediation is an additional dispute resolution layer before a trade goes to arbitration. Mediators do not have a key in the multisig escrow, so they can only evaluate a situation and make a suggestion. If this suggestion is accepted by both traders, the trade can be completed without involving an arbitrator. Otherwise, the trade goes to arbitration. See more information here.
For backward compatibility reasons, mediation will be activated in 2 steps.

• By September 19, all traders need to have updated to v1.1.6, or they will not be able to trade.
• On September 26, mediation will become available.

Additionally this version features a dark mode, adds Japan Bank transfer and we've lifted the 0.01 BTC limit for all markets except USD, EUR, CAD, GBP, AUD and BRL.

DAO

• Avoid validating proposals during initial sync
• Check that proposal is in correct cycle for vote result
• Don't force close on checkpoint fail
• Prevent NullPointerException in proposals view
• Fix incorrect DAO full node check when loading preferences
• Improve processing of removed proposals
• Update data storage on expired data removal
• Do not send BSQ blocks to full nodes
• Group burned BSQ by day
• Add average BSQ price in Dashboard
• Add BSQ price trend indicator

UI

• Add dark mode
• Translation improvements
• High/low values are swapped in trade statistics candle popup
• Show median value in trade statistics candle popup
• Confusing message after making a payment
• Update trading amount on Error to prevent popup loop
• Improve usage of available height for lists
• Fix bugs in searchable dropdown
• Increase top navigation button text size for Japanese locale

Trading

• Add mediation support
• Add chat for traders
• Add new payment method: Japan Bank Transfer
• Add Export to CSV in Portfolio History
• Render proper column headers and values for CSV exports
• Auto remove whitespace in the IBAN input field

Wallet

• Make RPC host configurable

Security

• Update Tor to 0.4.0.5

Monitoring

• Lots of minor Monitor improvements

Development

• Log stacktrace to logfile when a task fails

Assets

• Namecoin (NMC) update AddressValidator
• Update KYD to KYDC listing to be conform ISO_4217
• Update legacy assets with proper AddressValidator
• Add support for Monero integrated addresses

Added 14 new asset: DarkPay (D4RK), Emercoin (EMC), Ergo (ERG), Know Your Developer (KYDC), Kore (KORE), Masari (MSR), Particl (PART), PENG Coin (PENG), SixEleven (SIL), Solo (XSL), VARIUS Coin (VARIUS), Vertcoin (VTC), WORX Coin (WORX)

Verification

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

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.1.7.dmg)

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

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/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.1.7.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Cleanup tool for saved trades that failed market price check

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