Issue with reddcoin wallet lots of coins at stake (irony intended!)

Hi, we are running a faucet for reddcoin, but somehow the outgoing transfers seem to be very unstabile, we even tried to recompile and resync, but instability still remains, anybody also encountering this issue? db.log is empty. It says balance is 43.5306 but unconfirmed balance is: 361255.3746. WTF! Walletversion 60000…

Is this a wallet malfunction, where did the coins go? Any ideas?

cointopay what block is your wallet on??

as of Mon Jan 26 11:12:40 2015 - block [515157]

cointopay ur wallets a bit out of date, ur probably not on main chain anymore.

"version" : 1040000

iisurge said:

ur probably not on main chain anymore.

It was recently compiled from github… Storing old versions there?

block: 515111

P.S. gimme some addnodes please!

cointopay yes all versions are kept on github. Do you use a code that has a version number to install it? current version is 1.4.1.0

We only use the daemon, no qt.

cointopay i do aswell.

all versions on github can be found here:

https://github.com/reddcoin-project/reddcoin/releases

https://github.com/reddcoin-project/reddcoin we used this version to compile.

cointopay well as you can see that is version 1.4.1.0

Are you sure the new install/update went smoothly

cointopay ah wait there is a difference between version and walletversion. I was looking at wrong one.

weird

yes, send ‘getinfo’ for the correct information

 "version" : 1040100,
 "protocolversion" : 80000,
 "walletversion" : 60000,

Hi, I have the same as you:
version: 1040100
protocolversion: 80000
walletversion 60000

For some reason the balance was confirmed tonight at block: 515234
The only thing I did was is increase the keypool to 5000, because faucets = huge amounts of transfers!

P.S. I get a lot of those:
ERROR: mempool transaction missing input, other then that seems fine.

But main question still remains: why it takes days before the balance gets to confirmed status? Do we need to add nodes, we don’t have this issue with other coins, but they are mostly proof of work…

Please assist, our customer needs answers :slight_smile:

cointopay Sorry, I am in the wrong timezone to search for a complete answer just now, so hopefully others will follow up in the meantime.
I did a quick Google search on the error message, and it appears with various other coin wallets
Will need to research this more

I think it’s a non-issue and is related to the internal working:
https://github.com/bitcoin/bitcoin/issues/2821

It’s about transactions that were added but unable to be dealt with so they become orphans, the code just makes the observation and moves on. I don’t think is a big issue, but would be great if removed or if the “somethin bigger” issue will get fixed.

Guys, some developer needs to really look into the wallet stability. We have massive faucets acting with reddcoin and we have lots of troubles of funds not being released. We are doing a full recompile now, I will keep this topic updated.

2 Likes

cointopay seems strange out of all the reddcoin faucets only yours seems to have issues. I hope you get it sorted

A couple ideas to iron out wrinkles with your wallet…

You mentioned that you use thousands of keys. You could consider re-using change addresses (or even eliminating them). There is an obvious privacy issue to consider, but when it comes to faucets, it’s pretty easy to tell which funds are in a faucet and which are paid out anyway through rudimentary blockchain analysis, so I don’t consider it a big concern.

You could also consider breaking up inputs in your wallet into many smaller inputs, so that a payout does not require you to include all your coins in the tx.

Finally, your faucet could include logic to only spend confirmed txs.

cointopay How is your internet connection? If it’s flaky, all kinds of problems can occur (private forks of the blockchain etc.)