-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incorrect transaction amount #59
Comments
I asked the guy to run the getrawtransaction command in the client that is showing the wrong amount. He replied with a screenshot: It looks like it's the same rawtx as I get: 01000000012d5a4ca421230de22ef048d1c2176d8ec71ccd7c212c2d6134d0764c2c74ad2d000000006c4930 (which I guess makes sense, since the hash is the same) So why does his client show it as a 2M DOGE tx, not 1M DOGE? Apparently it reduced his balance by 2M DOGE too, so he's actually lost coins due to this issue. Is there some way he can get his missing 1M DOGE back? |
This seems really difficult to believe. So you only received 1M? |
You can see it for yourself on the blockchain. I only received 1M, yes, to the DJoRyGBJHgoqBpEUknxi49RTDLN6MCaVMt address. It did cross my mind that the guy who sent it doctored the screenshot, replacing the 1M with 2M just to mess with us, but I don't think that's the case. |
I haven't done this before so I dunno how it works exactly, but can he use something like pywallet http://www.devtome.com/doku.php?id=pywallet to delete the transaction from his wallet, rebuild the blockchain, and see the result correctly? |
I'm going to close this as I don't believe the screenshot is proof that the client is fundamentally broken. If you experienced this from your end when sending to someone dooglus I'd 100% believe you and treat it as an emergency, but since someone else is claiming it, I think it's more likely someone is yanking your chain unfortunately. |
The above image shows a transaction which spends 1M DOGE according to the blockchain, but 2M DOGE according to the client. What's going on here?
The text was updated successfully, but these errors were encountered: