Sovereignty, Privacy & Economic Freedom.


Dojo x86 Bitcoin Node Guide: Part 6 – Installing Updates

bitcoin node updating packages
  1. Dojo x86 Bitcoin Node Guide: Part 1. Installing Bitcoin Core & Tor.
  2. Dojo x86 Bitcoin Node Guide: Part 2 – Installing Fulcrum Indexer.
  3. Dojo x86 Bitcoin Node Guide: Part 3. Installing Mempool Explorer.
  4. Dojo x86 Bitcoin Node Guide: Part 4 – Installing Dojo.
  5. Dojo x86 Bitcoin Node Guide: Part 5 – Installing Whirlpool & UFW.
  6. Dojo x86 Bitcoin Node Guide: Part 6 – Installing Updates

One of the benefits of building your own node is the freedom to choose what packages you want on your system and how often you update them. Some like to stay on the cutting edge of software releases, whereas others prefer to wait for the wider community to update in case issues are reported. Unless a vital update arises, I typically leave everything as is, updating only once every six months.

The best way to keep up with software releases is by creating Github and Gitlab accounts and following projects of interest. You can then register for update alerts, ensuring you stay updated with the latest package releases. It’s also worth having an account to create bug reports or feature requests.

Before performing any package updates, updating your operating system is always advisable.

sudo apt update && sudo apt upgrade -y

Updating Bitcoin Core.

As well as GitHub notifications, another great way to keep up with the latest Core releases is by adding’s releases RSS feed to your favourite reader.

You can check the version of Core that is currently installed using the following command.

bitcoin-cli --version
  1. If a newer version is available, you must first stop Bitcoin CLI.
bitcoin-cli stop

2. Download and verify the latest Core release as we did in the Core installation guide. Don’t forget to modify these commands for whichever Core version you’re installing.

cd ~/downloads
sha256sum --ignore-missing --check SHA256SUMS
gpg --verify SHA256SUMS.asc

3. Once the download is verified, unpack the archive and delete the sha256 files and the downloaded archive.

tar xzf bitcoin-*-x86_64-linux-gnu.tar.gz
rm -r bitcoin-*-x86_64-linux-gnu.tar.gz
rm SHA256SUMS && rm SHA256SUMS.asc

4. Next, initialise Bitcoin.

sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-*/bin/*
sudo systemctl start bitcoind

5. Remove the leftover folder from your downloads directory.

rm -r bitcoin-*/

6. Check that the output of the following command reports the new Core version.

bitcoin-cli --version

7. Check the logs to ensure that Core is running correctly and downloading blocks.

tail -f .bitcoin/debug.log

Updating Dojo.

You can keep up to date with the latest Dojo releases by following the GitLab repo.

1. Go to your “my-dojo” directory and stop Dojo.

cd ~/dojo-app/docker/my-dojo
./ stop

2. Go to the downloads directory.

cd ~/downloads

3. Download the latest Dojo release and unpackage.

unzip -d .

4. Copy the contents over to your “dojo-app” directory.

cp -a samourai-dojo-master/. dojo-app/

5. Remove the archive and remaining folder.

rm -rf samourai-dojo-master

6. Return to the “my-dojo” directory.

cd ~/dojo-app/docker/my-dojo

7. Finally, run the upgrade script.

./ upgrade

Once the upgrade logs finish, and you start seeing lots of “node.js” logs, the upgrade is complete, and you can safely exit the logs with “control + c”.

Updating Whirlpool CLI.

You can follow new Whirlpool releases using the official Whirlpool GitLab repo.

  1. From the home directory, stop Whirlpool and remove the Whirlpool folder.
sudo systemctl stop whirlpool
rm -rf whirlpool

2. Create a new Whirlpool directory and fetch the .jar file for the latest CLI version.

mkdir ~/whirlpool
cd ~/whirlpool

3. Go to the Whirlpool CLI repository and download the latest jar file. The command for version 0.10.16 would be as follows.


4. Next, you need to edit your system file. In the “WorkingDirectory” section, edit the version number to match your newly downloaded .jar file version.

sudo nano /etc/systemd/system/whirlpool.service

5. And then start the Whirlpool service.

sudo systemctl daemon-reload
sudo systemctl start whirlpool

6. Check that the Whirlpool service is active.

sudo systemctl status whirlpool

Updating Mempool.

Thanks to Docker, updating Mempool is incredibly simple. When a new version is tagged on the GitHub repository, you can update it by running the following three commands.

cd ~/mempool/docker
docker compose down --rmi all
docker compose up -d

Updating Fulcrum Indexer.

You can register for Fulcrum updates using the official GitHub repo.

  1. First, stop Fulcrum and remove ONLY the following files from the Fulcrum directory. Be careful NOT to accidentally remove “fulcrum.conf” as this contains your custom settings.
sudo systemctl stop fulcrum
cd ~/fulcrum/
rm -r Fulcrum
rm -r FulcrumAdmin
rm fulcrum-example-config.conf
rm fulcrum-quick-config.conf
rm -r man
rm LICENSE.txt

2. Next, download the latest version of Fulcrum from the GitHub repository.

cd ~/downloads

For example, downloading version 1.9.1, the command would be as follows.


3. Now unzip the archive and then delete it. Be careful not to accidentally delete the unpackaged file if using the Tab button’s auto-complete function.

tar xvf Fulcrum-1.9.1-x86_64-linux.tar.gz
rm -r Fulcrum-1.9.1-x86_64-linux.tar.gz

4. Next, move the contents of the unpackaged archive to your Fulcrum directory and remove the empty folder. Change the username in the command if you didn’t use “satoshi“.

mv Fulcrum-1.9.1-x86_64-linux/* /home/satoshi/fulcrum
rm -r Fulcrum-1.9.1-x86_64-linux

5. Now start Fulcrum and restart the Tor service.

sudo systemctl start fulcrum.service
sudo systemctl restart tor

6. To ensure everything runs as expected, check the Fulcrum logs with the following command. You should see regular indexing logs.

journalctl -fu fulcrum.service

Updating Docker Compose.

As with all other updates, you can keep up to date with new Compose releases directly from the GitHub repository. Docker itself will update along with your regular system updates.

You can check which version of the standalone plugin you’re using with the following command.

docker-compose --version
  1. If a newer version is available, first remove the old version.
sudo rm /usr/local/bin/docker-compose

2. You can now install the new version. Don’t forget to modify the URL for the version you’re updating to. For 2.17.2, the command would be as follows.

sudo curl -SL -o /usr/local/bin/docker-compose

3. Modify the directories permissions.

sudo chmod +x /usr/local/bin/docker-compose

4. Finally, check that the output of the following command reports the new version.

docker-compose --version