https://forum.decred.org/threads/pos-guide-any-os-solo-stake-mining.1228 the get stake info command is mentioned here.
i can not do that at first stage at pool Your P2SH multisignature script for delegating votes has been generated. Please first import it locally into your wallet using dcrctl for safe keeping, so you can recover your funds and vote in the unlikely event of a pool failure: dcrctl --wallet importscript "script"
The main reason to vote in a stake pool is that the pool will actually vote on your behalf so you don't need to keep your wallet open or computer on 24/7. Of course, you have to trust the stake pool to be online 24/7
Is this man trolling/fudding or are there serious problems? So far I didn't experience any issues after the update.
There are known problems with 0.0.7 vote reporting which are expected to be resolved with 0.0.8. Some people have just been luckier than others.
Well I don't know if he has a problem with total balance or spendable balance but I have some minor issues too with total balance (spendable + locked) after recreating wallet from seed. My spendable balance and bought tickets are OK though so my problems are minor but I start PoS and first bought tickets for Mainnet Stake Pool address with 0.0.7 version anyway. In Windows 10 Pro x64 using windows-amd64-20160309-01.zip v0.0.7 files with a spendable balance more x10 times the price of ticket I was getting a message that I didn't have enough balance for a ticket for hours so I delete everything including Dcrd and Dcrwallet folders on local files to check if that will fix the problem. Unfortunately, because I've done this before with every dcrd release update with no problem I didn't backup previous dcrwallet folder files. When dcrd folder / block database recreated, got updated to latest height (+1 found block after to be sure) I recreated wallet from seed as always and then run dcrwallet, synced to dcrd, unlocked it and re-import pool script, these issues came up: - getbalance (spendable only) is equal = to getbalance "default" 0 all (spendable + locked) but it shouldn't cause I have some live and immature tickets for staking so getbalance "default" 0 all (spendable + locked) should also count these tickets value but it doesn’t. I didn't get any tickets disappeared though (--wallet getstakeinfo) so there is NO real or major problem, the values from these tickets will start adding to both balances when they got voted, misses/revoked or expired, to total balance when they will still be immature and to both balances (total and spendable) when they get 256 confirmations. - With --wallet getbalance "default" 0 locked I also get 0 of course and it starts counting from that point. For example, a ticket voted afterwards and I got it count on locked and total balance at first and after the appropriate confirmations to spendable balance as well (removed from locked at that point of course). - Sometimes with sufficient spendable balance I still can't buy - manually or automatically - tickets for mainnet stake pool address (I don't want to test without it because I can't run wallet 24/7) but I believe this might be cause of many people trying to buy tickets, but why the message of no sufficient balance (I don't remember the message exactly), shouldn't I get another one instead? Maybe @ceejep and other developers can check these minor problems and fix them in next versions. I reproduced the problem 3 times since yesterday before I post it here just to be sure. It's not a real problem though since spendable balance is always correct, staking works and there is no other problem with transactions or anything else. Also when the tickets bought before wallet recreation will get voted, missed or expired, everything will be go back to normal I believe. It's just annoying not to get everything with getbalance "default" 0. Those who just replaced the dcrd release files and didn’t delete Dcrwallet local folder probably didn’t have such a problem. But is it better to make a clean update (deleting Dcrd and Dcrwallet local folders too) on every new release or there is no difference or reason for it? Should I only replace the .exe files in future releases?
1) First issue is a bug with storing P2SH outputs as I'm guessing these are stakepool tickets. Fixed in https://github.com/decred/dcrwallet/pull/104 2) Should be fixed on next release. 3) There's a bug with both fees (which isn't fixed by that branch) and accounts. UTXOs being in other accounts messes up transaction generation. That's patched in the next version. Fees will take a bit longer to patch, but the work around for now is consolidating (dcrctl consolidate 9999). I would resync your wallet after the next release and reimport the stakepool redeemscript. Should fix everything.
Dear Decreders, With my limited understanding of the process I was wondering: if I use --wallet getbalance to obtain a new address, does this interfere with the Stake Pool? Because if I do so, the Stake Pool will be using a Public Key Address that is based on one of my older addresses. I'm afraid that if I request a new address, it will create a syncing problem between my wallet and the stake pool. Legit? Also, can I use my webwallet while I'm also using my desktop wallet? Funds are not automatically syncing at the moment. As always, thank you in advance for your answers!
That doesn't get a new address, it checks your (spendable, by default) balance. Also, no it won't. The ticket is tied either to the address used to purchase it, or to a unique ticket address which the wallet tracks. (I'm not entirely sure which, but either way, the wallet would keep track.) Decred would be pretty useless if this was a problem. No. Don't do that. The web wallet tells you not to do that. You've been told elsewhere not to do that. @davecgh has said repeatedly not to do that. Everybody who's ever asked has been told not to do that. Seriously, why do people try to do that? If you have two wallets with spending access to the same addresses, they can get out of sync with each other and you also increase your chances of spending collisions, exactly like what you're observing. I think you in particular asked about that on IRC and dave and I both told you not to do that. If you want to keep a Copay wallet for everyday use and a dedicated staking wallet, send credits from the staking wallet to load your copay wallet periodically. That's how I do it.
As @ClokworkGremlin has noted, that is absolutely the case. That said, I do also recognize that it is useful to have multiple instances, such as in the case of redundant voting wallets, so I just opened a new proposal on Github which could help resolve the issue or running multiple instances if implemented.
@ceejep is it possible to add a label/type "immature" to getbalance command. Right now there is no way to see immature balance. This might not be a problem with other coins as coins are immature for just 1 conf but with ticket buying they are immature for 256 confs. Also "all" won't show immature balance which makes people think there funds are missing. Those funds are invisible for 256 blocks as their is no way to see immature funds.
Yes, that should have been --wallet getnewaddress, obviously... It was late and I lost my focus after writing this: https://decreddiscovery.blogspot.com/2016/03/making-profit-with-decred-beginner.html Thank you for the definitive answer. Actually I wasn't using my webwallet, just checking my balance sometimes to see if it would work to have both wallets synced. I'm not a total idiot Great, I think that would improve the user experience of Decred significantly. Thank you for taking the time to help out a newbie like me. As mentioned I published this to help out others. If it has any mistakes, please inform me in this thread: https://forum.decred.org/threads/decred-discovery-beginner-friendly-pos-guide.1322/
i put my first ticket at pool in how many days i will know if voted or not? and what my pool tickets stats will tell???? also what mean at pool site Votebits 1?????