Hey guys, just a quick question, Does buying ticket and pointing it to a pool causes your --wallet getbalance * 0 all to reduce temporarily? For example, Say i have 1000DCR to begin with...afterbuying 50 tickets at 20DCR and delegate it to the pool. Am i expecting to see 1000DCR when i run the --wallet getbalance * 0 all command or zero? The reason why i'm asking because my "--wallet getbalance * 0 all" is showing about 1000DCR lesser compared to a few days ago, after i started pool mining. And i realized this only 24-48 hours after buying a about 1000DCR worth of tickets. I never encountered this before when i was solo mining so im just curious. Thank you.
If you use a pool, there shall be "imported" account for it I think. You can try dcrctl --wallet listaccounts and for each account _ACCNT_ do dcrctl --wallet getbalance _ACCNT_ 0 all I believe I saw something about account handling not ready somewhere, but please check with pool ops or devs.
Hmm, there doesn't seems to be any additional accounts apart from the one and only "default" . any other thoughts? P/S - As of now, i have 315 live tickets. Assuming they are all bought at an average of 17DCR, that should still give me a total of 5400~DCR. However, my --getbalance all is only showing 4400+ DCR or so. It was still showing the correct number the last i checked about 1 week ago.
Is it possible they are still in mempool ? What getstakeinfo returns ? Also - I see "imported" among your accounts, what dcrctl --wallet getbalance imported 0 all returns ?
Thank you for pointing that out, you were right. The "imported" turned out to be the second account. All the balances has been accounted for! I see a flag that i can use to move and merge this back together into the default account. 1. I don't like running separate account and prefer to have single default account for everything. Can i move the imported account back into the "default" and delete it thereafter? 2, Or is this "imported" account absolutely necessary for pool mining? 3. Does this "imported" account has its own wallet address? So far, i have been getting error "Address Pools for account XXXXX are undeclared" whenever i tried to --getaccountadress or --getnewaddress.
I'd wait for version 1.6 (in GIT) to be released and test. Just guesses, not sure about the corectness neither present decred state "account functionality" : 1/ yes you can as long as your money are available. If you are staking, they are locked. 2/ it works that way 3/ yes, addresses. No idea about that error, if in troubles, rebuild from seed (see my signature) Spoiler: getnewaddress help help getnewaddress getnewaddress ("account" verbose=false) Generates and returns a new payment address. Arguments: 1. account (string, optional) DEPRECATED -- Account name the new address will belong to (default="default") 2. verbose (boolean, optional, default=false) Show pub key as well as address Result: "value" (string) The payment address EDIT : 3/ - maybe not - may be it contains imported addresses(keys) only, so a wallet does not know how to generate a new one. Pool ops shall know better