A number of bugs affecting balance were found in 0.0.8 and patched. On the release of 0.0.9, it is recommended to restore your wallet from seed. 0.0.9 will also automatically restore your accounts from seed.
v0.0.9 is the next release. v0.0.8 is the latest. You can always find the latest releases using the releases tag on Github. The latest version is always posted across different platforms as well, and is usually accompanied by a Development Dispatch.
Knock on wood, I am running v 0.0.8 and have not had any significant wallet issues from launch day. I have never restored from seed, just replaced the files on each update. Is this abnormal? I don't want to restore from seed if it's not necessary. Please let us know on v 0.0.9 release if a restore should indeed be performed (even if one hasn't experienced any wallet issues). If so, instructions with the release would be welcomed.
Its not necessary that u will get issues if u just replace the binaries. Its just that it is recommended to recreate the wallet from seed. Even recreating the wallet from seed is not perfect yet. There are some issues that are still being resolved. Its largely up to u to choose the method though the devs suggest its better to recreate from seed. Edit - It will also be like a practise session for u so that in case for reasons whatsoever u lose ur wallet files then u will know how to recreate the wallet from seed. Thereby redusing a lot of tension for urself.
I'd advise --testnet for testing. I may have made some error, but after restore from seed I see 5 missed votes (there was 1 before). Can not recommend. Is there a way to check the numbers / tickets / votes / misses ? EDIT : if the log says "WLLT: PLEASE ENSURE YOUR WALLET IS UNLOCKED SO IT MAY VOTE ON BLOCKS AND RECEIVE STAKE REWARDS" you should really do so :-/ My bad.
The wallet will resync with the network and checked for lost tickets whenever it's restarted. It's likely you had some missed tickets that the wallet didn't pick up until it rescanned. Assuming you took the wallet down for about 10 minutes to rebuild, that's only 2 blocks that would have gone through. It's extremely (EXTREMELY) unlikely that you missed 4 votes in that period. You can check your dcrwallet log (~/.dcrwallet in Linux or %LOCALAPPDATA%\dcrwallet in Windows) to see when the votes failed.
EDIT : if the log says "WLLT: PLEASE ENSURE YOUR WALLET IS UNLOCKED SO IT MAY VOTE ON BLOCKS AND RECEIVE STAKE REWARDS" you should really do so :-/ My bad. I think he didn't keep his wallet unlocked in the first place.
v0.0.9 is already uploaded a few hours ago on GitHub but I'll wait for the announcement before I'll update. So @ceejep @_ingsoc we have to backup the old dcrwallet folder, delete it and then run the new 0.0.9 version of dcrwallet or the new dcrwallet version will ask for our seed at first and our wallet will get recreated from seed anyway? Please clarify this on next release announcement. Also every time a ticket of mine (I only have tickets on stake pool) gets voted, dcrwallet on v0.0.8 returns this message: "[ERR] WLLT: Cannot handle chain server voting notification WinningTickets: Error encountered attempting to create vote using ticket xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: failed to generate correct signature script for ssgen or ssrtx: stack underflow" Is that an issue? Before v0.0.8 I remember getting a message like: "[INF] WLLT: Voted on block...".