Skip to content

Update Dingo Node

Download the latest release from the Dingo releases page.

⚠️ Adjust the version and architecture to match your system.

cd ~/dingo
wget https://github.com/blinklabs-io/dingo/releases/download/v0.68.0/dingo-v0.68.0-linux-amd64.tar.gz -O - | tar -xz

sudo systemctl stop dingo

Step 3 - Copy Dingo Binary to /usr/local/bin/

Section titled “Step 3 - Copy Dingo Binary to /usr/local/bin/”
sudo cp ~/dingo/dingo /usr/local/bin/

Verify it has been copied by which dingo


Step 4 - Check for Configuration File Updates

Section titled “Step 4 - Check for Configuration File Updates”

Check to make sure no config updates are required.

Refer to the Dingo Release Notes and the Quick Start guide.

💡 To view and edit dingo.yaml file run:

sudo nano /etc/dingo/dingo.yaml

⚠️ Adjust path as needed


Section titled “Step 5 - RECOMMENDED - Remove the .dingo Database and Resync Mithril Snapshot”

Since Dingo is under active development it is recommended during upgrading to delete database and start fresh.

💡 To view hidden files and double-check path run:

cd ~/dingo
ls -a

You should see .dingo. If not, check your dingo.yaml file for the database path you configured.

Delete the .dingo database directory by running:

cd ~/dingo
rm -r .dingo

Dingo has a built-in Mithril client that downloads and loads a snapshot automatically. This saves hours of sync time compared to replaying the chain from genesis.

Run the following command from your ~/dingo directory:

dingo sync --mithril

Dingo will:

  1. Download the latest Mithril snapshot for your configured network
  2. Verify the certificate chain
  3. Load the snapshot into the database

This takes approximately 20-30 minutes depending on your system and network speed.

📝 If you skip this step, Dingo will sync from genesis when started, which takes significantly longer.

Once the Mithril snapshot has finished loading, start the node:

cd ~/dingo
sudo systemctl start dingo

Verify that the new version is installed:

dingo version

Verify the service is running:

sudo systemctl status dingo.service

To follow the logs in real time:

sudo journalctl -u dingo -f

To see recent logs if there is an error:

sudo journalctl -u dingo -n 50 --no-pager