I would think that a faucet trying to stake would introduce all kinds of issues. Does your faucet include logic to not try to spend staked coins after they have successfully staked for some period of time (2 hours maybe? I can’t recall off the top of my head how long they are frozen)? Also, if it pays out frequently, it is highly likely that staking is impossible anyway, as you need to accumulate some number of hours of coin age before staking can even happen.
Well, the unconfirmed balance is now confirmed, and I didn’t change it back to staking=0. It took maybe a week to get to this state.
It took a full wallet rebuild (with same wallet) and a keypool upgrade, but all is well. Last time this happened the wallet was not staking, similar issue happened. I really like the idea of staking (in general), so we will see what will happen. Customer was still using reddcoin for the faucet, but there was just a big amount in unconfirmed status.
So all in all is well, would still be interesting to know the root cause for this. We will see. Thanks for supporting!
Our faucet wallet encounters the same problem when conducting multiple payouts and so does many others. This has been an issue happening to us for roughly 9 months and to fix the issue we just reboot the wallets. We have written a source code that checks the wallets balance and if its not there it reboots the daemon!
I have talked to a few people before about this and nobody seems to know or want to believe me about it either.
For any of you that think its a version or compiling error try sending 100 transactions of 1 RDD to another one of your wallets not the same one and see how many go through before the issue occurs!
Our faucet wallet encounters the same problem when conducting multiple payouts and so does many others. This has been an issue happening to us for roughly 9 months and to fix the issue we just reboot the wallets. We have written a source code that checks the wallets balance and if its not there it reboots the daemon!
I have talked to a few people before about this and nobody seems to know or want to believe me about it either.
For any of you that think its a version or compiling error try sending 100 transactions of 1 RDD to another one of your wallets not the same one and see how many go through before the issue occurs!
To be clear, it happens on just Reddcoin wallets or on a lot of wallets?
Also, have you considered sending 10 txs with 10 outputs each, or even 1 tx with 100 outputs, rather than 100 individual txs? I would imagine you are getting robbed in fees doing them separately, and the network could be throttling you for “spamming” it…
Our faucet wallet encounters the same problem when conducting multiple payouts and so does many others. This has been an issue happening to us for roughly 9 months and to fix the issue we just reboot the wallets. We have written a source code that checks the wallets balance and if its not there it reboots the daemon!
I have talked to a few people before about this and nobody seems to know or want to believe me about it either.
For any of you that think its a version or compiling error try sending 100 transactions of 1 RDD to another one of your wallets not the same one and see how many go through before the issue occurs!
Is cryptoblox your faucet? I’ve noticed the server balance goes to below 1 full coin quite often, then after a bit returns to full. I only mention this cuz if that’s not your faucet, a similar issue might be happening to others.