@ripcurlx ripcurlx released this Feb 21, 2019 · 1 commit to master since this release

Release notes

This release is featuring a 2x increase of the current trade limits for fiat and altcoins, lots of improvements for the Bisq DAO on our DAO Testnet and includes bug fixes across the app. You should update to this release especially if you had problems restoring your wallet or tor related startup issues.

Bisq DAO (on our DAO Testnet)

Trading

UI

Privacy/Security/Network

Wallet

Development

Build

Installation

Infrastructure

Assets

  • Added 19 new assets: Adeptio (ADE), Askcoin (ASK), Augmint Euro (AEUR), AustraliaCash (AUS), BitDaric (DARX), Cash2 (CASH2), Credits (CRDS), CRowdCLassic (CRCL), DAI Stablecoin (DAI), DeepOnion (ONION), Fujicoin (FJC), LitecoinZ (LTZ), Lytix (LYTX), Mile (MILE), Persona (PRSN), TrueUSD (TUSD), USD Coin (USDC), VectorspaceAI (VXV), ZelCash (ZEL)

  • Removed assets: Gridcoin (GRC) and ZeroOneCoin (ZOC)

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.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-0.9.4.jar
The output need to match the value from the Bisq-0.9.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-0.9.4.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Assets 15

@ripcurlx ripcurlx released this Feb 21, 2019 · 458 commits to master since this release

Release notes

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

Here are the release notes from v0.9.2:

With this release the fee model of Bisq was simplified and the maker fee reduced. The Bisq trading fee for the offer maker is now a fixed percentage of 0.1% and for the taker it was increased from 0.2% to 0.3%. This should reflect the higher burden on the maker side and incentivize market makers.
Besides that we squashed some bugs in the Bisq DAO and improved the UI on multiple places. This release adds 19 new assets including the 2 Mimblewimble implementations Beam and Grin (Grin will be enabled as soon as it goes live on Mainnet).

Bisq DAO (on Testnet)

Trading

UI

Privacy/Security

  • Update to netlayer 0.6.3: 1, 2

Development

Installation

Infrastructure

Assets

  • Added 19 new assets:
    Aeon (AEON), Beam (BEAM), Bitmark (BTM), Dextro (DXO), FourtyTwo (FRTY), GambleCoin (GMCN), Grin (GRIN) (will be enabled on Mainnet release), Horizen (ZEN), IdaPay (IDA), Iridium (IRD), Noir (NOR), Pinkcoin (PINK), Qbase (QBS), Remix (RMX), SiaPrimeCoin (SCP), SpaceCash (SPACE), UnitedCommunityCoin (UCC), Webchain (WEB), WrkzCoin (WRKZ)
  • Removed not traded assets.

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.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-0.9.3.jar
The output need to match the value from the Bisq-0.9.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-0.9.3.deb  
sudo tar Jxvf data.tar.xz  
sudo cp -rp opt/Bisq /opt/

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

Assets 13

@ripcurlx ripcurlx released this Jan 8, 2019 · 462 commits to master since this release

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

Release notes

With this release the fee model of Bisq was simplified and the maker fee reduced. The Bisq trading fee for the offer maker is now a fixed percentage of 0.1% and for the taker it was increased from 0.2% to 0.3%. This should reflect the higher burden on the maker side and incentivize market makers.
Besides that we squashed some bugs in the Bisq DAO and improved the UI on multiple places. This release adds 19 new assets including the 2 Mimblewimble implementations Beam and Grin (Grin will be enabled as soon as it goes live on Mainnet).

Bisq DAO (on Testnet)

Trading

UI

Privacy/Security

  • Update to netlayer 0.6.3: 1, 2

Development

Installation

Infrastructure

Assets

  • Added 19 new assets:
    Aeon (AEON), Beam (BEAM), Bitmark (BTM), Dextro (DXO), FourtyTwo (FRTY), GambleCoin (GMCN), Grin (GRIN) (will be enabled on Mainnet release), Horizen (ZEN), IdaPay (IDA), Iridium (IRD), Noir (NOR), Pinkcoin (PINK), Qbase (QBS), Remix (RMX), SiaPrimeCoin (SCP), SpaceCash (SPACE), UnitedCommunityCoin (UCC), Webchain (WEB), WrkzCoin (WRKZ)
  • Removed not traded assets.

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

Assets 2

@ripcurlx ripcurlx released this Dec 13, 2018 · 699 commits to master since this release

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

Release notes

This release is not only a bug fix release following v0.9.0 (Windows installation issues, switching between BTC networks not working,...), but contains also lots of improvements as well. Thanks to everyone who started testing of the Bisq DAO on Testnet already!

As we have updated to Java 10 and Oracle has dropped support for 32 bit Operating systems we cannot provide 32 bit binaries anymore.

Bisq DAO (on Testnet)

Trading

Payment methods

UI

Privacy/Security

Development

Installation

Assets

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

Assets 13

@ripcurlx ripcurlx released this Dec 3, 2018 · 806 commits to master since this release

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

Release notes

This release is one of our biggest in Bisq's history. Not only is the Bisq DAO code included for Testnet, but we've also redesigned the client from the ground up. Thanks to @pedromvpg for initiating and leading this Bisq redesign! Of course this release is packed as always with lots of bug fixes and UI improvements in general.

As we have updated to Java 10 and Oracle has dropped support for 32 bit Operating systems we cannot provide 32 bit binaries anymore.

Release notes:

Bisq DAO (on Testnet)

  • BSQ wallet (Send/Receive BSQ)
  • Governance (Make and vote on proposals, create compensation requests, change DAO parameters, issue BSQ)
  • Bonding (Create bonded roles/bonded reputation)
  • Pay asset listing fee with BSQ
  • Proof of burn with BSQ
  • Pay trading fees with BSQ

Trading

Payment methods

UI

Privacy/Security

Development

Assets

  • Add 25 new assets:
    Actinium (ACM), Bitcoin 2 (BTC2), Bitcoin Rhodium (XRC), Blur (BLUR), Chaucha (CHA), Croat (CROAT), Dragonglass (DRGL), EtherStone (ETHS), Kekcoin (KEK), Mask (MASK), MoX (MOX), MobitGlobal (MBGL), MonetaryUnit (MUE), Neos (NEOS), PZDC (PZDC), QMCoin (QMCoin), Radium (RADS), Ryo (RYO), SUB1X (SUB1X), Starwels (MAI), TurtleCoin (TRTL), Zero (ZER)
  • Remove not traded assets.

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.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-0.9.0.jar
The output need to match the value from the Bisq-0.9.0.jar.txt file.

Known issues with installation

Windows:

There are some known issues (not introduced in that release) with installing Bisq on Windows.
The Windows installer does not cleanup or overwrite always correctly the old installation files. If you cannot start Bisq after installation please delete the application directory [1] (not the data directory! [2]). You could also try to uninstall Bisq from the operating system but then the data directory (including your wallet and account data) will be deleted as well. If you want to use the uninstall option be sure to have made a backup first and move the backup afterwards to the data directory location.

Another issue can be 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 or app directory) 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

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.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.

Assets 13

@ripcurlx ripcurlx released this Nov 12, 2018 · 1967 commits to master since this release

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

Release notes

In this release only trade statistics and account age witness db was updated to improve startup time for a fresh install.

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.8.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-0.8.1.jar
The output need to match the value from the Bisq-0.8.1.jar.txt file.

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.8.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.

Assets 17
Aug 22, 2018
JitPack alias for v0.8.0

@ripcurlx ripcurlx released this Aug 22, 2018 · 1967 commits to master since this release

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

Release notes

This release adds two long requested payment methods (Face to Face payment and HalCash) improves everyone's privacy by rounding fiat values and finally adds support for mobile notifications for your trades, market activity and price alerts. Although currently hidden the DAO code is also part of this release.

Trading

Payment methods

Assets

No new assets are listed until the Listing fee policy proposal reaches consensus.

UI

Development

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.8.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-0.8.0.jar
The output need to match the value from the Bisq-0.8.0.jar.txt file.

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.8.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.

Assets 17
Jul 4, 2018
JitPack alias for v0.7.1

@ripcurlx ripcurlx released this Jul 4, 2018 · 2297 commits to master since this release

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

Release notes

This release adds acknowledgment status for trade, offer and dispute messages. This gives the user more information on each message status (message arrived, arrival confirmed, sent to mailbox) during its trade/dispute experience. Besides lots of bug fixes, MoneyGram was added as a new payment method and the account field for Argentinian banks support now non-standard account identifiers.

Trading

Payment methods

Assets

  • Add 28 new assets: 01coin, Aquachain, BitCloud, Bitcoin Core, Bitcoin Instant, Credits, Cryptonodes, CryptoTari, DACash, Diamon, DRIP, FuturoCoin, Graft, LikeCoin, Lobstex, MaxCoin, MegaCoin, MicroCoin, Motion, Myriadcoin, Nano, NewPowerCoin, Nimiq, Pix, PixelPropertyToken, PRiVCY, Triton, Wavi

UI

Development

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

How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-0.7.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-0.7.1.jar
The output need to match the value from the Bisq-0.7.1.jar.txt file.

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

Assets 17