Stake on a Raspberry Pi

1Which wallets run on a Pi

A Pi has an ARM processor, so it needs programs built for ARM. Only the two command-line nodes have ARM builds that can stake:

So a Pi stakes from the command line. If that is new to you, read Stake from the command line first; the commands there are the same on a Pi.

2Which Pi system you have

Raspberry Pi OS comes in three kinds, and the right download depends on which one is on your Pi. On 2026-10-22 the official Raspberry Pi Imager listed:

Ask the Pi which kind of programs it runs, and which Debian it is built on:

dpkg --print-architecture
arm64        # or armhf
cat /etc/debian_version
13.7         # 13 = Trixie, 12 = Bookworm

Use dpkg, not uname -m. uname describes the system's core, which can be 64-bit under a 32-bit system; dpkg describes the programs you will run.

3Which Pi, and what storage

The 64-bit Raspberry Pi OS runs on the Pi 3, 4, 400 and 5, according to the Imager. We could not measure a node on Pi hardware, so these figures are from our Intel testnet nodes in Stake on a VPS:

On that evidence a Pi with 1 GB of memory is too small for IronDivi. Our suggestion, not a measured need, is a Pi 4 or 5 with at least 4 GB and 32 GB or more of storage. A USB SSD for the chain is worth having if you own one; we did not test SD cards.

4IronDivi on a Pi

Pick the IronDivi build from what dpkg said:

On a 64-bit Pi:

cd /tmp
curl -LO https://github.com/DiviDomains/IronDivi/releases/download/v0.2.6/irondivi-aarch64-linux-musl.tar.gz
sha256sum irondivi-aarch64-linux-musl.tar.gz
6863c56afad91edfb340fe49e976643ffb67b2dc7709898c91adb2da68537bd1
tar xzf irondivi-aarch64-linux-musl.tar.gz
sudo install -m 755 irondivi-aarch64-linux-musl/irondivid irondivi-aarch64-linux-musl/irondivi-cli /usr/local/bin/
irondivid --version
irondivid 0.2.6

On a 32-bit Pi, the same with the 32-bit file:

cd /tmp
curl -LO https://github.com/DiviDomains/IronDivi/releases/download/v0.2.6/irondivi-armv7-linux-musl.tar.gz
sha256sum irondivi-armv7-linux-musl.tar.gz
786b464a48dfe5a4a7743bf490453d058e510a0298978fc4da0f9357401cf9e1
tar xzf irondivi-armv7-linux-musl.tar.gz
sudo install -m 755 irondivi-armv7-linux-musl/irondivid irondivi-armv7-linux-musl/irondivi-cli /usr/local/bin/
irondivid --version
irondivid 0.2.6

Both checksums are the ones in the release's own SHA256SUMS file, and GitHub lists the same values next to each download.

On 0.2.6, each build started on testnet, found peers (6 and 8) and began downloading blocks, then encrypted a new wallet and unlocked it for staking only. We did not stake with 0.2.6 on ARM. With 0.2.5, the 64-bit build, started from a copy of our synced testnet chain, reached the newest block, and once its new wallet held 3,000 tDIVI it reported:

irondivi-cli --testnet getstakingstatus
  "enoughcoins": true,
  "mintablecoins": true,
  "staking status": "Staking Active",

0.2.6 words this differently: "staking status": true, with the text in "staking status text".

5The Divi node on a Pi

Divi publishes one ARM build of the Divi node, for 32-bit systems. Divi publishes no checksum for it; this is the one we got:

cd /tmp
curl -LO https://github.com/DiviProject/Divi/releases/download/v3.0.0/divi-3.0.0-RPi2-9e2f76c.tar.gz
sha256sum divi-3.0.0-RPi2-9e2f76c.tar.gz
e584348f20d8dbb4942ec13e98769ce6d97511060584686322a3d6af4865156f
tar xzf divi-3.0.0-RPi2-9e2f76c.tar.gz
sudo install -m 755 divi-3.0.0/bin/divid divi-3.0.0/bin/divi-cli /usr/local/bin/
divid -version
Divi Core Daemon version v3.0.0

It ran on both 32-bit Trixie and 32-bit Bookworm. On a 64-bit Pi it needs the 32-bit system libraries. Without them it cannot start; with the 32-bit libraries copied into a 64-bit Trixie system it ran. On a real Pi the usual way to add them is:

# only if divid will not start on a 64-bit Pi (we could not test this on a Pi)
sudo dpkg --add-architecture armhf
sudo apt update
sudo apt install libc6:armhf libstdc++6:armhf

On a 64-bit Pi, IronDivi's 64-bit build is the simpler choice.

Under emulation, this 32-bit build synced testnet, unlocked an encrypted wallet for staking, and once its 3,000 tDIVI had matured it reported:

divi-cli getstakingstatus
  "walletunlocked": true,
  "mintablecoins": true,
  "enoughcoins": true,
  "stakingstatus": true

6Run it as a service

From here a Pi is a small Linux server, and the steps are the same as on a rented one. Follow Stake on a VPS from step 4 onwards, with two changes:

• Skip its download steps. You installed the ARM programs above to the same place, /usr/local/bin, so its service files work unchanged.
• The firewall matters less at home. Your router already blocks connections from outside. Never forward the RPC port on the router. Forwarding the network port (51472) is optional; staking only needs the Pi to reach out.

The rest applies as written: the divi user, the service files that restart the node, unlocking after every restart, and what a crash looks like.

7Vault or wallet

A Pi at home is safer than a rented server, but it is still a computer that holds keys and stays on. The vault route keeps your coins out of its reach: the Pi holds only the manager key, which can stake but not send. See What a vault is and Add a vault as manager.

8What we could not test

• No Raspberry Pi. Every ARM program ran on an Intel Linux server under QEMU, an emulator that runs ARM programs, inside copies of Debian's ARM systems. The programs are the real release files. Speed, memory use and heat on a Pi are unknown.
• No sync from scratch. Under emulation a full sync was far too slow, so both nodes started from a copy of our synced testnet chain. The 0.2.6 ARM runs were short: start, peers, the first few thousand blocks and wallet encryption; no staking.
• No SD card, no reboot, no mainnet. We did not test storage, starting on boot, or the main network on ARM.
• The 32-bit library install for the Divi node on a 64-bit Pi is the standard Debian way, but we showed only that the node runs once those libraries are present.

Next

• Stake on a VPS: the service files, unlocking, and crash recovery.
• Stake alerts: a Telegram message for every stake.
• Why isn't my wallet staking? when nothing arrives.
• Glossary for the words on this page.