A Yearly Checkup for Your DIVI

1The list, and when to do it

Pick one fixed day and put it in your calendar as a yearly event. Early January works well, because the tax export in step 8 needs the year to be over. Then work down this table. Skip the rows that do not apply to you.

Run a staking server? Add its system updates to the list. Still have a masternode.conf from before 2023? Read what to do with old masternode collateral; it may be holding coins back from staking.

2Software versions

Divi has had mandatory upgrades before. Version 3.0.0 was one: nodes that missed it stopped earning on 23 August 2023. Ask each program which version it is, then compare with its releases page.

# IronDivi
./irondivid --version
irondivid 0.2.6

# Divi Core
./divid -version
Divi Core Daemon version v3.0.0

# a running node; IronDivi uses
# irondivi-cli (and --testnet
# on testnet)
./divi-cli getnetworkinfo
"subversion": "DIVI Core: 3.0.0.0"

On IronDivi, getinfo always says 3.0.0.0. That is the Divi version it is compatible with, not its own. Use --version or the subversion line instead. Ours said /IronDivi:0.2.6/.

Now check what the newest release is. Each releases page has a link that always points at the newest one:

Our IronDivi says 0.2.6, newer than the newest release, because it is a test build. Yours should match the table or be newer. Divi Desktop shows its version when you hover over its icon in the system tray. BoxWallet updates itself and installs the Divi Core node for you.

If you are behind, follow Upgrade a node safely. Back up first, and download only from the releases pages above.

3Backups and the recovery phrase

The 24-word recovery phrase rebuilds the wallet. It is the backup that matters most. Check that it is still in your password manager (step 5). Once every year or two, prove it still works by restoring it on testnet.

The phrase cannot rebuild everything. Imported paper-wallet keys and vaults you added as a manager need a file backup too. If you did either this year, make a new encrypted backup now and replace the old one:

# Divi Core: one file
./divi-cli backupwallet \
  /home/you/divi-wallet-2027-01.dat

# IronDivi: a folder; zip it
./irondivi-cli backupwallet \
  /home/you/irondivi-wallet-2027-01

4The wallet passphrase

An encrypted wallet with a forgotten passphrase is only saved by the recovery phrase. So test the passphrase you have on record. Unlock for one second; the wallet locks itself again.

# Divi Core. Start the line with
# a space so the shell does not
# keep it in its history.
 ./divi-cli walletpassphrase "…" 1
null

./divi-cli getwalletinfo
"encryption_status": "locked"

null means the passphrase is right. A wrong one answers Error: The wallet passphrase entered was incorrect. on Divi Core, and Incorrect passphrase on IronDivi. Both use error code -14. On our node, two seconds after the test, getwalletinfo said "locked" again. A Divi Core node that was unlocked for staking goes back to that state instead.

On IronDivi, do not use getstakingstatus to see whether the wallet is locked. Ours said "walletunlocked": true while getwalletinfo said "locked". In Divi Desktop or BoxWallet, unlock in the app as you would to send, then lock it again.

If the test fails, stop. Do not try guesses on your only wallet. Go to A forgotten passphrase.

5Your password-manager entry

If you followed Inheritance, one entry holds everything. Open it and check, line by line:

• The 24 words are there, numbered 1 to 24. Do not copy them anywhere to check them.
• The wallet passphrase is the one that passed step 4. If you changed it this year, update it here first.
• The encrypted backup attachment opens, and it is the newest one from step 3.
• Each paper wallet has its address, where the paper is, and its passphrase.
• Emergency access still names the right person, and they still have an account. See Give your family access.

Check the manager itself too. Is its master password still at least 15 characters? Is two-factor login still on, with a second factor your family could use? Then, once a year, rehearse the inheritance on testnet, so you know the entry still works.

6Paper wallets

Visit each copy. Is it where the entry says? Can every character still be read? Ink fades, and paper gets damp. If a copy is damaged, make a fresh one from a good copy.

Then look up the address in Explorer 2.0 and check the balance. You only need the address for this. Do not type the 6P… key or its passphrase anywhere just to check. Decrypting shows the raw private key, and that is only needed when you spend from the paper wallet.

7Vaults and their managers

If someone else stakes your coins in a vault, check two things. The coins are still in the vault, and the manager is still staking them. You need your own wallet, the owner, for this, not the manager's word.

On 2026-10-22 we funded a 100 tDIVI vault from a Divi Core wallet and added it to an IronDivi manager. Here is what the owner saw:

# owner, Divi Core
./divi-cli getcoinavailability true
"Vaulted": {"AllVaults": [{
  "vault": "yGnauAuG…:yBPH6XXh…",
  "value": 100.00000000,
  "txids": ["68b06649…"] }]}

./divi-cli getwalletinfo
"vaulted_balance": 100.00000000

You can also look the vault up in Explorer 2.0 with no wallet at all. If your owner wallet is IronDivi, use the explorer: IronDivi's getwalletinfo always shows a vaulted_balance of 0.

Is the manager still staking? When the manager stakes your vault, the vault's coins are spent and sent back to the same vault with the reward added. So the value grows and the txids change. Write down the value and the first txid each year. If neither has changed for much longer than Estimate your stakes predicts for that amount, ask the manager. If they do not answer, take the coins back yourself: Reclaim vault funds needs only your wallet. Our test vault was too young to stake, so this paragraph comes from the source, not from a block we watched.

8The year's tax export

Staking rewards are income in many countries. Save each address's history once a year, even if nobody has asked for it yet. Explorer 2.0 can make the file in two ways:

• The CSV button on the address page saves every transaction. See Export an address's history.
• A link gives the same file with a price and a value for each row, which is what tax software wants.

# mainnet, one line, with your
# address in place of ADDR
https://services.divi.domains/
api/rpc/csv/ADDR.csv?vs=usdt

Ours, for a testnet address, began Date,Type,Amount (DIVI),Other Address,TxID,Block Hash,Price (USDT),Value (USDT). For money apps such as GnuCash, the OFX link has /ofx/ in place of /csv/ and ends in .ofx. Keep only last year's rows, and store the file with your other tax records. Staking returns shows how to turn it into a statement, and which tax tools read it.

If something goes wrong