I haven't created an issue or posted on the issue you linked. The issue in #106 appears to still be happening with 0.0.8.
So it is not just me having wrong balance return from dcrwallet after it's recreation from seed. If you use the consolidate command you have to wait for it's transaction - like any other - to get included into a block, usually it won't take more that 3 new found blocks. Keep also in mind that a tx fee will be deducted for it, like any other transaction. Yeah if someone uses the stake pool, every time needed to re-create the dcrwallet from seed, the script should be re-imported.
Yes it's very important but someone may make this mistake because at the syncing end, daemon "stucks" about 15 blocks away from latest height until a new block is found. When you'll get the same latest height as in https://mainnet.decred.org/ is safe to start your dcrwallet and create your wallet.
Maybe running your wallet once with "-d debug" will help. More about it in this post and in this thread.
I find out that a ticket voted from getstakeinfo and the message I get in dcrwallet is an error one again: "[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" I remember before v0.0.8 I didn't get an error message, I've get something like "ticket voted on..." instead but I don't remember it exactly. I think it's just a display issue but I still don't know if there is might a voting problem with my wallet running if something goes wrong with stake pool. My wallet is unlocked of course and all my tickets are on stake pool.
I believe it's the maximum number of address to consolidate. Since it's unlikely that you'll have 100 000 address, this will consolidate them all.
I agree with @Shadowlance. As I've said here, I think 99999 means consolidate up to 99999 addresses and since 99999 addresses is hard to have right now, I believe it will work for everyone at this point. If I am wrong someone may correct me.
I agree with @Shadowlance As I've said here, I think 99999 means consolidate up to 99999 addresses and since 99999 addresses is hard to have right now, I believe it will work for everyone at this point. If I am wrong someone may correct me.[/QUOTE] Thanks a lot. Will check balance and tell how much it shows
Guys. After I recreated wallet from seed and even ran the consolidate wallet command (fees was deducted), today I checked the balance again, Ticket info is correct.But "Default" still has only 69 coins while "*" shows 402 coins. I dont think anyone sent me any coins so my balance has to be 290 something, The consolidate wallet command hasn't been able to help I guess. Any other solutions?
I have been tracking my coins to 100% accuracy in a spreadsheet as well, as balance/tx history shown by wallet have not been reliable. Just to know what came from where and how much profitable the mining has been for me. With GUI wallet i hope it will be as easy as looking at Transaction tab, as it is with other coins.
I missed something obvious here. Too much shorthand... is the debug command part of dcrctl? Not listed as a command with /l ?
@_ingsoc @ceejep My balance is still not correct. Any help? How can I spend the coins which are shown in "*" account? When I tried the dcrctl command to buy tickets and replaced "default" with "*", I got error message saying - -4: account name '*' not found Should I recreate wallet again/
'*' is just the "all funds" method for balance, it should show funds in all accounts. Tickets themselves may only be generated from a single account. If you or anyone else is still having balance issues, you can send me the wallet master pubkey (dcrctl --wallet getmasterpubkey) at cjepson@decred.org. I will load your wallet and check the balances. Your master pub key will allow me to see your fund but not spend them. You will also need to send redeemscripts for the pool if you are using it.
Just a clarification for any newbies that wander through here: @ceejep is asking for the PUBLIC key which is ok to give to people (that's why it's called public) NOT the PRIVATE key which is your seed words and hex string. Don't give that to ANYONE, including ceejep