Skip to main content

Upgrade Hathor core (full node)

Goal​

By the end of this guide, your Hathor full node will be running the latest release, with your existing database intact.

We advise operators to upgrade their full nodes whenever Hathor team releases a version with critical modification — i.e., those who address security issues or greatly alter the system's machinery. To follow such releases, see Hathor core release notes.

Requirement​

Having a running version of Hathor core different from the latest one. To see the latest release, see Hathor core release notes.

Step-by-step​

  1. Get the latest release.
  2. Install the latest release.

Step 1: get the latest release​

  1. Start a shell session.
  2. Change the working directory to where you installed your full node — namely, hathor-core and database, docker-compose.yml and database, or just the database.
  1. If you installed your full node from source code, change the working directory (the one you chose to store the application) to its child hathor-core:
cd hathor-core
  1. Update the branch release with the latest changes:
git fetch origin release && git switch release || git switch -c release --track origin/release && git pull origin release

Step 2: install the latest release​

warning

Do not remove the full node's database. Otherwise, it will need to sync with the network from scratch. In other words, keep the directory containing the blockchain database intact — typically data.

If you are connecting your full node to the mainnet, do not remove file peer.json. This file stores your node's unique peer identity for the mainnet whitelist — replacing it means your node will need to be re-whitelisted by Hathor team.

If you installed your full node from source code, follow Install full node from source code from step 2, substep 5 onward to update the project dependencies and to restart your full node normally.

Task completed​

Your full node is now running the latest release. It will resume syncing from where it left off — your existing database was preserved throughout the upgrade.

Hathor team notifies node operators whenever a critical version is released. To track releases, see Hathor core release notes.

What's next?​