Why isn't my wallet staking?

1First, read what the wallet says

Every Divi wallet runs the same node underneath, and the node answers one question, getstakingstatus, with a list of true/false checks. Each wallet shows that list its own way:

The checks below follow the node's list. Divi Desktop shows only the first failing one, so fix it and look again; another may be hiding behind it.

2Is staking switched on?

Staking is on by default in every Divi node, but it can be turned off and stay off:

• Divi Desktop: the switch in the bottom bar must be on. If it won't move at all, the wallet isn't encrypted yet: click the lock icon beside it and set a passphrase first.
• Divi node: look for staking=0 in divi.conf and remove it, then restart. The last line of getstakingstatus, staking status, is false while staking is off.
• IronDivi: irondivi-cli setstaking true, or remove staking = false from irondivi.conf. The status text reads Staking Disabled while it's off.

3Is the wallet unlocked?

An encrypted wallet starts locked every time the node starts, and a locked wallet cannot sign a stake. This is the most common cause after a reboot or an update.

• Divi Desktop: tooltip Wallet locked. Click the switch, type the passphrase, keep Unlock for Staking only ticked.
• Divi node: walletunlocked: false. Run divi-cli walletpassphrase "passphrase" 0 true.
• IronDivi: getwalletinfo says "encryption_status": "locked". Run irondivi-cli walletpassphrase "passphrase" 0.

An unlock with a timeout runs out quietly. If you unlocked for 10 minutes last week, the wallet is locked again now. Use 0, or in Divi Desktop the Unlock for Staking only box, which has no timeout. Details in Stake from the command line.

4Are the coins old enough?

A coin can stake once it has sat unmoved in a block for one hour. The clock starts at the block that holds the coin, not at the moment you pressed send, and it restarts every time the coin moves, including when you send to yourself. We did exactly that on testnet, sending 100 tDIVI from a staking wallet to one of its own addresses:

divi-cli sendtoaddress y6Hni2ZJbfswHRv6TLNwApPVR4RxiT1QQd 100
b73ecd6c6c848f5fb7f75059497fce82303b78d72d3024cdb1c6a344f053eacc
divi-cli getstakingstatus
{
    "validtime" : true,
    "haveconnections" : true,
    "walletunlocked" : true,
    "mintablecoins" : false,
    "staking_balance" : 0.00000000,
    "enoughcoins" : false,
    "mnsync" : true,
    "staking status" : false,
    "stake split threshold" : 20000.00000000
}
# a few minutes later, one confirmation
divi-cli getstakingstatus
...
    "mintablecoins" : false,
    "staking_balance" : 12999.99995480,
    "enoughcoins" : true,
...
    "staking status" : false,

The whole 13,000 tDIVI stopped staking, not just the 100: the wallet had one coin, the send spent it, and the change came back as a brand-new coin. Until the next block confirms the transaction the balance counts as zero (Not enough coins); for the hour after that it counts but is too young (Coins maturing). Then it stakes again.

• Just received coins? Wait an hour after the first confirmation, then up to five more minutes: the node re-checks for aged coins every five minutes.
• Just won a stake? The coin that staked is spent and comes back as new outputs, so it starts the hour again; its reward can't move for 20 blocks either way. This is normal.
• Wallet with many coins: only the moved ones restart. Sending from a wallet with twenty separate coins leaves nineteen staking. Split and combine coins explains how to keep it that way.

5Is the node synced and connected?

The node refuses to stake on a chain it isn't sure about. It needs at least one peer, a newest block less than 100 minutes old, and a clock that agrees with the network.

• Divi Desktop: tooltip Syncing, and the peer count in the bottom bar. Wait for the sync to finish; on a fresh install that can take hours.
• Divi node: haveconnections: false means no peers. Compare divi-cli getblockcount with the explorer; if yours is behind and not moving, check the internet connection and any firewall.
• IronDivi: irondivi-cli getpeerinfo should list peers, and getblockcount should match the explorer.
• Clock: if the node logs Please check that your computer's date and time are correct, fix the system clock (turn on automatic time). A clock more than three minutes fast makes the network reject your stakes as "too far in the future".

6Are the coins where you think?

• In a vault. Coins you put in a vault are staked by the vault's server, not by your wallet. Your wallet's staking balance leaves them out on purpose. See What is a vault?
• Locked with lockunspent. A coin you locked on the command line is skipped by the staker too. divi-cli listlockunspent shows them; lockunspent true frees them.
• In another wallet file. If the balance itself is wrong, the node may have opened a different wallet.dat than you expect. Config files shows where each wallet keeps it.
• Not confirmed. staking_balance counts only confirmed coins. One block is enough.

7Is the computer awake?

Staking is a lottery drawn every minute, and your ticket only counts while the node is running. A laptop that sleeps at night, a desktop wallet you close, or a machine that updates and reboots into a locked wallet all stake far less than their balance suggests, and show no error at all. Options, cheapest first: stop the machine sleeping, run the node on a Raspberry Pi or a VPS, or put the coins in a vault and let someone else keep the lights on.

8Or is it just waiting?

If every check passes, the wallet is staking. Winning is a matter of balance and time. Each block goes to one staker, chosen roughly in proportion to coins staked, and today about 2.55 billion DIVI are staking on the network. Divide that by your balance and you have the number of blocks, on average, between your wins; there are 1,440 blocks a day.

Those are averages. Waiting twice as long as the average happens to about one staker in seven, and it means nothing is wrong. Estimate your stakes runs the numbers for your own balance, Staking returns explains where the 2.55 billion comes from, and Stake alerts sets up a message for the day a stake lands, so you can stop checking.

Next

• Stake from the command line: every field of getstakingstatus explained.
• Split and combine coins: stake more smoothly by keeping several coins.
• Stake alerts: be told when you win.
• Glossary for the words on this page.

Still have a question? Ask the Divi chatbot, or see all tutorials.