Skip to content
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

Closed
dooglus opened this issue Dec 27, 2013 · 5 comments
Closed

incorrect transaction amount #59

dooglus opened this issue Dec 27, 2013 · 5 comments

Comments

@dooglus
Copy link
Contributor

dooglus commented Dec 27, 2013

untitled

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?

$ dogecoind getrawtransaction 7a41006d1b511f875f68707b9f310b1946d7c3e1af6d51961faaf3130d5da4e9
01000000012d5a4ca421230de22ef048d1c2176d8ec71ccd7c212c2d6134d0764c2c74ad2d000000006c493046022100d4d76f87e9edfa770063d86f12d0cf8a915864ee9f857a37e8f22244f405a187022100dcbfca11b1ccdb17e1303519906e7df96604afbb8b0d70a1c65f4a1a39609a6d01210265151f1fc2192e8617f8243e78dab4517a97aaeabcea9e6b446026ac23445884ffffffff0230467c77145e00001976a914303d79d9af56a66108895f36be2a1db805241dfc88ac00407a10f35a00001976a91495d9a9793e162a213d3c9730838f735579a3382688ac00000000
$ dogecoind decoderawtransaction 01000000012d5a4ca421230de22ef048d1c2176d8ec71ccd7c212c2d6134d0764c2c74ad2d000000006c493046022100d4d76f87e9edfa770063d86f12d0cf8a915864ee9f857a37e8f22244f405a187022100dcbfca11b1ccdb17e1303519906e7df96604afbb8b0d70a1c65f4a1a39609a6d01210265151f1fc2192e8617f8243e78dab4517a97aaeabcea9e6b446026ac23445884ffffffff0230467c77145e00001976a914303d79d9af56a66108895f36be2a1db805241dfc88ac00407a10f35a00001976a91495d9a9793e162a213d3c9730838f735579a3382688ac00000000
{
    "txid" : "7a41006d1b511f875f68707b9f310b1946d7c3e1af6d51961faaf3130d5da4e9",
    "version" : 1,
    "locktime" : 0,
    "vin" : [
        {
            "txid" : "2dad742c4c76d034612d2c217ccd1cc78e6d17c2d148f02ee20d2321a44c5a2d",
            "vout" : 0,
            "scriptSig" : {
                "asm" : "3046022100d4d76f87e9edfa770063d86f12d0cf8a915864ee9f857a37e8f22244f405a187022100dcbfca11b1ccdb17e1303519906e7df96604afbb8b0d70a1c65f4a1a39609a6d01 0265151f1fc2192e8617f8243e78dab4517a97aaeabcea9e6b446026ac23445884",
                "hex" : "493046022100d4d76f87e9edfa770063d86f12d0cf8a915864ee9f857a37e8f22244f405a187022100dcbfca11b1ccdb17e1303519906e7df96604afbb8b0d70a1c65f4a1a39609a6d01210265151f1fc2192e8617f8243e78dab4517a97aaeabcea9e6b446026ac23445884"
            },
            "sequence" : 4294967295
        }
    ],
    "vout" : [
        {
            "value" : 1034419.96990000,
            "n" : 0,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 303d79d9af56a66108895f36be2a1db805241dfc OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a914303d79d9af56a66108895f36be2a1db805241dfc88ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "D9YActhMpZ13DVFykFPqzgoycpr3TFuYLq"
                ]
            }
        },
        {
            "value" : 1000000.00000000,
            "n" : 1,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 95d9a9793e162a213d3c9730838f735579a33826 OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a91495d9a9793e162a213d3c9730838f735579a3382688ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "DJoRyGBJHgoqBpEUknxi49RTDLN6MCaVMt"
                ]
            }
        }
    ]
}
$ 
@dooglus
Copy link
Contributor Author

dooglus commented Dec 27, 2013

I asked the guy to run the getrawtransaction command in the client that is showing the wrong amount. He replied with a screenshot:

screenshot - 13-12-27 - 10 44 34 am

It looks like it's the same rawtx as I get:

01000000012d5a4ca421230de22ef048d1c2176d8ec71ccd7c212c2d6134d0764c2c74ad2d000000006c4930
46022100d4d76f87e9edfa770063d86f12d0cf8a915864ee9f857a37e8f22244f405a187022100dcbfca11b1c
cdb17e1303519906e7df96604afbb8b0d70a1c65f4a1a39609a6d01210265151f1fc2192e8617f8243e78dab45
17a97aaeabcea9e6b446026ac23445884ffffffff0230467c77145e00001976a914303d79d9af56a66108895
f36be2a1db805241dfc88ac00407a10f35a00001976a91495d9a9793e162a213d3c9730838f735579a338268
8ac00000000

(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?

@dogecoin
Copy link
Collaborator

This seems really difficult to believe. So you only received 1M?

@dooglus
Copy link
Contributor Author

dooglus commented Dec 28, 2013

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.

@dogecoin
Copy link
Collaborator

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?

@dogecoin
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant