I send it the private key already, please find out what happened
*sigh*
Yes, you've been had. How did you get the public address? The private key you sent me does not correspond to it, and is one of a small handful of "valid-looking" WIF strings that, after the checksum is decoded, result in garbage. In this case, the supposed actual private key is all zeroes:
That key has been published before during the directory.io bit back in the day:
http://www.reddit.com/r/Bitcoin/comments/1ruk0z/dont_panic_directoryio_thing_is_fake/Many different odd errors arise from trying to use it, depending on the client. C's address verifier completely crashes if I try to check it a certain way. You can however look at what I'm talking about here:
http://gobittest.appspot.com/PrivateKeyThat presents the most accurate answer. It's not included in my screenshot, but if you test it yourself, it's at the top of the page in red:
Private key is not on curveIt's a deliberately-chosen "private key" coordinate that does not have a coordinate pair. It is not a point in the elliptical curve used in Bitcoin at all. (According to most client interpretations.) You can actually send coins there with certain clients and retrieve them also, but, as you can see here:
http://directory.io/0 yours is the very first one, and has been used before, and is definitely not the key to the address you were expecting, with 2.2~ish BTC.
Thank you for the analysis, i saw the QRCode of private key is likely not flat, can it make the problem ?, i send to you the original QR Code which he send to me
I can import the QRCode to the blockchain wallet perfectly, and get the coins (2.2 BTC ) without addressing the public key at all.
No, the QR Code and WIF_PrivKey you showed me are for a private key, in hex form, of *ALL ZEROES*. Blockchain.info does not parse that properly (it will tell you "
Error importing private key: TypeError: this.x is null"). Which is pretty irrelevant, because even if it could, the addresses associated with that private key are
https://blockchain.info/address/1MsHWS1BnwMc3tLE8G35UXsS58fKipzB7a and
https://blockchain.info/address/1Q1pE5vPGEEMqRcVRMbtBK842Y6Pzo6nK9 (uncompressed, and compressed, respectively; the compressed WIFprivkey would be KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU73Nd2Mcv1 btw, but blockchain.info will error out on that one as well), neither of which is the address you're talking about, and neither of which currently has coins.
Edit: public addresses based on list at database.io; perhaps the nature of that site didn't require complete protocol compatibility. The ones I listed may not be (or at least not the only) addresses for this privkey. The public address you showed us all way earlier has a couple BTC, yes. However, none of the information you've showed since (QR code, private key, etc) grants you spend power over those coins, and there is nothing we can do about that. If you were scammed, that is truly unfortunate and I am sorry about that, but unless the guy gave you any other QR codes or something, we can't do anything I'm afraid.
Also, to your question, that I think you're asking about QR scanning... no, if it "scans" and gives you characters, it is very rare for it to have been a "mis-scan". And if it did misscan, which I have been occasionally, it is unfathomably improbable that it would become a privkey of all zeroes! It doesn't mess up by a letter or two, it'll turn a string like KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU73Nd2Mcv1 into something like a few letters, weird ASCII symbols, that kind of thing. QR codes don't have to be flat. Either they scan or they don't. That's part of the crazy pattern on them, to allow for the correction of skewed and off-axis camera angles.
Anyway, bottom line is, if that's the QR code he gave you, while you thought your coins were at the address you gave way earlier, yes, it seems you were scammed.