Skip to content


Jam comes packaged with the following full-node solutions:

You should be able to install Jam with one click if you are running any of the above. You can also do a manual installation.

Install as a Package

The easiest way to install Jam is to install it as a package.


Please understand the trade-offs you are making when installing Jam as a package. Make sure to verify the integrity and authenticity of the node software you are running. And, if possible, verify the Jam installation yourself.

...with Umbrel

Jam can be installed directly from the Umbrel app store:

  • Open the interface of your Umbrel node
    (type umbrel.local in your browser)
  • Find "Jam" in the Umbrel app store
  • Click install
  • Done!

...with Citadel

Jam can be installed directly from the Citadel app store:

  • Open the interface of your Citadel node
    (type citadel.local in your browser)
  • Find "Jam" in the Citadel app store
  • Click install
  • Done!


If you are asked to enter a username and password after installation, enter "citadel" as the username and the password that Citadel provides for you.

...with Raspiblitz

You can install Jam via the command line in RaspiBlitz v1.7.2 and up. To install it, exit the Raspiblitz menu and run:

config.scripts/ on

To get information on how to connect to Jam run:

config.scripts/ menu

We hope that Jam will be available as a one-click app install with RaspiBlitz v1.8.0.

Manual Installation

There are three ways to set up Jam manually:

  1. Run the standalone docker image (easiest)
  2. Connect Jam to a local JoinMarket instance
  3. Connect Jam to a remote JoinMarket instance

All these methods have benefits and drawbacks. One method is easy, but you have less control. Others give you more flexibility, but require several manual steps. Choose the method that works best for you. The rule of thumb is: Always prefer to build and verify the applications locally yourself if you have the necessary technical skills to do so.

...with docker image

Using docker is the easiest way to run JoinMarket with Jam. However, a disadvantage is that you have to trust the developers and it is rather difficult to verify the authenticity.


  • Bitcoin Core
  • docker

The official Jam standalone docker image is already bundled with JoinMarket and Tor. It takes care of starting all subservices (API, Orderbook, etc.) and everything works out-of-the-box.

If you are connecting to a remote Bitcoin Core node, run:

docker run --rm  -it \
        --env JM_RPC_USER="BTC_RPC_USERNAME" \
        --env JM_RPC_PASSWORD="****************" \
        --env APP_USER="JAM_USERNAME" \
        --env APP_PASSWORD="****************" \
        --publish "8080:80" \

If you are connecting to a local Bitcoin Core node, use the above command but add param --add-host=host.docker.internal:host-gateway and set the environment variable JM_RPC_HOST to host.docker.internal.

After starting the container, Jam can be accessed by visiting http://localhost:8080 in your browser.

Make sure to replace the above dummy values for IP, port, RPC username, and RPC password with values appropriate to your setup. For example:

docker run --rm  -it \
        --env JM_RPC_HOST="" \
        --env JM_RPC_PORT="8332" \
        --env JM_RPC_USER="bitcoin" \
        --env JM_RPC_PASSWORD="n5a___YOUR_RPC_PASSWORD___yNA" \
        --env APP_USER="jam" \
        --env APP_PASSWORD="AvQ___YOUR_APP_PASSWORD___iCw" \
        --publish "8080:80" \

Please use your password manager or something like openssl rand -base64 32 to generate strong passwords.

...connecting to a local JoinMarket instance


If you have successfully installed JoinMarket, navigate to JoinMarket's root directory and start jmwalletd and ob-watcher:

. jmvenv/bin/activate
python3 scripts/
. jmvenv/bin/activate
python3 scripts/obwatch/ --host=

It is recommended to install both services as system services, e.g. via systemd. Also, see your joinmarket.cfg config file and adapt the values to your needs. It is generally advised to leave all settings at their default values. The above commands all use the standard values (e.g. for ports).


Bind both services to instead of to not expose them to your local network.

Once jmwalletd and ob-watcher are running, the last thing to do is to launch Jam. You can either run the docker image, or download the source code and run it via npm. If you run Jam via the docker image, you will have to make sure that the "internal" host is used:

# Option 1: run Jam via docker

docker run --rm  -it \
        --add-host=host.docker.internal:host-gateway \
        --env JAM_JMWALLETD_HOST="host.docker.internal" \
        --env JAM_JMWALLETD_API_PORT="28183" \
        --env JAM_JMWALLETD_WEBSOCKET_PORT="28283" \
        --env JAM_JMOBWATCH_PORT="62601" \
        --publish "8080:80" \
# Option 2: run Jam via npm

git clone --branch v0.1.0 --depth=1
cd jam/
npm install
npm start


Always make sure to verify the code that you run.

When successful, a browser pointing to http://localhost:3000 should automatically be opened.

...connecting to a remote JoinMarket instance

Do all the same steps as in Connecting to a local JoinMarket instance but before starting Jam (either directly or with docker), create a ssh tunnel to the remote host.

ssh yourhost.local -v -o GatewayPorts=true -N -L 28183: -L 28283: -L 62601:

Once you managed to install Jam, make sure to understand how to use it.

First Use