Quote from: fbastage2 on March 14, 2018, 12:27:45 PM

There's something wrong with the daemon or wallet. Had problems all day yesterday with the wallet getting incorrect values (especially if I run 'reset'). This is a high-traffic wallet, and this issue might not affect smaller wallets.

As a result, the wallet tries to spend inputs that have already been spent. I think the problem may be at the daemon level, though, because after an attempted invalid spend, the daemon itself fails to mine properly. I had to resync and restart the daemon about 5 times yesterday, and it still ends up getting corrupted over time.

Overnight the wallet balance was:

Code:

[wallet aab111]: balance
available balance: 0.00000000, locked amount: 10149.36234978

in the morning, with only one block being processed, and no other activity:

Code:

[wallet aab111]: balance
available balance: 21609.03594598, locked amount: 8540.32740380

the correct balance after resync:

Code:

[wallet aab111]: balance
available balance: 900.52624989, locked amount: 9248.83609989

overnight the daemon shows invalid transactions (spent inputs)

Code:

05:54:07.811682 INFO Transaction with id= <22990622fa5c985dcb0932549a5ca8278f1d8fdd7b00b187da16c06d22874d28> used already spent inputs
05:54:07.811850 ERROR Transaction verification failed: <22990622fa5c985dcb0932549a5ca8278f1d8fdd7b00b187da16c06d22874d28>
05:54:07.811925 INFO [on_send_raw_tx]: Failed to process tx

---

what code base did you fork for your coin? is there a known issue and a known fix?

I'm in the process of moving coins to a new wallet to confirm that this does not affect a low-traffic wallet and so my payouts can work again.

known issue on double spend! seems not sync proper