Package Details: bisq 1.3.5-1

Git Clone URL: (read-only, click to copy)
Package Base: bisq
Description: Cross-platform desktop application that allows users to trade national currency (dollars, euros, etc) for bitcoin without relying on centralized exchanges
Upstream URL:
Licenses: AGPL3
Conflicts: bisq-bin, bisq-git
Provides: bisq
Submitter: dmp1ce
Maintainer: dmp1ce (freimair, TheGoliath)
Last Packager: freimair
Votes: 34
Popularity: 2.76
First Submitted: 2017-07-05 14:43
Last Updated: 2020-06-22 09:59

Latest Comments

1 2 3 4 5 6 Next › Last »

sylphio commented on 2020-06-22 08:38

@dsche-cyber I am not one of the maintainers, so all I can say is that the reference should be the GitHub release channel, in my opinion. Means of verification are provided there for every release. Since this AUR package had to switch to git clone because of this issue, I don't know what the checksum is supposed to check. I think you were right to raise ŧhis issue with the Bisq developer: if one cannot build from the release's archive alone, a different verification is necessary.

dsche-cyber commented on 2020-06-21 21:58

@sylphio alright, one more thing: where did you get the sha256sum in PKGBUILD from?

sylphio commented on 2020-06-21 21:46

@dsche-cyber I can't help you with that; that question would be better asked to the Bisq community than in the AUR. Still, what you report is what I would expect: Bisq is a separate network (built atop Tor).

dsche-cyber commented on 2020-06-21 21:27

@sylphio thanks for the quick response and the hint. Was searching for it a long time and 10 min after the post I found it, this happens all the time...

Got my full node connected the following way:
1. Custom Node under settings with: (No [] and since port 8333 is set per default no port)
2. restart (you get prompted to do so)
3. Uncheck on tor.
4. restart (you get prompted to do so)

But I got a question: The connected peers shown in bisq are not the same as the ones from bitcoin-cli getpeerinfo. Why is that and is it normal?

sylphio commented on 2020-06-21 20:48

@dsche-cyber The files you are looking for are likely in $HOME/.local/share/Bisq (particularly btc_mainnet). You may want to back it up, since it contains important data that you may not be able to recover otherwise (wallet, keys, etc.).

dsche-cyber commented on 2020-06-21 20:25

How can I fully deinstall this? sudo pacman -R bisq is not enough. I want to reinstall it, and start it as i never touched it. But after pacman -R bisq, new git clone and build I am stuck with the same problems, bisq not getting the connected to the network (after 3/4) "connection problems". I know that there is still data not deleted as it starts in dark mode even though it is not the default (after new install).

sylphio commented on 2020-06-21 14:39

@kwacorn Thanks for the feedback. I hope one of the maintainers will find the time to fix the PKGBUILD.

@jamesjon My post describes modifications of the file PKGBUILD: the lines begun by a + are to be added; the rest is just context to locate the place in the file. I guess you use an AUR helper (probably yay, the default in Manjaro). There should be an option to edit the PKGBUILD, but I am not familiar with yay. Here is the manual process:

  1. Download the PKGBUILD file. You can get it directly on this page (direct link). Alternatively, I think yay -G bisq does exactly that. Do not change the file's name; it has to be named PKGBUILD.

  2. Edit the PKGBUILD file as I describe: find the line git clone [...] and add below the three lines marked by a + (do not write the +).

  3. In the same directory as the PKGBUILD (you may want an empty directory for this), run the command makepkg --syncdeps --install. This will follow the instructions in the PKGBUILD file: install any missing dependency (--syncdeps); download the source files; build the package; install it (--install). The purpose of the lines I propose to add is to download the missing files that caused the error you got; it is simply what the error message suggested to do.

  4. If you get another error, report the error message so that someone can help you.

This 'manual' process, and everything you need to know about it, is described in the ArchWiki page on makepkg (particularly the usage section). The AUR helpers do the same thing, they just automate it for convenience. When you need to fix something, understanding the installation process helps.

jamesjon commented on 2020-06-21 13:43

@sylphio Where am I supposed to put that? How do I install it "manually"? Thank you

kwacorn commented on 2020-06-20 20:03

@sylphio I am happy to report that your suggested changes to PKGBUILD have worked and I have a successful build and install of bisq 1.3.5-1, thank you.

sylphio commented on 2020-06-20 16:46

@jamesjon Did you try my suggested fix (see my message just below yours)? If you did and still get this error, please share the full error message until BUILD FAILED (as kwacorn did below) so that people can try to help you.