Install IronDivi

1What IronDivi is

IronDivi is a Divi node written in Rust. It joins the same network as the original Divi node, follows the same chain, and takes the same commands, so anything written for divi-cli works with irondivi-cli. It comes as two programs:

• irondivid, the node. It downloads the chain, keeps your wallet, and stakes.
• irondivi-cli, the command line you use to talk to it.

This tutorial installs it on testnet, the practice network where coins are worth nothing, so a mistake costs nothing. Everything here works the same on the real network without --testnet.

If you want a wallet with windows and buttons rather than a node you type at, Divi Desktop or BoxWallet are the easier start.

2Pick your download

Every release is on the IronDivi releases page as a .tar.gz file holding both programs. Pick the one for your computer:

There are also builds for 32-bit ARM, 32-bit Intel, POWER, RISC-V and IBM Z. The musl files are the safe choice on Linux: they carry everything they need, so they run on any distribution, old or new.

3Install on Linux

Open a terminal. These four lines make a folder, download the release, check it, and unpack it:

mkdir -p ~/irondivi && cd ~/irondivi
curl -LO https://github.com/DiviDomains/IronDivi/releases/download/v0.2.5/irondivi-x86_64-linux-musl.tar.gz
sha256sum irondivi-x86_64-linux-musl.tar.gz
tar xzf irondivi-x86_64-linux-musl.tar.gz

You now have a folder irondivi-x86_64-linux-musl with four files in it: irondivid, irondivi-cli, a LICENSE and a README.md. Ask each program its version to prove it runs:

./irondivi-x86_64-linux-musl/irondivid --version
./irondivi-x86_64-linux-musl/irondivi-cli --version

# what we got on Ubuntu 22.04
irondivid 0.2.5
irondivi-cli 0.2.5

That is the whole install. There is nothing to run as root and no package to register. If you would rather type irondivid from anywhere, copy the two programs into a folder on your PATH, for example ~/.local/bin.

On a Raspberry Pi or another ARM machine, swap x86_64 for aarch64 in every line.

4Install on a Mac

Open Terminal (it is in Applications → Utilities). On an Apple silicon Mac:

mkdir -p ~/irondivi && cd ~/irondivi
curl -LO https://github.com/DiviDomains/IronDivi/releases/download/v0.2.5/irondivi-aarch64-macos.tar.gz
shasum -a 256 irondivi-aarch64-macos.tar.gz
tar xzf irondivi-aarch64-macos.tar.gz
./irondivi-aarch64-macos/irondivid --version
./irondivi-aarch64-macos/irondivi-cli --version

# what we got on macOS 27.0.1, Apple silicon
irondivid 0.2.5
irondivi-cli 0.2.5

On an Intel Mac use x86_64 instead of aarch64 in each line. Because you downloaded with curl in Terminal rather than a browser, macOS does not put its quarantine mark on the files and does not block them from running.

5Windows

Release v0.2.5 has no Windows download, and we have not built IronDivi on Windows ourselves. You have three honest choices:

• Use Linux inside Windows. Install Ubuntu from the Microsoft Store (Windows Subsystem for Linux), then follow the Linux steps inside it. We have not tested this path, but it runs the same Linux file.
• Run the original Divi node instead. It has a Windows download: see Install the Divi node.
• Use a wallet app. Divi Desktop and BoxWallet both run on Windows.

6Build it from source

You do not need this to run a node; the downloads above are the same programs. Build from source if you want the newest unreleased code, or a platform with no download. You need Rust 1.75 or newer, a C compiler, and on Linux the libclang-dev package (Ubuntu: sudo apt install build-essential libclang-dev).

git clone https://github.com/DiviDomains/IronDivi.git
cd IronDivi
cargo build --release

The two programs land in target/release/. The build pulls in a few hundred Rust libraries and compiles all of them, so it takes a while:

7Start it on testnet

IronDivi keeps its testnet files, including its wallet, in one folder, apart from anything on the real network:

• Linux: ~/.irondivi/testnet
• Mac: ~/Library/Application Support/IronDivi/testnet

Before the first start, create that folder and put a settings file called irondivi.conf in it. The file protects the node's command port with a name and password that only irondivi-cli on your own machine needs to know, and it names one node to connect to first:

mkdir -p ~/.irondivi/testnet
nano ~/.irondivi/testnet/irondivi.conf

# irondivi.conf: the quotes matter
rpcuser = "pick-a-name"
rpcpassword = "pick-a-long-random-password"
addnode = "services.divi.domains:51474"

The settings file is in TOML form, so text values need double quotes and each setting appears once. (The original Divi node's divi.conf has no quotes, and that is the most common slip when you have used both.) Save it, then start the node:

cd ~/irondivi
./irondivi-x86_64-linux-musl/irondivid --testnet --daemon

# what it prints
Logging to "/home/you/.irondivi/testnet/debug.log"

--daemon sends it to the background and gives you your terminal back. Leave --daemon off if you prefer to keep it in its own window and stop it with Ctrl+C. On a Mac the program is in irondivi-aarch64-macos instead.

The first start creates a new wallet in the testnet folder. The log says so:

INFO irondivid:   IronDivi v0.2.5
INFO irondivid: Chain: Divi (testnet)
INFO irondivid: Data dir: "/home/you/.irondivi/testnet"
INFO irondivid: RPC: 127.0.0.1:51473
INFO irondivid: P2P: 0.0.0.0:51474
INFO irondivid: Creating new wallet at "/home/you/.irondivi/testnet/wallet"
WARN irondivid: new wallet created; retrieve the seed with the dumphdinfo RPC

The node talks to other testnet nodes on port 51474 and listens for irondivi-cli on port 51473, on your own machine only. If another Divi node already uses those ports, give this one its own by adding port = 53600 and rpcport = 53601 to the settings file. You can also keep everything in a folder of your choosing with --datadir /some/folder on both programs; then the settings file goes in that folder.

8Check it, then stop it

Ask the node how far it has got and how many other nodes it is talking to:

./irondivi-x86_64-linux-musl/irondivi-cli --testnet getblockcount
./irondivi-x86_64-linux-musl/irondivi-cli --testnet getconnectioncount

# six minutes after the first start, on 2026-10-21
35097
8

The block count climbs until it matches the latest block on the testnet explorer; then you are synced. Our test node downloaded about 35,000 blocks in its first six minutes and the whole testnet chain in about an hour. -getinfo gives a one-screen summary:

./irondivi-x86_64-linux-musl/irondivi-cli --testnet -getinfo

Chain: test
Blocks: 7223
Headers: 7223
Verification: 100.0000%
Difficulty: 2583.9590888854127

Network: /IronDivi:0.2.5/
Connections: 8 (in: 0, out: 8)

Wallet: wallet.dat
Balance: 0.0

To stop the node, send it the stop signal. IronDivi 0.2.5 also accepts irondivi-cli stop, but that only prints Divi server stopping; in our tests the node kept running for minutes afterwards. The signal works. Find the program's process number and pass it to kill:

pgrep -a irondivid
kill 890008        # use the number pgrep printed
pgrep irondivid    # prints nothing once it has gone

Our synced testnet node closed its files and exited 2 seconds after kill. On a Mac, use pgrep -l irondivid in the first line. If you started it without --daemon, pressing Ctrl+C in its window does the same. Always check it has gone before you copy its folder, upgrade it or switch the machine off.

Next time you start it, it carries on from where it left off. Now that it runs, learn what you can ask it in A tour of irondivi-cli, see every setting in Config files explained, or make it start by itself with Run a node as a service. To put some testnet coins in the new wallet, see Get testnet DIVI.

If something goes wrong

Still stuck? Ask the Divi chatbot, or see all tutorials.