All my coins are in the wallet and staking since now.
I closed my wallet and opened it again but a Note says we are not staking because we don't have mature coins.
We were just staking prior to closing the wallet and re-opening it.
What happened?
I see that all the time. "Not staking because you don't have mature coins", but nonetheless
it does still stake(!) Just wait an hour or two and you should see staking payments coming in.
Dunno why the message shows there, which is does for me most of the time as well, even when
it is staking (shows coin next to "Staking:", that's how I know), and my wallets seemingly are staking all the time (although I do see them randomly, for brief periods of time, like 1 or 2 seconds, not staking and then it jumps back to coins showing up next to the "Staking:" label again.) It has me wondering whether it is "normal" behaviour or something else going on. In other words, perhaps it is staking intermittantly, and, in which case, I'm wondering if I'm getting the full staking payments.
I think it's this:1-IF you close wallet and re-open it the coins that were deposited from staking need to mature.
2-When you deposit more coins to a wallet those new coins need to mature.
So it stakes the coins that were there already BUT is waiting till the NEW Coins mature before it stakes them also.
Make Sense?
Update: Yep...All coins now staking on this wallet too...
BTW-Staking is Kewl!
Everyone should do it!
I must just add: That since 'the issue', yesterday: when it happened, I reloaded my blockchain in one of my wallets (deleted the blockchain files.) That was the first thing I did, thinking it might be something going on with my wallet, before we knew what the cause was; and, since then my wallet seems to, properly, show the staking icon all the time! (as would be expected.) So it seems I've managed to inadvertently fix that issue with my wallet!
If anyone else is experiencing an issue with not seeing the staking icon (after waiting the 8 hours for coins to mature, first, of course), then that's what seems to have fixed it for me!
Previously I had suspected that the issue might be caused by NAT which is used on the network I'm on, but it seems I 'just' needed to reload my blockchain and it worked properly.