A friend of mine, opened his wallet today, and had recieved a 70 Decred transaction. Which seems to be a ticket being called to vote, but being sent the wrong way. ^ That's what we concluded anyway, since locked tickets, don't change the total balance, but this vote added all 70 DCR to total balance. 1cd6a39461f6932190c758a8503713a5587184778a9fefd1ed9588c225e8dbda Seems like a really bad thing, if that is the case. So figured I'd post it somewhere, though, not sure where to post it.
No, that's behaving as expected. 69 coins were temporarily locked in the ticket, then after voting 70.5 coins were sent to the reward address. The ticket doesn't exist any longer, so he hasn't gained 70 coins, but 1.5.
No, he gained a total of 70 Decred, added to his wallet. - I'm just gonna use fictive numbers, since it's not my place to showcase his balance. So let's just say he had 3 tickets locked, and a total of 400 coins. - He still have 3 tickets locked, but now have a total of 470 DCR in his wallet.
In that case he probably hadn't imported his pool script, so the ticket didn't appear in his balance until after it had voted.
That makes no sense, since he know exactly how many coins he have bought, and how many he received through PoS. - Those 70 DCR, showed up out of nowhere. I appreciate you trying to help, but please stop, if it's just gonna be guesswork without knowledge.
Hmmm... Let me try to understand. This is not his ticket? So are you saying someone else staked this and the return address somehow happens to be your friends wallet address? The sums at least match up. The ticket was purchased for 69.08 and was payed out with the POS reward of 1.4 (70.08 returned)
- He have never had a ticket missing, and none of his tickets were called. It just added 70 DCR to his balance, with a regular transaction. And since he didn't know why, he looked it up, and notified me about it, when he realized it was a vote. So yeah, that sums it up.
OK. The person purchased 3 ticket at the same price on the 9th of July. You are sure your friend did not do this? Can't explain that, beyond my level of expertise. Not a dev! That said, it would be logical to eventually see another 2 tickets to be payed to you friend as well. Lucky guy?
Yup Nimrod, I have seen the same thing. 3 tickets purchased on July 9th with the same split tx. Logistically speaking, the way that we construct tickets and votes in dcrwallet, it's simply not possible to have a vote reward go to a random address. Maybe if someone goofed up and did something crazy in constructing their own ticket it could happen, but not in our code. Sounds like user-error or getstakeinfo display issues
Well, he's not missing any tickets, so I'm assuming that it's not his. - The only way I see it happening, is if the guy who actually bought the ticket, punched in a recieving address on his own, and made a mistake somehow. Or if the new algorithm had a flaw. ^ I'm not a dev either, heck I don't code at all. So I would havbe no way of checking anything myself. <.<
your friend should try dcrctl --wallet validateaddress DsYjwV3q9pQvXQBMBqucJCJ11goEF5Uj9WX That will verify without a doubt that this is his ticket
This is how it usually looks, with an incomming payout. - It looks like an outgoing transaction. But instead of subtracting from the outgoing number, it adds to it instead. http://imgur.com/a/10kkR And this is the one in question. - The green icon, is for incomming transactions. http://imgur.com/a/mGlB3
So as Kandiru suggested before you rudely told him to stop,your friend should make sure they have imported the script from dcrstats
And as I wrote, my friend knows exactly how many tickets he have locked into, and how many coins he have purchased. So it makes no sense. - And that was definitely not being rude. That was me, politely asking him to stop, with what wasn't any help.
