Running Bisq on Raspberry Pi

Running_Bisq_on_Raspberry_Pi.md

Running Bisq on Raspberry Pi

Working as of 2023-01-13

My setup:

Raspberry Pi 4 Model B Rev 1.5 2GB Raspberry Pi OS 64-bit with Desktop Release Date: September 22nd 2022

Bisq 1.9.9 built from source

Install Java

• Download Liberica Standard JDK 11 ARM 64 for Linux .DEB file
  • https://bell-sw.com/pages/downloads/#/java-11-lts
  • https://download.bell-sw.com/java/11.0.17+7/bellsoft-jdk11.0.17+7-linux-aarch64.deb
• sudo dpkg -i bellsoft-jdk11.0.17+7-linux-aarch64.deb

Build Bisq from source

• git clone https://github.com/tmakerman/bisq.git
• cd bisq
• git checkout bisq-on-rpi-v1.9.9
  • this branch applies the same changes as cbeams bisq-on-m1, but for linux aarch64 instead of mac https://github.com/cbeams/bisq/commit/8546f59b12a58775e6bf7fa1852204cfcfdb9f8e
• ./gradlew build
  • some artifact dependency verifications fail, this can be ignored
  • build took ~ 26 min on my RPi 4 4GB
  • Bisq is ready to run, however when it initializes it will try to connect to Bitcoin network over Tor using its bundled Tor which fails and it will eventually time out. Instead setup a Tor hidden service and configure Bisq to connect through that…

Setup Tor

• My steps below are taken from this guide:
  • https://stopanddecrypt.medium.com/running-bitcoin-lightning-nodes-over-the-tor-network-2021-edition-489180297d5#dbe0
• lsb_release -c
• Add following lines to /etc/apt/sources.list.d/tor_repo.list – if codename from lsb_release was anything but bullseye change that in lines below
  • NOTE this step is modified from the guide I referenced above to add [arch=arm64] and properly resolve tor on RPi

deb [arch=arm64] http://deb.torproject.org/torproject.org bullseye main
deb-src [arch=arm64] http://deb.torproject.org/torproject.org bullseye main

• curl https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc | sudo apt-key add -
• sudo apt-get update
• sudo apt-get install tor deb.torproject.org-keyring
• Edit /etc/tor/torrc adding the following lines to bottom of file:

SOCKSPort 9050
Log notice stdout
ControlPort 9051
CookieAuthentication 1
CookieAuthFileGroupReadable 1
HiddenServiceDir /var/lib/tor/bisq/
HiddenServicePort 8080 127.0.0.1:8080

• Determine Tor group:
• grep User /usr/share/tor/tor-service-defaults-torrc
• sudo usermod -a -G debian-tor satoshi
  • replace satoshi with your username
• sudo shutdown -r now
• Wait for system to come back up
• sudo systemctl enable tor
• sudo systemctl start tor

Running Bisq

• from RPi Desktop environment terminal window
• cd bisq
• ./bisq-desktop --torControlPort 9051 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth
  • Note on command line arguments:
  • bisq-network/bisq#2278 (comment)
  • Will get some Unsupported JavaFX configuration warning, ignore it

Thank you for the note @napoly

Hi Tom,

On Wed, Mar 13, 2024 at 10:56:27AM -0700, Tom Makerman wrote: @tmakerman commented on this gist:

Thanks to you both for your replies. FWIW my interest in implementing Bisq on a Raspberry Pi was to have the possibility, among other things, of having battery backup should the mains electricity fail. I now decided to defer that indefinitely. In case someone else wants to pursue this coding, I had found jfoenix = { strictly = '9.0.10' } in libs.versions.toml but prior to bisq-1.9.14 /lib/jfoenix-17.0.1.jar was implemented instead via some mystery in other files. And jfoenix-17.0.1 does not seem to be well supported in the java community. That is as far as I had gone. I came to the view that java is insecure by design. And that having a nice progress bar in a web page is probably not worth the addtional risk or maintenance burden. But I'm inexperienced in these matters, and an advocate of free choices. Again, thanks for your replies.