v1.1.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.1.7

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.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.1.6.jar
The output need to match the value from the Bisq-1.1.6.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.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.1.6 or later. You can verify the binary the same way as you do with the Bisq application.

v1.1.5

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

This is a hotfix release mainly covering following issue:

DAO data store wasn't properly synchronized (again)

Here are the release notes from v1.1.3:

Release notes

This is a bug fix and network improvement release. You'll see faster startup and synchronization times and it includes lots of smaller bug fixes and improvements as well.

DAO

• Handling of revealing of late votes
• Limit BSQ validator to 10M BSQ
• Display changed param value at proposal time
• Handle null tx for unconfirmed BSQ change output
• Don't dump blockchain data during initial parsing
• Limit number of blocks sent in GetBlocksResponse
• Fixes for initial block sync

UI

• Hide extreme offers in chart
• Label offers correctly for removed assets

Trading

• Fix acknowledgement message for available offers
• Use tempTradingPeerNodeAddress if the trade doesn't have a trading peer set yet
• Fix offer editing for low volume offers
• Fix missing payment info on SEPA Instant trades
• Exclude non executed BSQ trade

Wallet

• Update BitcoinJ checkpoint files
• Wait for initialized wallet before processing dispute msgs
• Add option to ignore local bitcoin node

Network

• Bundling of envelopes: 1, 2

Monitoring

• Monitor is aware of the DAO (monitor.bisq.network)
• Monitor reports BSQBlock head

Development

• Improve setup instructions for Windows
• Resurrect testnet
• Update command to generate blocks

Assets

Added four new asset: Genesis (GENX), Know Your Developer (KYD), Myce (YCE), Starwels (USDH)

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.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.1.5.jar
The output need to match the value from the Bisq-1.1.5.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.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.1.5 or later. You can verify the binary the same way as you do with the Bisq application.

v1.1.4

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

This is a hotfix release mainly covering following issue:

• DAO data store wasn't properly synchronized

It also introduces Japanese as a new language on Bisq (thanks @jmaurice)

Here are the release notes from v1.1.3:

Release notes

This is a bug fix and network improvement release. You'll see faster startup and synchronization times and it includes lots of smaller bug fixes and improvements as well.

DAO

• Handling of revealing of late votes
• Limit BSQ validator to 10M BSQ
• Display changed param value at proposal time
• Handle null tx for unconfirmed BSQ change output
• Don't dump blockchain data during initial parsing
• Limit number of blocks sent in GetBlocksResponse
• Fixes for initial block sync

UI

• Hide extreme offers in chart
• Label offers correctly for removed assets

Trading

• Fix acknowledgement message for available offers
• Use tempTradingPeerNodeAddress if the trade doesn't have a trading peer set yet
• Fix offer editing for low volume offers
• Fix missing payment info on SEPA Instant trades
• Exclude non executed BSQ trade

Wallet

• Update BitcoinJ checkpoint files
• Wait for initialized wallet before processing dispute msgs
• Add option to ignore local bitcoin node

Network

• Bundling of envelopes: 1, 2

Monitoring

• Monitor is aware of the DAO (monitor.bisq.network)
• Monitor reports BSQBlock head

Development

• Improve setup instructions for Windows
• Resurrect testnet
• Update command to generate blocks

Assets

Added four new asset: Genesis (GENX), Know Your Developer (KYD), Myce (YCE), Starwels (USDH)

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.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.1.4.jar
The output need to match the value from the Bisq-1.1.4.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.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.1.4 or later. You can verify the binary the same way as you do with the Bisq application.

v1.1.3

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

Release notes

This is a bug fix and network improvement release. You'll see faster startup and synchronization times and it includes lots of smaller bug fixes and improvements as well.

DAO

• Handling of revealing of late votes
• Limit BSQ validator to 10M BSQ
• Display changed param value at proposal time
• Handle null tx for unconfirmed BSQ change output
• Don't dump blockchain data during initial parsing
• Limit number of blocks sent in GetBlocksResponse
• Fixes for initial block sync

UI

• Hide extreme offers in chart
• Label offers correctly for removed assets

Trading

• Fix acknowledgement message for available offers
• Use tempTradingPeerNodeAddress if the trade doesn't have a trading peer set yet
• Fix offer editing for low volume offers
• Fix missing payment info on SEPA Instant trades
• Exclude non executed BSQ trade

Wallet

• Update BitcoinJ checkpoint files
• Wait for initialized wallet before processing dispute msgs
• Add option to ignore local bitcoin node

Network

• Bundling of envelopes: 1, 2

Monitoring

• Monitor is aware of the DAO (monitor.bisq.network)
• Monitor reports BSQBlock head

Development

• Improve setup instructions for Windows
• Resurrect testnet
• Update command to generate blocks

Assets

Added four new asset: Genesis (GENX), Know Your Developer (KYD), Myce (YCE), Starwels (USDH)

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.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.1.3.jar
The output need to match the value from the Bisq-1.1.3.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.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.1.3 or later. You can verify the binary the same way as you do with the Bisq application.

v1.1.2

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

Release notes

This version fixes DAO synchronization issues with seed nodes on startup and also includes additional bug fixes and improvements.

DAO

• Add missing dust check
• Fix synchronization issue with seed nodes on startup
• Fix DAO sync text after restore from seed
• Fix confirm lockup transaction prompt showing incorrect estimated time
• Fix peer handling for address display and signing

UI

• Fix linguistic issues in the English version
• Fix issue with label width in contract window and add deposits in dispute summary

Trading

• Use minTakerFee when calculating taker fee

Privacy

• Fix useless use of IPv6 (Tails interop issue)

Assets

Added two new asset: Burnt BlackCoin (BLK-BURNT), ZeroClassic (ZERC)

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.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.1.2.jar
The output need to match the value from the Bisq-1.1.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.1.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.

v1.1.1

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

This is a hotfix release mainly covering following issue:

• Allow seller to take any offers

Here are the release notes from v1.1.0:

Release notes

This release adds an impotant security meassurement to protect against the bank chargeback scammer. With this in place we can remove the banning of certain SEPA regions and Interac scheduled for the 5th of May.

The new restrictions are as follows:
If a fiat payment account was created after March 1st 2019 it is considered risky and limited to 0.01 BTC trades if the account holder is the BTC buyer. For the seller there is no restriction. The restriction is applied to all payment methods based on bank transfers which carry some chargeback risk (Sepa, Sepa Instant, Interact, Zelle, Revolut, National bank transfers, Chase Quick Pay, Popmoney, Moneybeam, Uphold).

On May 5th we will block old accounts from trading to enable us to unblock the banned SEPA regions and Interac. So please update as soon as possible!

This solution is an intermediary step on the way to a more sophisticated protection solution (see proposals) but those will require more time to get implemented.

Beside that there are some other important fixes:

• Fix account age display in peer avatar
• Decrease the security deposit amount for altcoins
• Improve BSQ block propagation
• Add search field to trade history

DAO

• Request blocks in case we have not received it
• Add node address and capabilities to prevent timeout
• Fix issues with DAO full mode in preferences
• Count cycles correctly

UI

• Add UTF8 for getBytes calls
• Use existing styling for developer alert message
• Use same precision for all x-axis labels

Trading

• Add check for account age to apply restrictions
• Improve ignore list
• Improve handling of editing of offers with invalid security deposit
• Use different security deposit for fiat-crypto and crypto-crypto trades
• Add filter to trade history
• Fix account age display of peer
• Don't disable confirm buttons

Wallet

• Set p2shHeader to fix address validation issues

Development

• Remove BSQ filter for crypto currencies
• Reflect pricenode operator change in ProvidersRepository
• Update mobile notification relay node DEV_URL IP address

Assets

Added two new asset: List Trust Eth reOrigin (TEO) and ParsiCoin (PARS)

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.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.1.1.jar
The output need to match the value from the Bisq-1.1.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.1.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.

v1.1.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.1.1

Release notes

This release adds an impotant security meassurement to protect against the bank chargeback scammer. With this in place we can remove the banning of certain SEPA regions and Interac scheduled for the 5th of May.

The new restrictions are as follows:
If a fiat payment account was created after March 15th 2019 it is considered risky and limited to 0.01 BTC trades if the account holder is the BTC buyer. For the seller there is no restriction. The restriction is applied to all payment methods based on bank transfers which carry some chargeback risk (Sepa, Sepa Instant, Interact, Zelle, Revolut, National bank transfers, Chase Quick Pay, Popmoney, Moneybeam, Uphold).

On May 5th we will block old accounts from trading to enable us to unblock the banned SEPA regions and Interac. So please update as soon as possible!

This solution is an intermediary step on the way to a more sophisticated protection solution (see proposals) but those will require more time to get implemented.

Beside that there are some other important fixes:

• Fix account age display in peer avatar
• Decrease the security deposit amount for altcoins
• Improve BSQ block propagation
• Add search field to trade history

DAO

• Request blocks in case we have not received it
• Add node address and capabilities to prevent timeout
• Fix issues with DAO full mode in preferences
• Count cycles correctly

UI

• Add UTF8 for getBytes calls
• Use existing styling for developer alert message
• Use same precision for all x-axis labels

Trading

• Add check for account age to apply restrictions
• Improve ignore list
• Improve handling of editing of offers with invalid security deposit
• Use different security deposit for fiat-crypto and crypto-crypto trades
• Add filter to trade history
• Fix account age display of peer
• Don't disable confirm buttons

Wallet

• Set p2shHeader to fix address validation issues

Development

• Remove BSQ filter for crypto currencies
• Reflect pricenode operator change in ProvidersRepository
• Update mobile notification relay node DEV_URL IP address

Assets

Added two new asset: List Trust Eth reOrigin (TEO) and ParsiCoin (PARS)

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.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.1.0.jar
The output need to match the value from the Bisq-1.1.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.1.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.

v1.0.1

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

This is a hotfix release mainly covering following two issues:

• Rebroadcast new blocks at lite nodes to improve DAO synchronization
• Fix wrong calculation of percentage based security deposit in edit offer screen

Here are the release notes from v1.0.0:

Release notes

We are proud to announce the release of version 1.0 - the most important milestone since Bisq has been launched!

• Bisq’s trading network was already decentralized. With the Bisq DAO, Bisq’s leadership is now decentralized too, making Bisq exceptionally resistant to censorship.
• Get a 90% discount on trading fees when you use BSQ. Save money and support the project at the same time!
• Trade BSQ (colored bitcoin) to participate in Bisq governance. You can buy and sell BSQ just like any other asset on Bisq.

Bisq DAO

• Add genesis transaction and changes required for v1.0.0
• Improve handling of DAO state conflicts
• Add DAO launch popup 1, 2, 3, 3, 4
• Add missing check to prevent re-selection of proposal

UI

• Update list of removed assets
• Left align hyperlinks
• Remove non-core languages (ro, hu, sr)
• Prevent text overlapping in popups

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.0.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.0.1.jar
The output need to match the value from the Bisq-1.0.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.0.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.

v1.0.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.0.1

Release notes

We are proud to announce the release of version 1.0.0 - the most important milestone since Bisq has been launched!

• Bisq’s trading network was already decentralized. With the Bisq DAO, Bisq’s leadership is now decentralized too, making Bisq exceptionally resistant to censorship.
• Get a 90% discount on trading fees when you use BSQ. Save money and support the project at the same time!
• Trade BSQ (colored bitcoin) to participate in Bisq governance. You can buy and sell BSQ just like any other asset on Bisq.

Bisq DAO

• Add genesis transaction and changes required for v1.0.0
• Improve handling of DAO state conflicts
• Add DAO launch popup 1, 2, 3, 3, 4
• Add missing check to prevent re-selection of proposal

UI

• Update list of removed assets
• Left align hyperlinks
• Remove non-core languages (ro, hu, sr)
• Prevent text overlapping in popups

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.0.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.0.0.jar
The output need to match the value from the Bisq-1.0.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.0.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.

v0.9.8

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

Release notes

This is a release focused on issues within the Bisq DAO on our DAO Testnet. Everyone who participates in testing please update to this release to continue with testing!

Bisq DAO (on our DAO Testnet)

• Protect against late blind vote publishing
• Use cryptographic hash from protobuffer serialized data instead of hashCode
• Add information of Satoshis needed for coloring
• Improve transaction display for BTC withdrawal from BSQ wallet
• Add filter for min required version for DAO
• Handle selected proposal popup state when new block is parsed
• Update insufficient BTC warning for issuance proposals
• Close printWriter before renaming temp file
• Reword text in proposal fee pop-up
• Reduce transaction broadcast timeout
• Fix max available stake for voting showing negative
• Fix incorrect required BSQ amount in warning text
• Fix incorrect transaction size shown for bonding
• Fix typo

Trading

• Change wrong name for Siacoin in removed crypto list

Development

• Add handling for bitcoinRegtestHost=none

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-0.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/Java/Bisq-0.9.8.jar
The output need to match the value from the Bisq-0.9.8.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-0.9.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.