The easy way: a Divi node with BoxWallet

1What BoxWallet is

BoxWallet is an independent, open-source program that installs and runs the official node of a dozen coins, Divi among them, and puts a wallet screen in front of each. It is not made by the Divi project. For Divi it downloads the C++ node, v3.0.0, from the Divi project's GitHub releases, so the node under it is the same program Divi Desktop runs, with the same wallet file and the same commands.

It comes in two forms built from the same code:

• The desktop app, a window with a coin list on the left, for Linux, Windows and Apple-silicon Macs.
• The terminal app, one file that draws the same screens inside a terminal. It needs nothing else installed, which makes it the right choice for a server, a Raspberry Pi, an Intel Mac, or anything you reach over SSH.

This tutorial uses the terminal app on Ubuntu, because every screen in it can be shown as text. The desktop app has the same panels and buttons under the same names. The current version is v0.8.38, released 2026-10-20.

2Download it and check the file

Everything is on the releases page. There is no installer. Pick one file:

Ignore the files named update-…; BoxWallet's own updater fetches those. Every release also carries SHA256SUMS, so check what you downloaded. On Linux:

# a fresh folder, the program, and the checksum list
mkdir -p ~/boxwallet && cd ~/boxwallet
curl -sSLO https://github.com/richardltc/boxwallet/releases/download/v0.8.38/boxwallet-linux-x86_64
curl -sSLO https://github.com/richardltc/boxwallet/releases/download/v0.8.38/SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS
boxwallet-linux-x86_64: OK
chmod +x boxwallet-linux-x86_64

On a Mac, shasum -a 256 boxwallet-macos-aarch64 prints the hash to compare by eye; on Windows, certutil -hashfile boxwallet-windows-x86_64.exe SHA256. The file is about 3 MB.

3Open it and install Divi

./boxwallet-linux-x86_64

The screen fills with a coin list on the left and a help pane on the right. Press ↓ until Divi is marked, then i to install. It downloads the node from GitHub, unpacks it, and the status changes to ✓ install complete within seconds on a fast line:

  BoxWallet v0.8.38   │ Divi v3.0.0     Total: 0.00000000 DIVI   $0.00
❯ Divi ❮              │ Home  |  Transactions  |  Receive  |  Send  |  Settings
                      │ Status: Idle
                      │ Installed: ✔    Running: ✘    Peers: -    Syncing: ✘    Staking: ✘
                      │ Wallet: Unknown
                      │
                      │ status: ✓ install complete
                      │
                      │ [ Start ]   (press s)
── Log  (l: hide) ──────────────────────────────────────────────
01:02:30  Divi: Extracting…
01:02:30  Divi: install complete

The keys you will use, all shown on the Home pane of the program itself:

4Start the node

Press s. The first time, before anything starts, BoxWallet asks one question:

┌─ Divi — Blockchain snapshot ───────────────┐
│ Download ~4.7 GB of chain data to sync in  │
│ minutes instead of days. Resumes if        │
│ interrupted.                               │
│                                            │
│ It's faster because it skips the           │
│ verification your node would otherwise do  │
│ itself — you're trusting whoever           │
│ published it. Syncing from the network is  │
│ slower, but your node proves every block   │
│ for itself.                                │
│                                            │
│   Yes — use it                             │
│ ❯ No — sync normally                       │
└────────────────────────────────────────────┘

The snapshot comes from the Divi project's own site, snapshots.diviproject.org, and is rebuilt every day, but that site publishes no checksum for it, so there is no way to prove the 4.9 GB you receive is the 4.9 GB they made. Choose No — sync normally: your node then checks every block itself. The offer appears only once, because once the node has run there is a chain in the folder and BoxWallet will not unpack a snapshot over it. Bootstrap from a snapshot goes into the trade-off.

The node starts and spends several minutes on Loading wallet… (13.24 %) with no peers; this is normal for the C++ node and took four and a half minutes on our machine. Then the pane comes alive:

Status: Syncing blocks…
Installed: ✔    Running: ✔ v3.0.0.0    Peers: 6    Syncing: ⠒    Staking:
Wallet: Unencrypted   (press w)

Headers  ██████████████████████████████ 100%
Blocks   ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 1.9%  2018-11-22 23:53  7 years and …
Storage  0.15 GB

01:08:23  Divi: Waiting for peers…
01:08:25  Divi: Syncing blocks…

The Blocks bar shows how far along the chain you are and the date of the block you have reached. Divi's mainnet was at block 4,269,318 on the day; our node did the first 130,000 blocks in four minutes, and early blocks are the quick ones. Leave it running. A full first sync of Divi mainnet takes hours on a good connection and a day or more on a slow disk; Run a node as a service shows how to keep it going through reboots.

Watch the Memory and Disk bars on the same pane. They are the whole machine's, not the node's, so you see at a glance whether the chain is going to fit.

5Encrypt the wallet and save the recovery words

The node created a wallet the moment it started, and Home says so: Wallet: Unencrypted (press w). Do this before any coin arrives. Press w:

┌─ Divi Wallet ──────────────────────────────┐
│ ❯ Encrypt wallet                           │
│   Back up wallet                           │
│   Show recovery seed                       │
│   Restore from wallet.dat                  │
│   Restore from seed words                  │
│                                            │
│ enter: select   esc: close                 │
└────────────────────────────────────────────┘

• Show recovery seed first. It prints the wallet's 24 words, numbered, under the warning "Anyone with these words can spend your…". Put them in a password manager now: Proton Pass is free; 1Password, Bitwarden, Dashlane, Keeper and Apple Passwords all work. Never a screenshot, never a chat. Those 24 words rebuild this wallet in BoxWallet, in Divi Desktop, in the C++ node or in IronDivi.
• Encrypt wallet next. It opens a box that says Passphrase:. Pick a long one and store it in the same password manager. BoxWallet's own guide says a new password is asked for twice, because a typo on a fresh wallet means the funds are gone. Once the wallet is encrypted, sending and staking need the passphrase.
• Back up wallet copies the wallet file somewhere you choose. With the 24 words saved you rarely need it; Your recovery phrase is your backup explains the two cases where you do.

6Receive, send, and the other tabs

Press 3 for Receive. Your address is shown as text and as a QR code, with c to copy it and n for a fresh one:

Receive

Address: DAu1kj3zNruvPi5sNjkDagS2BD5L7ckCrC  (c: copy   n: new address)

▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ …

A Divi mainnet address starts with D. While the node is still syncing, coins sent to it will not show in Transactions (2) until the sync reaches the block they are in, so there is no rush. Send (4) shows the available balance, takes a destination and an amount, and, by BoxWallet's own guide, lets you review the transaction before it is sent. This guide did not send from BoxWallet, so check the screen yourself before you confirm. Settings (5) tells you where the wallet file and the chain live:

Settings

Wallet file: /home/you/.divi/wallet.dat
Blockchain : /home/you/.divi
Block index: built by the daemon
             Stop the daemon to rebuild it.

Staking needs a synced node and coins that have waited long enough. The Home pane has a Staking field for it, and BoxWallet's guide says the w menu is where you unlock and check staking. This guide did not stake with BoxWallet, so it does not show that field turning on. Estimate how often you'll stake covers what to expect from the balance you hold.

7What it put on your disk

BoxWallet does nothing you could not do by hand, and it leaves every piece where the C++ node expects it, so you can take over with divi-cli whenever you like.

Those two ports are deliberate. The C++ node's defaults, 51472 and 51473, are shared with PIVX, so a folder BoxWallet creates is moved off them. A folder that already existed, from Divi Desktop say, is adopted as it is: BoxWallet uses the chain and wallet already there, and adds only the lines the settings file is missing. The command tool reads the ports from the file, so this works unchanged:

~/.boxwallet/divi-cli getinfo
{
    "version" : "3.0.0.0",
    …
    "blocks" : 86011,
    "connections" : 8,
    …

Everything in A tour of irondivi-cli works here too, since the two command tools take the same commands.

8Stopping, quitting and updating

• s on the Home pane stops the node cleanly. Wait for Running: ✘ before switching the machine off.
• q quits BoxWallet but leaves the node running. We quit, the node kept syncing, and when we opened BoxWallet again it found the running node within two seconds and carried on showing it. So on a server you can close your SSH session and the sync continues; if you do want the node stopped, press s first.
• BoxWallet updates itself: it checks for a new release in the background, verifies the download against that release's SHA256SUMS, and swaps it in on the next launch. The log's second line tells you where you stand: BoxWallet: up to date (v0.8.38).
• A new Divi node release, when one comes, is installed by marking Divi and pressing i again, with the node stopped. Upgrade a node covers what to check before and after.

If something goes wrong

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